Introduction

Oracle Fusion SaaS applications, such as HCM and ERP, provide the ability to approve certain transaction before they are committed. The rules behind these approvals are exposed to customers through Transaction Console or BPM worklist applications. If necessary, customers can modify conditions of approval rules or add new rules to the rulesets for a transaction. Customers can also configure various aspects of approvals, such as the approval groups, approval exceptions and notifications.

Approval capabilities in Oracle Cloud Applications, on purpose, do not include complex BPM capabilities. For example, approval rules can use data accessible within the SaaS application, but are not allowed to an external API to fetch data from another application. They also do not permit complex logic such as iteration. Also note that certain SaaS applications, for example, Oracle Sales Cloud, do permit more complex BPM processes through application composer. Refer to product-specific documentation for more information.

Occasionally, customers might need to externalize approval processes, either because of the complexity of the desired approval processes or because of other reasons such as dependency on external approvers who cannot be granted access to customers’ SaaS applications. Read the complete article here.

PaaS Partner Community

For regular information on Oracle PaaS become a member in the PaaS (Integration & Process) Partner Community please register here.

Blog Twitter LinkedIn Facebook Wiki

Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress