Committing Requests

Users assigned to the final Commit stage in the workflow model for a request must provide their approval to commit the changes in the request to the target version of data. During the Commit stage, all required values for all request items must be provided and all validations must pass. An approver can edit any request item to address remaining issues or make final adjustments. A committing user must approve all request items in a request. After the request is ready to be committed, the approver provides their approval to initiate the commit operation. If there are multiple approvers for the Commit stage, the last approval will trigger the commitment of changes in the request.

Note these transaction history details for committed requests:

• For auditing purposes, the final approving user of a request in the Commit stage is assigned to the transactions created in transaction history for the committed request items.

• In cases where a request may skip or be promoted in the Commit stage, the version or hierarchy owner is assigned to the transactions in transaction history.