Initial Submission Actions are configured inside an existing Classic Approval Process. The record lock is created for you, so this is about adding the optional field updates, alerts, tasks, outbound messages, or flows that should fire when a record is first submitted.
- Open the approval process
In Setup, use Quick Find to open Approval Processes, choose the object, and click into the process you want to edit. Scroll to the Initial Submission Actions related list.
- Add an action
From the Add New picklist in the Initial Submission Actions section, pick the action type. You can add an existing action or create a new one inline, then save it back to the process.
- Stamp a status with a field update
Create a field update that sets your Approval Status field to Pending or Submitted. This makes the in-flight state visible to reports, list views, and other automation.
- Notify the approver with an email alert
Add an email alert that targets the first approver, using a template that merges in the key record details and a link to the approval screen. Optionally add a confirmation to the submitter.
- Set who can edit the locked record
On the approval process, set Record Editability to either Administrators only, or Administrators and the assigned approver, so the right people can still update the record while it waits.
Changes a field value at submission, most often setting an Approval Status field to Pending so the request is visible everywhere.
Sends a templated email when the record is submitted, typically to the first approver and sometimes a confirmation to the submitter.
Creates a follow-up task, for example reminding the submitter to chase the approval if it stalls.
Sends a SOAP message with record fields to an external endpoint, useful for mirroring the approval in a connected system.
Launches an autolaunched flow for richer logic, such as creating related records or calling an Apex action at submission.
Controls who can edit the auto-locked record, either administrators only or administrators plus the assigned approver.
- The record lock is automatic and implicit. If a submitted record will not save, check whether it is sitting in an open approval before hunting for other causes.
- Changing Record Editability only affects records submitted after you save the change, not approvals already in flight.
- The standard approval assignment email is separate from any custom email alert, so it is easy to send the approver two emails at submission.
- A flow launched at submission runs synchronously in the same transaction, so a slow flow delays the user who clicked Submit for Approval.