Complete Post-Upgrade Tasks for Process Automation

Perform the following steps to complete migration to Process Automation in Oracle Integration 3.

Application-Level Post-Upgrade Tasks for Process Automation

Perform the following tasks for each Process application.

Task Who When Details

Update role mappings

Developer/Administrator Immediately after upgrade Role assignments have changed in Oracle Integration 3, so you must map your existing roles to the new roles. See Configure Roles for Process Applications in Using Oracle Cloud Infrastructure Process Automation.

Process owners

Add members who had the following roles to the Process Owner role in the new application:

  • <application-name>.ProcessOwner
  • <application-name>.AnalyticsViewer
  • auto-handler for the swim-lane

Process reviewers

Add members who had the <application-name>.ProcessReviewer role to the Process Reviewer role in the new application.

Members with swimlane roles

Add members who had a swim-lane role to the role assigned to the swimlane in the new application.

Groups

Change the old group to a role in the new application, and either add the group to the new role or add the members of the group to the new role.

Roles

Change the old role to a role in the new application, and add members to the new role.

Members who can start a process

In the process start properties, select the members who can start the process from one of the following options:

  • Role members with at least Use permission: Allows any user assigned a role with Use or Manage permission to see and start the application. Note that in a structured process, a user does not need to be assigned to the swimlane to start the process.
  • All users and external applications: Allows any user or external application with access to Process Automation to see and start the application.

Dynamic process roles

Add members who had dynamic process roles to the dynamic process roles in the new application.

Update connector credentials

Developer/Administrator Immediately after upgrade Credentials aren't migration to Oracle Integration 3, so you must reconfigure authentication for your REST connectors. If there are multiple applications connecting to the same server you may want to create a global credential that can then be reused across applications. See Configure Basic Auth Security in Using Oracle Cloud Infrastructure Process Automation.

Fix any errors and warnings

Developer/Administrator Immediately after upgrade Because there are differences in process features between Oracle Integration Generation 2 and Oracle Integration 3, you'll need to validate your application and fix any errors or warnings. See "How are applications validated?" in Applications at a Glance in Using Oracle Cloud Infrastructure Process Automation.

Activate application

Developer/Administrator Immediately after upgrade After you've resolved all validation errors, activate your application so new instances can be triggered and worked on. See Activate Applications in Using Oracle Cloud Infrastructure Process Automation.

Access Mapping Post-Upgrade Tasks for Process Automation

Some access mapping tasks are completed automatically during upgrade and some are your responsibility.

The following Oracle Identity Cloud Service (IDCS) roles are automatically mapped from Oracle Integration Generation 2 to Oracle Integration 3 during upgrade.

Oracle Integration Generation 2 Oracle Integration 3
ServiceDeveloper ServiceDeveloper
ServiceAdministrator ServiceAdministrator
ServiceUser N/A
ServiceMonitor N/A
ServiceDeployer ServiceDeployer
ServiceViewer N/A
ServiceInvoker N/A
ServiceEndUser N/A

Service-Level Post-Upgrade Tasks for Process Automation

Depending on how you use Process, you'll perform different service-level steps after upgrade to Oracle Integration 3. Perform any steps that apply to your implementation.

Task Who When Details

Allowlist the new Process Automation URL

Developer Immediately after upgrade

Add the new Process Automation URL to your allowlists. To find the new URL, click Process in the Oracle Integration 3 menu. You'll be redirected to the Process Automation URL.

Update integrations to call Process Automation

Developer Immediately after upgrade

Process APIs and endpoints have changed after the upgrade. As a result, you must update any integrations that use the Process action to use the REST adapter instead. See REST API for Oracle Cloud Infrastructure Process Automation.

Update Visual Builder applications to call Process Automation

Developer Immediately after upgrade

Process APIs and endpoints have changed after the upgrade. As a result, you must update any Visual Builder application that calls Process, replacing any deprecated interaction patterns. See Connect to Oracle Process Automation APIs in Building Responsive Applications with Visual Builder Studio.

Update external clients to call Process Automation

Developer Immediately after upgrade

If you're using Process CCA components in external applications, they won't work after the upgrade to Oracle Integration 3. You must transition to using the new Process Automation CCA components to leverage the APIs. See REST API for Oracle Cloud Infrastructure Process Automation.

Share the new Process Automation URL

Administrator Immediately after upgrade

The URL used to access and interact with Process Automation has changed after the upgrade. Share the new URL with anyone who needs to administer Process Automation, start a new process, or view and act on their tasks.