Run the Integrations

The integrations in this accelerator can be run from either the Oracle Integration or Primavera Unifier user interface.

Running the integrations in this order is required:
  1. Run Oracle OPC Unifier Resources Roles Sync first.
  2. Run Oracle OPC Unifier Activity Sync second.

    Running the second integration automatically triggers the Oracle OPC Unifier Activity and Assignment Spreads helper integration at the end of the run.

Note:

For both synchronizations to run successfully, all delivered integrations must be activated first (see Activate the Integrations).

Run 'Oracle OPC Unifier Resources Roles Sync'

  1. In the Integrations section of the project workspace, click Actions Actions icon on the integration, then select Run.
  2. On the Configure and run page, in the Request section, click the Body tab to enter the required JSON payload.
  3. Click Run and watch the Activity Stream / Tracking to verify success.

Request payload example: 

{
  "source": "Primavera Cloud",
  "unifierJobId": "3A0429936DD166A",
  "workspaceCode": "OPC-WORKSPACE-CODE"
}
Element Required Data Type Description
source Yes String Source application label used by the integration. Use: Primavera Cloud
unifierJobId No String Optional correlation ID for Primavera Unifier job tracking (when triggered from Primavera Unifier).
workspaceCode

No

 String Oracle Primavera Cloud workspace ID. If not provided (or empty), the integration syncs resources/roles from all workspaces the integration user can access.

Run 'Oracle OPC Unifier Activity Sync'

Note:

Before you run this integration, make sure Oracle OPC Unifier Resources Roles Sync has already run successfully first.

You can run the this integration in two ways:

Option A: Run from Primavera Unifier

Use this option when Primavera Unifier is configured to call the Oracle Integration endpoint.

The steps below describe how to configure Primavera Unifier to call the Oracle Integration endpoint, and then once configured, how to run the integration from Primavera Unifier.

  1. In Primavera Unifier, add and activate the integration.
    1. In the Company Workspace, select Admin mode
    2. In the left Navigator, select Integrations, and then Oracle Integration Cloud.
    3. On the Oracle Integration Cloud page, select the Integrations tab.
    4. Select System Activity Sheets, then select Add integration.

      1. In the Integration Name field, enter a name for the integration. For example, Oracle OPC Unifier Activity Sync.

        The name here can be, but it does not have to be the exact name of the integration, as named in Oracle Integration.

      2. In the API Path field, enter the API endpoint path of the Oracle OPC Unifier Activity Sync integration in Oracle Integration.

        To find this path, go to the Integrations section of the project workspace in Oracle Integration, click Actions Actions icon on the integration, select Run, then on the Configure and run page, copy the endpoint path at the top of the page.

        For example:

        /ic/api/integration/v2/flows/rest/project/ORCL-BA-OPC_TO_UNIFI_INTEG/<integration-id>/<version>/sync/activities
    5. Click Activate.
  2. In Primavera Unifier, assign the integration to the System Activity Sheet.
    1. Open the project and select Admin mode.
    2. In the left Navigator, expand Setup and select Activity Sheets.
    3. On the Activity Sheets page, for System Activity Sheet – Get, click Select an Integration, then select the integration from the list.
    4. Click Save.
  3. Run the synchronization.
    1. Open Activity Sheets, and then System Activity Sheet.
    2. Click Get Data into Activity Sheet.
    3. Select the current project and choose optional flags:
      • Synchronize baseline projects (include baseline data)
      • Remove unreferenced data (full refresh behavior - remove records in Primavera Unifier that no longer exist in Oracle Primavera Cloud)

Option B: Run from Oracle Integration

  1. In the Integrations section of the project workspace, click Actions Actions icon on the integration, then select Run.
  2. On the Configure and run page, in the Request section, click the Body tab to enter the required JSON payload.
  3. Click Run and watch the Activity Stream / Tracking to verify success.

Request payload example: 

{
  "opcProjectCode": "OPC-Proj-001",
  "opcWorkspaceCode": "OPC-WORKSPACE-CODE",
  "performRecostingAutomatically": true,
  "removeUnreferencedData": true,
  "synchronizeBaselineProjects": false,
  "unifierJobId": "3A0429936DD166A",
  "unifierProjectNumber": "UNIFIER-Proj-001"
}
Element Required? Data Type Description
opcProjectCode Yes String The Oracle Primavera Cloud project ID to sync.
opcWorkspaceCode Yes String The Oracle Primavera Cloud workspace ID for the project.
performRecostingAutomatically No Boolean If true (default), triggers Primavera Unifier project recosting after spreads complete successfully. Set to false to manage recosting manually in Primavera Unifier.
removeUnreferencedData Yes Boolean If true, removes records in Primavera Unifier that do not exist in Oracle Primavera Cloud (primarily WBS/Activities/Assignments), making the target a 1:1 copy.
synchronizeBaselineProjects Yes Boolean If true, also syncs the current baseline project from Oracle Primavera Cloud.
unifierJobId No String Optional correlation ID for Primavera Unifier job tracking (if triggered from Primavera Unifier).
unifierProjectNumber Yes String Primavera Unifier project number to sync to.

Run the Integrations Using the REST API (optional)

Use this method if you prefer to invoke integrations using REST instead of the Oracle Integration or Primavera Unifier user interface.

  1. In the Integrations section of the project workspace, click Actions Actions icon on the integration, then select Run.
  2. On the Configure and run page, click the Endpoint Metadata tab.
  3. Copy the Endpoint URL and review the Resource information (HTTP method, request/response schemas). Use this with your REST client (Postman/curl). Oracle also supports publishing OpenAPI documents for REST-triggered integrations for easy client import.