UNIFYNow Changes Operation Usage Considerations

Due to the nature of the MIM Portal, a few things should be considered with regards to operation of the UNIFYNow Changes Activity:

  • The workflow will attempt to run the UNIFYNow operation list the instant the workflow is enacted.
  • Ensure the activity is configured on an Action Workflow to ensure the operation list is instigated as late in the processing of an object as possible.
  • In the interest of ensuring optimal performance and minimal clutter in the Portal, the changes activity does not maintain state. The success or failure of the executed operation list can be determined by examining the UNIFYNow logs around the time the request has been marked as "Complete".
  • Synchronization rule changes require full synchronization in order to take full effect in the Synchronization Server, and as such should be configured differently as explained in Configuring the UNIFYNow Changes Activity

Given the nature of the workflow, it may be possible in environments of high Portal activity for latter operations to be missed if an import occurs before all changes have successfully registered in the Portal. This can be addressed by marking the operation lists for incoming and outgoing operations as Queue Missed, meaning that changes and workflows that complete execution while an import is already running will be picked up on a subsequent import run. It is also advised that these operation lists are placed in the same Exclusion Group, allowing for appropriate action to occur as events complete. To avoid multiple concurrent calls to the workflow resulting in multiple runs of the operation list, ensure that the delay setting is configured to a number larger than the typical gap between calls.

It is recommended that UNIFYNow logs and the MIM run history are regularly monitored for any messages pertaining to failures in pulling changes from the MIM Portal.

Is this article helpful for you?