With the evolution of business processes and compliance, companies are emphasising on documents and approvals. Many applications use Approval Management Extension (AMX) for approvals. With Oracle BPM AMX, you can define approval rules based on your business processes and decisions, such as whether to route documents to approvers in series or parallel and whether approvals should be based on employee supervisory hierarchy, position hierarchy, job levels, or Approval Groups. The approval tasks are defined in Oracle JDeveloper's Human Task editor and approvals are managed in BPM Worklist applications or BPM Workspace applications. You used BPM Workspace in this book and will be using the same application for AMX too.
The following are the key elements that are involved in understanding and setting up approval routing rules:
Your business requirement is to generate approvers list dynamically. They have a basic business fulfillment to be taken care of, based on the industry type, and then as per business defined logics, a list of approvers will be generated. The business needs to incorporate the following logic to derive approvers dynamically:
If Industry IS 'Sales' Then Approvers are - Salesbusinessanalyst1 and Salesbusinessanalyst2 If Industry IS 'IT' Then Approvers are - ITbusinessanalyst1 and ITbusinessanalyst2 Else Approvers are - businessanalyst and businessanalystmanager
To generate a list dynamically, the process needs to interact with the enterprise database. The enterprise database would have a procedure defined to take care of logic and to return approvers list. To fulfill the business requirement, you have to follow the ensuing steps:
You have defined user hierarchy in the Defining assignments—powerment, and business alignment. What make management chain participant section in Chapter 5, Human Workflow in BPM Process. Ensure that following users are created in security realm in Oracle SOA or are available in your identity management solution:
3.17.79.206