PEX Network’s key takeaways:
- Oracle Integration 26.01 is now available with new process enhancement features.
- New capabilities improve process lifecycle management tasks and the user experience.
- Updates include unified identity application, the ability to remove process automation, and process instance tracking changes.
The 26.01 release of Oracle Integration is now available, bringing new process enhancement features.
The new capabilities are designed to deliver improvements to process lifecycle management tasks and the user experience across instance tracking. They include unified identity application, the ability to remove process automation, and process instance tracking updates as well as request withdrawal and task reassignment changes.
Unified identity application in Oracle Integration
New process instances provisioned through Oracle Integration no longer have a separate identity application, according to the release announcement. This will remove additional configuration requirements needed to access the service and eliminate the ongoing burden of role membership synchronization.
Existing instances created prior to this release will not be affected. They will continue to use a separate identity application for process.
What changes:
- No separate process application: Newly provisioned process instances share the Oracle Integration identity application. Users will no longer see a separate process automation application listed under Oracle Cloud Services.
- Unified scopes: When users enable process automation, the Oracle Integration identity application automatically updates to include the process instance as a secondary audience and process and decision scopes
- Single authentication: This configuration allows authorization tokens to cover both integration and process services, enabling seamless authentication across the entire platform.
Disabling process automation from Oracle Integration
Users now have the flexibility to remove process automation from Oracle Integration instance when needed. Oracle said this capability is particularly useful when users want to:
- Downgrade to standard edition.
- Replace a process instance as part of the standalone EOL migration.
“If needed, you can re-enable process automation at any time from the same location, by clicking enable,” wrote Stan Tanev, product manager – OCI Process Automation (OPA).”This will provision a fresh process instance with no data from the previous instance.”
Register for All Access: Future of BPM 2026!
Process instance tracking in Oracle Integration
The process instance tracking page in the OPA Workspace is now organized into two focused tabs, making it easier for users to find what they are looking for.
How it works:
Instance tracking is now divided into two views based role and needs:
- Started by me: Shows instances started by the logged in user. This view is designed for requestors who want to check the status of their own process instances – perfect for tracking expense reports, approvals, or any workflows you’ve submitted.
- Managed by me: An administrative view showing all instances a user has manage permission on. This is designed for process administrators who need visibility into the state of all instances within a process application.
Withdrawing requests and reassigning tasks in Oracle Integration
Requestors can now terminate their own process instances directly from the tracking page with no administrator involvement required. This added flexibility allows users to withdraw requests when circumstances change, such as canceling a travel request or closing an outdated approval.
Previously, terminating a process instance was limited to users with manage permission. With this update, requestors are empowered to take full control of their own submissions.
Finally, process administrators can now reassign tasks even when they’re in a “request info” state – eliminating workflow bottlenecks when task assignees are out of office.
Previously, when additional information was requested from a user, and that user went on leave, the workflow would stall. Process admins had no direct way to reassign the task to someone else that could take action, but users with manage permission can now use the standard reassign action on tasks in the request info state, just as they would with any other task.
Image credit: Oracle