Configure approval processes, including entry criteria, approval steps, approvers, and the field updates and actions that fire on approval or rejection.

What is the purpose of a final approval action in an approval process, as distinct from a final rejection action?

• AIt defines the entry criteria that a record must satisfy before it can be submitted into the approval process at all.
• BIt specifies which fields the approver is permitted to edit on the record while the request is still pending.
• CIt runs the field updates, email alerts, and other actions that fire once the record has been fully approved.check_circle Correct
• DIt reassigns the pending request back to the previous step so the earlier approver can reconsider the decision.

Why A is wrong: Entry criteria control whether submission is allowed, which is a separate setting; final approval actions fire after a decision, so this confuses the two stages.

Why B is wrong: Editable fields for approvers are controlled elsewhere in the step and page layout, not by final actions, so this misplaces the setting.

Why C is correct: Final approval actions execute after the last required approval, and they typically unlock the record and set a status field, distinct from final rejection actions that fire on a rejected request.

Why D is wrong: Routing back to a prior step is rejection-behaviour on a step, not a final approval action, so this describes a different mechanism.