In some of the recent articles we studied about Workflow and how to set them up in Force.com platform. The other part of workflow is Approval Process. Workflow is triggered when a record is added or updated. Approval process is triggered when the user manually clicks on 'Submit for Approval' button.
An approval process consists of steps and actions. An approval process is a sequence of steps that finally declare the record as approved. You can also define who must approve at each step. Thus, by defining approval process, records that need different approvals are submitted to the right people at the right time. And just like workflows, we can setup actions as part of the approval process as well.
An approval process consists of the following -
1. Process Definition - Process definition contains Name and Description. Entry Criteria can be specified here for setting a filter to find the records for which you are applying the approval process. You can specify the user for automated approval routing for approval steps and also specify if the approver along with the administrator can edit records that are pending approval. Email template can be specified to use for notifying approvers. The approval page can be designed to display appropriate details for approver to see while approving. You can specify initially who can submit the records for approval.
2. Initial Submission Actions - You can specify actions to execute when a record is initially submitted for approval. Actions could be Task, Email Alert, Field Update or Outbound Message.
3. Approval Steps - You can define one or more approval steps in the approval process. Approval steps are numbered that determines the order. Entry criteria can be specified for each step allowing records to enter that step only if it meets the criteria. You can specify who should approve the records that are in this step. For each step you can specify approval and rejection actions.
4. Final Approval Actions - You can specify actions to execute at the end of the approval process, that is after the record has passed all the necessary steps and approved.
5. Final Rejection Actions - Just like final approval actions, you may specify rejection actions to indicate what must happen if rejected.
6. Recall Actions - An approval request can be recalled. Hence you could specify actions to execute if recalled.
As you can see, the Force.com platform lets us cover all the possibilities. As you can also imagine, how quickly an approval process can get too complicated, a through planning and designing is a must before we venture into setting up approval process.
Happy cloud computing using Salesforce!
An approval process consists of steps and actions. An approval process is a sequence of steps that finally declare the record as approved. You can also define who must approve at each step. Thus, by defining approval process, records that need different approvals are submitted to the right people at the right time. And just like workflows, we can setup actions as part of the approval process as well.
An approval process consists of the following -
1. Process Definition - Process definition contains Name and Description. Entry Criteria can be specified here for setting a filter to find the records for which you are applying the approval process. You can specify the user for automated approval routing for approval steps and also specify if the approver along with the administrator can edit records that are pending approval. Email template can be specified to use for notifying approvers. The approval page can be designed to display appropriate details for approver to see while approving. You can specify initially who can submit the records for approval.
2. Initial Submission Actions - You can specify actions to execute when a record is initially submitted for approval. Actions could be Task, Email Alert, Field Update or Outbound Message.
3. Approval Steps - You can define one or more approval steps in the approval process. Approval steps are numbered that determines the order. Entry criteria can be specified for each step allowing records to enter that step only if it meets the criteria. You can specify who should approve the records that are in this step. For each step you can specify approval and rejection actions.
4. Final Approval Actions - You can specify actions to execute at the end of the approval process, that is after the record has passed all the necessary steps and approved.
5. Final Rejection Actions - Just like final approval actions, you may specify rejection actions to indicate what must happen if rejected.
6. Recall Actions - An approval request can be recalled. Hence you could specify actions to execute if recalled.
As you can see, the Force.com platform lets us cover all the possibilities. As you can also imagine, how quickly an approval process can get too complicated, a through planning and designing is a must before we venture into setting up approval process.
Happy cloud computing using Salesforce!
No comments:
Post a Comment