Enable Process Automation and Human in the Loop in Oracle Integration

Before you can use Process Automation or human in the loop in Oracle Integration, complete a few tasks, including enabling these technologies.

Workflow

  1. Set Up IAM Policies to Manage Process Automation Instance
  2. Enable Process Automation and Human in the Loop
  3. Assign IDCS Application Roles to Manage Access

Learn more about Process Automation

See Using Oracle Cloud Infrastructure Process Automation.

Key Points

When enabled, a Process Automation instance gets automatically provisioned with the Oracle Integration instance. In such a case, the two services become associated with each other and gets listed in each others Associated services page in the Oracle Cloud Console.

Keep in mind the following key points about enabling Process Automation with Oracle Integration:
  • You can enable Process Automation and human in the loop only with Oracle Integration 3 Enterprise Edition.
  • You must ensure that the user who enables Process Automation and human in the loop with Oracle Integration must exist in the identity domain of the Oracle Integration instance and must have MANAGE permissions on Process Automation.
  • You must ensure that you've set up the correct IAM policies to manage access to the Process Automation instance. See Set Up IAM Policies to Manage Process Automation Instance.
  • A Process Automation instance provisioned with Oracle Integration cannot be deleted independently. Such an instance is deleted whenever the Oracle Integration instance with which it is associated is deleted.
  • A Process Automation instance provisioned with Oracle Integration must be in the same tenancy, region, and compartment as the Oracle Integration instance. You cannot move the instance to a different compartment.

Set Up IAM Policies to Manage Process Automation Instance

To enable Process Automation and human in the loop with Oracle Integration, you need to create Oracle Cloud Infrastructure Identity and Access Management (IAM) policies that allow Oracle Integration administrators belonging to a specified IAM group to manage the Process Automation instance.

Set up the following IAM policies for Process Automation and human in the loop:

  • Syntax: allow group <group_name> to manage process-automation-instances in compartment <compartment_name>

    Example: allow group domain_admins to manage process-automation-instances in compartment oicpa_compartment

  • Syntax: allow group <group_name> to read metrics in compartment <compartment_name>

    Example: allow group domain_admins to read metrics in compartment oicpa_compartment

  • Syntax: allow group <group-name> to use tag-namespaces in tenancy

    Example: allow group domain_admins to use tag-namespaces in tenancy

See IAM Policies for Process Automation.

For information on IAM policies for Oracle Integration, see About IAM Policies for Oracle Integration and Create an IAM Policy in an Identity Domain for Oracle Integration in Provisioning and Administering Oracle Integration 3.

Enable Process Automation and Human in the Loop

To enable a Process Automation instance with an Oracle Integration instance:
  1. Open the navigation menu and click Developer Services. Under Application Integration, click Integration.
  2. From the Compartment drop-down list, select the compartment in which you want to provision and enable a Process Automation instance with an Oracle Integration instance.
    The page is refreshed to show any existing service instances in the selected compartment.
  3. Choose an existing instance or create an Oracle Integration instance and select it.
    The Integration instance details page opens.
  4. On the Integration Details tab, below Settings, find the Human in the Loop entry, and select Enable.
  5. When prompted, click Enable to confirm the action.
    Note the following:
    • The Oracle Integration icon turns orange and its status changes to Updating.
    • It can take several minutes for the enablement to complete.
    • After the Process Automation instance gets enabled and provisioned with the Oracle Integration instance, the Oracle Integration icon changes back to green with an Active status, and Enabled appears for the Human in the Loop setting.
  6. To navigate to the Process Automation instance that just got created, click Associated services under Resources.
  7. Select the Process Automation instance and view its details.

Assign IDCS Application Roles to Manage Access

After you've enabled an Process Automation instance, assign predefined IDCS application roles to users so that they can work with the features of the Process Automation instance.

In Process Automation, there are two predefined IDCS application roles: ServiceDeveloper and ServiceAdministrator. These roles have to be assigned to users or groups in the Process Automation service instance application from the Oracle Identity Cloud Service (IDCS) admin console.

Note:

The user who enables Process Automation and human in the loop with Oracle Integration is automatically granted the ServiceAdministrator role.

  • ServiceDeveloper: Any user who wants to access and work on Process Automation Designer has to be assigned the ServiceDeveloper role.

  • ServiceAdministrator: Any user who wants full administrative privileges within Process Automation including administrative tasks in Workspace has to be assigned the ServiceAdministrator role.

Note:

From January 2026 release, any newly provisioned Oracle Cloud Infrastructure Process Automation instances do not have a process specific identity application. However, the new Process Automation instances use the identity application used by Oracle Integration. To work in Process Automation Designer, users need access to ServiceDeveloper role in Oracle Integration. To use the administration capabilities of Process Automation Workspace, users need access to ServiceAdministrator role in Oracle Integration.

If a user in Oracle Integration has ServiceDeveloper and ServiceAdministrator roles, then the user has by default access to process components when a new Process Automation instance is provisioned.

As a best practice, it is recommended that you assign these roles to groups, rather than individual users. For example, assign the ServiceDeveloper IDCS application role to a group in both the Oracle Integration and Process Automation service instance applications from the Oracle Identity Cloud Service admin console. In this way it will be easier to manage user access, as any user who is a member of the group can access the Oracle Integration and Process Automation design-time.

For information on how to assign IDCS application roles, see Assign Oracle Integration Roles to Groups in an Identity Domain.

Now that a Process Automation instance is enabled and provisioned with an Oracle Integration instance, and IDCS application roles assigned, you can:
  • Open the Process Automation Designer and Workspace user interfaces using the Designer and Workspace URLs displayed on the Details tab of the Process Automation instance details page.
  • Open Oracle Integration by clicking the Service Console button from the Oracle Integration instance details page. From the navigation menu in the Oracle Integration home page, click the punch out URL for Process Automation. The Process Automation Designer opens in another browser tab and you can start designing your process applications.

Disable Process Automation and Human in the Loop

If you want to stop use of Process Automation or human in the loop and delete the associated instance, a service administrator can remove these features from the Oracle Integration instance.

You can perform this action if you want to downgrade to a Standard Edition or replace your process instance as part of the Standalone EOL migration.

Note:

After disabling these features, a service administrator can click Enable to re-enable Process Automation and human in the loop at any time. However, Oracle Integration provisions a new instance with no data from the previous instance.

Caution:

If you are using processes or human in the loop in any way, including calling them from integrations, do not disable human in the loop. Disabling human in the loop permanently deletes your Process Automation instance and all its runtime data, including human in the loop. This action can't be undone.

Before disabling, back up any necessary information.
  1. In the Oracle Cloud Console navigation menu, click Developer Services, then, under Application Integration, click Integration.
  2. From the Compartment drop-down list, select the compartment to locate and access the Process Automation instance with an Oracle Integration instance.
    The page refreshes to show any existing service instances in the selected compartment.
  3. Select the required Oracle Integration instance.
    If you don't see the instance you're looking for, make sure you're viewing the correct region (in the banner) and compartment (at the top of the instance list, next to Applied filters).
    The Integration instance Details tab opens.
  4. On the Integration Details tab, below Settings, find the Human in the Loop entry, and select Disable.

    Caution:

    Disabling human in the loop permanently deletes your Process Automation instance, including all processes and human in the loop. If you later re-enable human in the loop, a new Process Automation instance is created with no data from the previous instance.

    A confirmation dialog appears.
  5. Select Diasable and delete.
    The process instance and all of its associated data are deleted.