Commit Policies

Commit policies provide a final review stage for a request during which all request items are reviewed and committed by a user specified in the commit policy in order to enforce a segregation of duties. While you can specify multiple users on a commit policy, only one commit action is required to fulfill each policy.

Note:

No changes to the request are allowed during the commit stage.

After all approval policies for a request are fulfilled, if commit policies are enabled for any of the request items, users configured in the policy are notified via email that they must review and commit the request in order to finalize the changes. Committers can also reject the request, which closes the request and sends a notification to the request submitter, or push the request back to the submitter so that the submitter can make edits and resubmit for approval and then committing.

Considerations

• Users who are listed on both an approval policy and a commit policy are invited to commit even after they have approved the request.
• Enrichment is not allowed during the commit stage, but you can add comments and attachments to the request.
• When a request is in the commit stage:
  • The request submitter can still recall the request, which moves the request back to the Submit stage with a status of Recall.
  • Request approvers can still withdraw their approvals, which moves the request back to the Approve stage with a status of In Flight.
• You can have multiple commit policies on a data chain object. The request is not completed until all commit policies are fulfilled.