Normally, an Active Roles Approval Workflow will execute before an Active Roles Policy. This can result in inconsistent results when the operations performed by a policy are needed by an Approval Workflow.
For example, a policy script might compute a Virtual Attribute value which needs to be embedded inside an Approval Notification token. Normally, this would work on the very first attempt, but subsequent attempts would only retrieve old values and not new values.
This is expected functionality by default.
It is possible to modify a specific Active Roles Policy so that it executes before an Active Roles Approval Workflow.
On the desired Active Roles Policy object, set the edsvaPrecedeWorkflowActivities to TRUE
When this attribute is set to TRUE on a Policy Object, the policies held in that Policy Object have precedence over any workflow activities. Otherwise, policies take effect after completing all workflow activities that precede the execution of the change request.
If the Active Roles Policy contains a Policy script, also disable the Wait while post-event handlers complete operation checkbox on the script module selection screen.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center