Custom Approver Logic in BPM – Validating User Email/Access via BIP or Alternative Approach

Summary:

In Oracle Fusion BPM, approval routing is typically based on predefined rules such as user, supervisory hierarchy, AOR, or role.

However, we have a requirement for more dynamic logic that standard BPM configuration does not seem to support.

Our requirement is as follows:

• Validate whether the selected approver (derived from the supervisory hierarchy) has a valid email address and an active user account.
• If the approver is not valid, the system should automatically move up the supervisory hierarchy and select the next valid approver.

We are exploring whether this validation can be implemented by leveraging a BI Publisher (BIP) report within the BPM approval process. The idea is to pass input parameters to BIP, apply the validation logic there, and return the appropriate approver back to BPM.