The Identity Applications installer copies the data from the Identity Applications database idmuserappdb to igaworkflowdb. If an existing workflow process is in a running state, it’s data is moved to igaworkflowdb before the new Workflow Engine starts managing it. The Workflow Engine persists the workflow state information in a new database named igaworkflowdb. This change is targeted to enable the Workflow Engine to execute business process definitions at runtime from Identity Applications and Identity Governance and act as a common request and approval service for both products.īy default, the Workflow Engine is installed as part of Identity Applications installation. This Workflow Engine will replace the Workflow Engine that was embedded with the Identity Applications in the previous versions of the product. Identity Manager provides Workflow Engine as a separate service. For more information, see Adding Workflow to Roles and Resources in the NetIQ Identity Manager - Administrator’s Guide to the Identity Applications. For greater flexibility and ease of use, NetIQ recommends that you use this method whenever possible. This new method is targeted to ease the user experience of creating workflows. The Add Workflow user interface is illustrative, easy-to-understand with a step-by-step wizard based workflow creation process. It also provides option to add workflow based on custom templates created in Designer. A set of pre-defined System Templates and Template Forms are available that you can use to add a workflow. You can now quickly create a workflow in Identity Applications without switching to Designer. The Identity Applications user interface includes a new option, namely Add Workflow, in the Roles and Resources pages, that allows you to add a workflow to the role and resource. Identity Manager introduces a new simplified method for adding a workflow to role and resource.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |