Child pages
  • IDM Workflow Development Lifecycle
Skip to end of metadata
Go to start of metadata

Description: Challenges of developing workflow in OpenIDM - Activiti, BPMN & Groovy


  • Synchronous changes are normal in OpenIDM - point a->point b : But you have to have a way to control the process (approval, etc) (make it asynchronous)
  • Workflows allow you to describe business logic and interaction that integrates with provisioning
  • Workflow design can be as complicated or simple as you wish - to fit your individual needs
  • The process of developing workflow from scratch can be challenging - but we include some samples (workflow sample)
    • XML based BPMN2 process description and definition
    • USE the sample to facilitate your requirements 
  • Easiest way to develop workflow is to find an example that closest fits your model and modifying
  • Activtio designer for eclipse demo
    • Generates BPMN2
    • You can ALSO edit the XML directly (Jake finds this easier) 
  • Design of workflow is really up to you:
    • You can design simple / specific workflow (hundreds of workflow)
    • You have complicated & dynamic workflow (tens)
    • Management of workflow is key and how much time you spend managing workflow
  • Forms can now be designed and implemented outside of the workflow process (used to be embedded in 2.1) using "formkey" property 
  • Flow of activity for workflow in OpenIDM:
    • Processes and tasks (factories)
    • Process instances
    • OpenIDM of workflow are abstracted (and present as an endpoint over REST)
  • Workflow is also a good way to control orchestration
  • Anything you can do in the UI, you can also do over REST,  Script, etc.
  • No labels