An administrator is troubleshooting an Approval Process configured for a custom object named Project Request. Upon initial submission, an initial submission action is configured to lock the record. However, during testing, a sales manager who is assigned as the approver for Step 1 is still able to edit field values on the record while its status is 'Pending Approval'. System administrators wish to understand why this user can edit the locked record while non-approver submitters cannot. Which approval process configuration setting accounts for this behavior?
- The Approval Process Record Editability setting is configured to allow Administrators OR the currently assigned approver to edit records during the approval process.Cevap
- BThe record locking action was omitted from the Initial Submission Actions section during approval process setup.
- CThe sales manager's profile has the 'Modify All Data' permission, which completely disables approval locking mechanism triggers on custom objects.
- DThe Organization-Wide Default (OWD) sharing setting for the Project Request object is set to Public Read/Write, overriding approval locking.
Cevap
The Approval Process Record Editability setting is configured to allow Administrators OR the currently assigned approver to edit records during the approval process.
Salesforce Approval Processes feature a specific configuration property called Record Editability. When set to 'Administrators OR the currently assigned approver', the system allows the user assigned to the current approval step to edit the record even while it remains locked to all other non-admin users.
Adım Adım Çözüm
Anahtar Kavram
Approval Process Record Editability Settings