A Salesforce Administrator is setting up an Approval Process for a custom object named Capital Expenditure Request. The business process requires that as soon as a user submits a record for evaluation, the custom Status field must automatically change to 'Submitted' and the record must be locked from editing by non-administrator users. Which configuration settings in the Approval Process satisfy these requirements?
- The Approval Process automatically locks the record upon submission based on the process configuration, and an Initial Submission Action must be configured to update the Status field.Answer
- BAn Initial Submission Action must be explicitly created to lock the record, alongside a separate Initial Submission Action to update the Status field.
- CThe record locking must be configured within the first Approval Step entry criteria, while the Status field update must be triggered via an external Record-Triggered Flow.
- DA Final Approval Action must be defined to lock the record, while an Approval Step action updates the Status field prior to approver assignment.
Answer
The Approval Process natively manages record locking upon submission based on process properties, while changing the custom Status field requires an Initial Submission Action of type Field Update.
When a record is submitted into an approval process, Salesforce automatically locks the record according to the process editability settings (allowing either administrators only or administrators and assigned approvers to edit). Field changes triggered upon submission—such as changing a status picklist—are configured using Field Updates in the Initial Submission Actions section.
Step-by-Step Solution
Key Concept
Approval Process Initial Submission Actions and Record Locking Framework