Save  | Saves the request to the Data Relationship Management repository in its current state without validating or approving the request This action is available for new requests and claimed requests. |
Submit  | Validates the request items in the request and if successful, assigns the request to the next stage in the workflow path This action is available for draft requests or requests that have been pushed back to the submitter. |
Calculate  | Calculates request item details based on proposed changes in the request |
Validate  | Validates proposed changes for request items in the request This action checks required values and runs batch validations configured for the task for the request item or the current workflow stage. Validation failures are returned for correction. Requests can be validated if: |
Copy  | Copies request items to a new request To copy a request, you must have access to submit the type of request you have selected. |
Claim  | Claims the request for the active workflow stage. A submitted request can be edited, pushed back, escalated, approved, or rejected only by a user who has claimed the request. When a user claims a request, the request is locked and cannot be claimed by any other user. The user must unclaim the request to release it to be claimed by another user. |
Unclaim  | Removes the claimed lock from the request but does not validate or assign the request to a different stage, user, or group If a user chooses to push back, escalate, approve, or reject the request, the request is automatically unclaimed. |
Pushback  | Pushes back the request to a previous user in the current stage or a previous stage to correct some element of a request or ask for more information about the request The user pushing back the request must provide a comment about why the request has been pushed back. |
Escalate  | Escalates the request to Data Manager role users Users may escalate a request for any number of reasons; for example, if they are unsure about what to do with a request or if they have access issues. Data Managers may resolve issues by adding comments to the request, changing the request items, modifying node access group assignment to hierarchies and nodes, or rejecting the request. |
De-escalate  | Reassigns the request to the next node access group for the current workflow stage |
Approve  | Approves and commits the changes in the request to the target version |
Reject  | Rejects the request A submitted request may be rejected by any approving user in the workflow path or a Data Manager during escalation. Rejecting a request terminates the workflow for the request. A rejected request cannot be resubmitted. To resubmit the request items in the rejected request, the original submitting user or another Submit stage participant can copy the rejected request to a new draft request, edit the request items in the new request, and then submit the new request. |