Approvals
Approvals centralize decisions that must happen before a Request or Price Offer can continue. Reviewers see the items waiting for them, while submitters can track the workflow and its decision history.
Supported records
Section titled “Supported records”Approval workflows currently support:
Review approvals
Section titled “Review approvals”Open Approvals from the Operations section. The page has two tabs:
| Tab | Purpose |
|---|---|
| Pending My Approval | Records waiting at a step assigned to the current user |
| My Requests | Approval requests submitted by the current user |
A pending approval shows the module, workflow, current step, and submission date. Open the source record to review its details, then select Approve or Reject. Add comments that explain the decision, especially when rejecting.
My Requests shows the current status, completed date, and action history. A rejected item can be resubmitted after the source record has been corrected.
Configure a workflow
Section titled “Configure a workflow”Open Settings → Approvals and select the Price Offers or Requests tab.
Each workflow defines:
- name and description
- module
- optional matching conditions
- active or inactive state
- order relative to other workflows
- one or more sequential approval steps
Conditions can use module-specific fields and operators. For example, a Price Offer workflow can route by value or currency, while a Request workflow can route by request type, submitter, or department.
Workstation evaluates active workflows in order and uses the first one whose conditions match. Put narrow, high-priority rules before broad fallback rules.
Configure approval steps
Section titled “Configure approval steps”Each step has a name and one or more specific user approvers. A step can also allow the approver to edit the source record and can send email notifications.
Steps run sequentially:
- The first step’s approvers are notified.
- An approval advances the request to the next step.
- The final approval marks both the approval request and source record approved.
- A rejection ends the current approval request and marks the source record rejected.
The submitter is notified of the final decision, and the next approvers are notified as the workflow advances.
Records without a matching workflow
Section titled “Records without a matching workflow”When a submitted Request or Price Offer does not match an active workflow, it does not wait in the Approvals queue. The module continues using its no-workflow behavior, which normally means automatic approval.
Before activating a broad workflow, test one matching and one non-matching record so the fallback behavior is clear.