Step 6: Creating Request Templates

Understanding Approval Process Development in Oracle SOA Suite 24-3 – One or more rulesets. There are specific business requirements that must be met when fulfilling requests. SOA composites leverage Oracle Business Rules to satisfy these requirements. A collection of rules developed by using Oracle Business Rules is called a ruleset. A composite can have one or more rulesets. Human tasks can also leverage these rules to determine the participants and the task routing. For information about how to design human tasks, see Oracle Fusion Middleware Developers Guide for Oracle SOA Suite. ■ A certified version of JDeveloper, for example, JDeveloper 11.1.1.3. ■ The SOA Design Time, also known as the SOA Composite Editor Extension for JDeveloper.

24.2 Predefined SOA Composites

Table 24–1 lists the predefined SOA composites in Oracle Identity Manager that can be used as approval processes. Note: In most approval scenarios, the composite contains only one human task. In some instances, additional human tasks may be required if the routing rules cannot be satisfied by using Oracle Business Rules. For example, the composite for resource request type contains multiple human tasks, one per resource. As a best practice, you must try to streamline the approval rules to facilitate reuse of the composites and human tasks. Table 24–1 Predefined Workflow Composites Workflow Composite Description DefaultRequestApproval This is the default request-level approval. By default, the request-level approval goes to the System Administrator, xelsysadm, for request-level approval. DefaultOperationalApproval This is the default operation-level approval. By default, the approval task is assigned to the System Administrator, xelsysadm, for operation-level approval. BeneficiaryManagerApproval This acquires approval from the beneficiarys manager. This can be associated with the following: ■ The request types that have a beneficiary. Examples of such request types are Provision Resource and Assign Roles. ■ All user models except Create User and Self-Register User. This composite must be associated at the operational level of approval because a request can have multiple beneficiaries at the request level. DefaultRoleApproval This SOA composite creates a single approval task that is assigned to the SYSTEM ADMINISTRATORS role for approval. RequesterManagerApproval This SOA composite creates a single approval task that is assigned to the requesters manager for approval. Note: This cannot be associated with unauthenticated request types, such as Self Register User.