You can add an approval step to a process to prompt a user to approve or reject a case after reviewing the case details. By using approval steps, you can enforce business policies in your workflows.
On the Life cycle tab of Case Designer, hover over a process and click + Step.
In the palette that is displayed, click Approve/Reject.
Caution: An alternate stage named Approval Rejection is added to your case type. Do not delete or rename this stage because users will not be able to reject cases.
In the text field that is displayed, enter a unique name that describes the step.
Indicate how the approval step is routed at run time.
In the Approval flow type list, select Single level.
Click Specific user.
Select an option from the first list that is displayed to indicate how your application finds the specific user.
Select an option from the second list that is displayed.
This list is populated with either the names of users or user references, based on the selection you made in the first list.
In the Approval flow type list, select Single level.
Click Specific user.
Select Reporting Manager.
In the Approval flow type list, select Single level.
Click Work queue.
Select the name of a user role from the list that is displayed.
In the Approval flow type list, select Cascading.
In the Approval based on list, select Reporting structure.
In the Approval to be complete by list, select a manager who is the first person in the reporting structure to review the case.
Expand the Approval Level section and click an option to indicate how many approvals are required for each case.
One — Only the manager specified in the Approval to be completed by field must approve the case.
All — The entire reporting structure, starting with the manager specified in the Approval to be completed by field, must approve the case.
Custom — A variable number of reviewers must approve the case, based on a list of when conditions.
If the approval level is Custom, click Update custom levels and enter values in the When and Levels of approval fields.
For example, you can require approval by two managers in the reporting structure when a purchase order exceeds $25,000.
In the Approval based on list, select Authority matrix.
Optional: Enter the name of a decision table in the Decision table for matrix field that returns a list of reviewers.
In the Page list property field, enter the name of a page list that contains a list of reviewers.
Tip: If you do not provide a value in the Decision table for matrix, ensure that this page list is populated by other means, such as an activity or data transform, before the case is processed.
In the Approver property field, enter a single-value property that uniquely identifies the reviewers in the page list.
Click Flow.
Define the process for handling approved cases.
Select Continue from the If Approved then list.
Optional: Press the Down Arrow key in the Set status field and select a case status.
Select Change stage from the If Approved then list.
Select a stage name from the To list.
Optional: Press the Down Arrow key in the Set status field and select a case status.
Define the process for handling rejected cases.
Select Continue from the If Rejected then list.
Optional: Press the Down Arrow key in the Set status field and select a case status.
Select Change stage from the If Rejected then list.
Select a stage name from the To list.
Optional: Press the Down Arrow key in the Set status field and select a case status.
Select Resolve from the If Rejected then list.
Press the Down Arrow key in the Set status field and select a case status.
Optional: Define a goal and deadline for the assignment to ensure that it is processed in a timely manner.
Click Save.
At run time, an assignment is routed to the worklist of the user who last updated the case. You can change this default behavior by using more routing options in the contextual property panel.
Tip: Click Configure view to define the fields that are displayed when the assignment is processed.