Submit Action Set
Overview
The Submit action set is a series of actions in Commerce that are essentially sub-actions of Submit. The Submit action set is comprised of Submit, Request Approval, Approve, Reject, and Revise.
|
Initiate Approval
|
submit_t
|
Submit
|
Submits the transaction for approval. If no approvals are defined or triggered for the transaction, the status will move directly to the approved step.
|
|
Request Approval
|
request_approval_submit_t
|
Request for Approval
|
This action is performed when submit action is clicked and there is at least one reason to approve.
|
|
Reject
|
reject_submit_t
|
Reject
|
This action is performed when a reason is rejected by the approver.
|
|
Approve
|
approve_submit_t
|
Approve
|
This action is performed when a reason is approved by the approver.
|
|
Cancel Approvals
|
revise_submit_t
|
Revise
|
This action is performed when Revise button is clicked.
|
When does the Submit action run?
When the Submit button is clicked, the Submit action and its associated modifications do not necessarily run.
After Submit is clicked:
- The quote passes through the approval tree defined on the Submit action. If any of them return true, the Request Approval action will be performed first.
- Approvers receive notifications and the Approve and Reject actions are available to them until they have performed either action, at which time the actions will no longer be visible to them.
- When the quote has received its final approval, or if no approvals are required, the Submit action and its associated modifications run.
Plan your status modifications, step transitions, and integrations accordingly!
Submit Action Set Behavior
| Submit |
The Submit action decides if the quote needs to enter the approval sequence or can be automatically approved. Other times it runs each Modify action. |
-
The FullAccess user creates this action as a Main Document Submit type action.
- Click Edit Approvals to define a hierarchical list of reasons why a quote might have to be approved. Each of the reason will have an approver assigned to it.
- This action runs when a user clicks Submit in a quote.
- The admin typically defines a transition rule on this action to take the quote to the Approved Step. If there are reasons for which this quote needs to be approved, the Request Approval sub-action will run.
- The order of operations for a Submit action type is the same as that of a standard Modify action. At the end of the Advanced Validation, the reason rules are run to check if the quote needs any approval.
|
| Request Approval |
The Request for Approval action moves the quote into an approval pathway. It is automatically performed when the user clicks a Submit action and there is a Reason to approve the quote. |
- This action cannot be placed on a Commerce document.
- Auto-Submit option: If the Auto-Submit option is enabled, then all Quotes must go through the approval Process and the box doesn't show up on the user-side.
- You will typically define a transition rule to take the transaction to the Submitted for Approval step. If there are no reasons for which this quote needs to be approved, then the Submit action will run.
- No email notifications should need to be sent out by using the transition rule on this action.
|
| Approve |
This action is performed when the user clicks the Approve button. |
- Step transitions should not be defined on the Approve action.
|
| Reject |
This action is performed when any Reason for an approval sequence is rejected by an approver. |
- This action can be placed in a group view and made accessible to a user.
- This must be active in a Step for it to be executed.
|
| Revise |
The Revise action allows the user to revise a Transaction document that has been submitted for approval. |
- You will typically define a transition rule on this action to take the quote to a Pending step.
- Transition rules must be defined on this action for step change.
- See the section Revising a Sub-Action (Reset Reasons) below for more details.
|
Administration
Creating the Submit Action Set
- Navigate to the Admin home page.
- Click Process Definition in the Commerce and Documents section.
- Click on the applicable Commerce process.
- Select Actions from the Navigation drop-down for the main document, and then click List.
- Click Add at the bottom of the Actions List page.
- Enter a Label.
-
Enter a unique Variable Name.
The Variable Name field populates automatically. Variable names can only contain alpha-numeric characters and underscores. The entry can be changed before saving, but after saving the value is read-only.
- Select Submit from the Action Type drop-down.
- Click Add to save changes, or click Cancel to return to Action List without saving changes.
Notes:
- When you create a Submit type action, a Submit type action with four sub-actions (Request Approval, Reject, Revise and Approve) are added.
The Submit type action and each of the sub-actions can all be edited.- Edit the parent Submit type action to Edit Approvals and view associated submit attributes.
- Edit the Request Approval type action to enable Auto Submit. If the Auto-Submit option is enabled, then all Quotes must go through the approval process.
- Edit the Revise type action to manage Reset Reasons
- If a custom Submit action is deleted, all associated actions and attributes are also deleted. The Standard Process Submit action cannot be deleted.
Revising a Sub-Action (Reset Reasons)
Resetting of reasons is typically used when a quote is required to step through the entire Approval Sequence, or portions of the sequence, even if some of the Approvals have already been received. An approval reason has 4 statuses: Approved, Rejected, Pending or Ignored.
Resetting & Approval Statuses
- Resetting a Reason that is in Approved or Rejected: The reason was triggered and already received an approval (or rejection). Resetting the reason means it will be re-evaluated upon a Submit action and if the condition is met, an email notification will be sent and a new approval/rejection will be required.
- Resetting a Reason that is in Pending: The reason was triggered but was neither approved nor rejected. Resetting the reason means that it will be re-evaluated upon a Submit action and if the condition is met, an email notification will be sent and a new approval/rejection will be required.
- Resetting a Reason that is in Ignored: The reason was not triggered in the initial request, so resetting it has no affect.
- Navigate to the Admin home page.
- Click Process Definition in the Commerce and Documents section.
- Click on the applicable Commerce process.
- Select Actions from the Navigation drop-down for the main document, and then click List.
- Open a Revise type action.
- Click the Reset Reasons tab.
- Select one of the following:
Notes
- When setting transitions, try to use just one pending approval Step. Adding multiple Steps increases complexity. Instead, use a variety of participant profiles.
- Keep both the parent Submit action advanced modification and the sub-action "Submit for approval" advanced modification equivalent.
Related Topics
See Also