So far we have created an approval process and added an approval step to it. We can specify the default actions that can happen when the record is: o Submitted: By default Force.com adds a new type of action to this step which is record lock. However, we can modify this action and unlock the record. This happens when a record is submitted for approval, possible action would be a field update for Status from Open to Under Approval. o Approved: These actions are executed when the record is approved in a step and is still in the approval process. Possible actions can be updating the status to Approved by XYZ or Under XYZ approval. o Rejected: These actions are executed when the record is rejected in a step and is still assigned to someone else. Possible action can be an e-mail alert to the submitter it has being rejected. o Finally approved: As with the submitted action, final approval of the record is also set to lock. It is recommended that the record remains locked to prevent the user from editing the approved record. These actions are executed at the end of the approval process when the record is finally moved out of it. Possible action can be updating the Status to Approved and e-mail alert to the submitter confirming the approval. o Finally rejected: Force.com provides us with a default action of unlocking the record once it is finally rejected. We can change it to lock. These actions happen when the record is finally rejected with comments from the rejecter.
Recall action: Force.com provides us with a default action of unlocking the record once it is finally rejected. We cannot change it. If the submitter has a change of heart once the record is submitted for approval he can recall the record. This is possible only if we set that the submitter can recall the record.
Question : If an approver rejects an approval request, then the final rejection actions are always executed.
Explanation: Represents what happens if the approver rejects the request during this approval step, unless it's the first step in the approval process. For the first step in the approval process, the reject behavior is determined by the approval process's final rejection actions. Field Name Field Type Description type StepRejectBehaviorType (enumeration of type string) Valid values are: " RejectRequest-Automatically rejects the request completely regardless of any previous steps that were approved. Salesforce performs all rejection actions specified for this step and all final rejection actions. " BackToPrevious-Automatically rejects the request and returns the approval request to the previous approver. Salesforce performs all rejection actions specified for this step. Not allowed in the first step of the approval process.
Question : New approval steps can be added to an active approval process only if it is deactivated
Explanation: Once you activate an approval process, you can not add or remove the approval steps even if you deactivate it. What I do, is clone the approval process and modify the name a bit. I add in the extra approval step(s) and then activate the cloned process