Summit Financial Services utilizes a two-step approval process for custom Purchase Order records. Step 1 requires direct manager approval for all purchase orders. Step 2 requires executive vice-president approval only if the total order amount exceeds 25,000 purchase order. The manager approves Step 1, but the system immediately marks the purchase order as Rejected instead of Approved. What is the root cause of this unexpected rejection?
- The entry criteria for Step 2 evaluated to false, and the step configuration was set to perform the 'else' action of rejecting the record.Cevap
- BThe initial submission actions failed to lock the record, causing the workflow engine to reject the record automatically upon step transition.
- CThe approval process final approval actions were not defined, causing Salesforce to default to the final rejection actions.
- DThe executive vice-president profile lacks Object-Level Read permissions on Purchase Orders, triggering an automatic system-level rejection.
Cevap
The step entry criteria for Step 2 evaluated to false, and the step was configured to reject the record when criteria are not met.
In a multi-step approval process, each step defines what happens if a record does not meet its entry criteria. The options are 'Go to the next step', 'Approve record', or 'Reject record'. Because the purchase order was under $50,000, it skipped Step 2 criteria. Since the step was misconfigured to 'Reject record' on criteria failure, Salesforce rejected the purchase order despite passing Step 1.
Adım Adım Çözüm
Anahtar Kavram
Approval Step Entry Criteria Fallback ('Else' Routing)