To copy a workflow
-
Select the Workflows category.
-
Select the workflow in the navigation view.
-
Click in the navigation view.
-
Edit the workflow properties.
- Click OK.
To copy a workflow
Select the Workflows category.
Select the workflow in the navigation view.
Click in the navigation view.
Edit the workflow properties.
To delete a workflow
The project wizard creates a synchronization workflowSpecifies the order of all the synchronization stepsSpecific rule for processingSequence of process steps for mappingList of object matching rules and property mapping rules which map the schema properties of two connected systems to one another. an operational workflow. The process steps are connected to one another by predecessor/successor relationships. This functionality allows flexibility when linking up actions and sequences on object events. exactly two schema classes. to be run during synchronizationThe process of comparing data between One Identity Manager and a target system. Objects and their properties are compared by fixed rules. Synchronization results in the identical data situation in the target system and One Identity Manager database.. for initially loading the target system objects into the One Identity Manager database. You can use the workflow wizard to set up more workflows. The workflow wizard specifies workflows for the direction of synchronization "target system".
To create a workflow with the workflow wizard
This starts the workflow wizard.
Click Next.
Property | Description |
---|---|
Display name | Enter a display name for the workflow. |
Description | Text field for additional explanation. |
Click Next.
All mappings are enabled by default.
To disable a mapping, double-click .
To enable a mapping, double-click .
Revision filteringMethod for accelerating synchronization. Only objects that have changed since the last synchronization are fully loaded and synchronized. RevisionHighest value of the revision countersInformation about the last change to a system object. The revision counter is used to determine the objects that have changed since the last synchronization. of all a schema type's objects that are synchronized during a synchronization run. This value is stored in the DPRRevisionStore table, in the Value column. It is used as a comparison value for revision filtering when the same workflow is synchronized the next time. filtering can only be used if the target system supports it. is permitted for all mapping, by default.
Click Next.
In the Database method column, select the processing method to be run in the One Identity Manager database.
- OR -
In the Target systemAn instance of a target system in which the employees managed by One Identity Manager have access to network resourcesEquipment that is necessary for an employee's work efficiency, for example, mobile phones, desks, company cars, or keys. Resources can be any equipment that is not system entitlements, devices, or software.. Example: An Active Directory domain X for target system type "Active Directory", a directory Y for target system type "LDAP", a client Z for target system type "SAP R/3". method column, select the processing method to be run in the target system.
Click Next.
In the Database method column, select the processing method to be run in the One Identity Manager database.
- OR -
In the Target system method column, select the processing method to be run in the target system.
Click Next.
In the Database method column, select the processing method to be run in the One Identity Manager database.
- OR -
In the Target system method column, select the processing method to be run in the target system.
Click Next.
This creates the workflow. You can check the properties of the Workflowsee decision workflow, see provisioning workflowSpecifies the order in which the synchronization steps are provisioned., see synchronization workflow, and the synchronization steps with the workflow editor and rework them.
Enter the following properties for a workflow.
Properties |
Meaning |
---|---|
Workflowsee decision workflow, see provisioning workflowSpecifies the order in which the synchronization stepsSpecific rule for processingSequence of process steps for mappingList of object matching rules and property mapping rules which map the schema properties of two connected systems to one another. an operational workflow. The process steps are connected to one another by predecessor/successor relationships. This functionality allows flexibility when linking up actions and sequences on object events. exactly two schema classes. are provisioned., see synchronization workflowSpecifies the order of all the synchronizationThe process of comparing data between One Identity Manager and a target system. Objects and their properties are compared by fixed rules. Synchronization results in the identical data situation in the target system and One Identity Manager database. steps to be run during synchronization., |
Workflow display name. |
Direction of synchronization |
Select the direction in which synchronization should take place.
|
Revision filteringMethod for accelerating synchronization. Only objects that have changed since the last synchronization are fully loaded and synchronized. RevisionHighest value of the revision countersInformation about the last change to a system object. The revision counter is used to determine the objects that have changed since the last synchronization. of all a schema type's objects that are synchronized during a synchronization run. This value is stored in the DPRRevisionStore table, in the Value column. It is used as a comparison value for revision filtering when the same workflow is synchronized the next time. filtering can only be used if the target system supports it. |
The revision filtering can be used to limit synchronization to just the objects that have been modified since the last synchronization. For more information, see How does revision filtering work?.
|
Error Handling |
Specify whether synchronization should be continued if an error occurs during processing of synchronization objects (adding, deleting, updating, and reloading objects). Object processing is continued using the next object; the error is logged. To optimize error localization, you can stop synchronization if an error occurs during the processing of synchronization objects. In this case, no further synchronization objects are processed. NOTE: This property does not affect configuration, network, or general synchronization errors (for example, if it is not possible to resolve a reference). The effectiveness of this property depends on the actual error, error position, the target system, and the implementation of the target system connectors.
|
Dependency resolution |
Specify how dependencies between synchronization step are resolved. For more information, see How does dependency resolution work?.
|
Description |
Text field for additional explanation. |
© 2024 One Identity LLC. ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center