Set Up Partner Integration Provisioning

To use a partner's service, the Recruiting Administrator needs to provision and activate a supported integration. The list of supported integrations is published on Oracle's Cloud Marketplace.

Here's what to do:

1. Configure the Integration
2. Provide User Account Credentials
3. Export and Import the Integration Provisioning Files
4. Enter the Reference Key
5. Activate the Integration
6. Enter a User Account for the Partner
7. Run Scheduled Processes

Configure the Integration

The Administrator configures the integration in a testing environment.

1. In the Setup and Maintenance work area, go to:

   • Offering: Recruiting and Candidate Experience

   • Functional Area: Recruiting and Candidate Experience Management

   • Task: Recruiting Category Provisioning and Configuration

2. On the Category Provisioning and Configuration page, locate the integration partner and click the Edit icon.

3. Complete the fields. For details, see Fields to Complete for Partner Integration Configuration.

4. Click Save.

Provide User Account Credentials

The Administrator provides the user account credentials to the partner for data synchronization. The partner uses this user account for authentication with HCM when updating the data.

This is done in a testing environment. A separate account is required for the testing environment and the production environment.

These are the privileges required to provide user account credentials to a partner.

Service	Privilege
Assessment	Use REST Service - Candidate Assessments (ORA_IRC_REST_SERVICE_ACCESS_CANDIDATE_ASSESSMENTS)
Background Check	Use REST Service - Candidate Background Checks (ORA_IRC_REST_SERVICE_ACCESS_CANDIDATE_BACKGROUND_CHECKS) Choose Application Reference Territory Data (PER_CHOOSE_APPLICATION_REFERENCE_TERRITORY_DATA)
Job Distribution	Post Job Requisition to Job Distributor's Portal (IRC_POST_JOB_REQUISITION_TO_JOB_DISTRIBUTORS_PORTAL)

Export and Import the Integration Provisioning Files

When the Administrator has tested the integration on a testing environment, a user with the Application Implementation Administrator role (ORA_ASM_APPLICATION_IMPLEMENTATION_ADMIN_ABSTRACT) and Recruiting Administrator role (ORA_PER_RECRUITING_ADMINISTRATOR_JOB) performs the following steps.

Note: The enablement file must be previously loaded if it's not a refresh of the configuration. You do this using the partner's .zip file as explained above or it can be exported from a test environment using the task Recruiting Category Enablement instead of the task Recruiting Category Provisioning and Configuration.

To export the file, you first create an implementation project:

1. In the Setup and Maintenance work area, click the Tasks icon then click Manage Implementation Projects.

2. In the Implementation Projects page, click the Plus icon to create an implementation project.

3. On the Create Implementation Project page, provide the following information:

   • Name: Enter a unique name.

   • Code: Enter a unique code.

   • Description: Provide a brief description, if desired.

   • Assigned To: Assign the project to a user, if desired.

   • Start Date: Enter the date when the project will start.

   • Finish Date: Enter the date when the project will finish.

4. Click Save and Open Project.

5. On the newly created implementation project page, click the Plus icon.

6. On the Task Lists and Tasks page, search for the task Recruiting Category Provisioning and Configuration.

7. Select the Recruiting Category Provisioning and Configuration task, click Apply, then click Done.

8. Exit the Implementation Projects page.

You then create a configuration package:

1. On the Manage Configuration Packages page, click the Plus icon to create a configuration package.

2. On the Create Configuration Package page, provide the following information:

   • Name: Select the implementation project you just created.

   • Export: Select the option Setup task list and setup data.

   Note: Fields in the Configuration Package Details section are automatically populated with data from the implementation project, except for the Client ID and Client Secret.

3. Click Next.

4. On the Create Configuration Package: Select Objects to Export page, keep the Export option selected for the Partner Service Provisioning.

5. In the Partner Service Provisioning: Scope section, click the Plus icon.

6. On the Partner Integration Provisioning page, select the partner service you want to add, click Apply, then click Save and Close.

7. On the Create Configuration Package: Select Objects to Export page, click Submit.

8. When the warning message appears, click Yes. The export process starts. Once the export is done, the status changes to Completed successfully.

   Note: Click the Refresh icon to update the status.

9. Once the export is successfully completed, click the Download icon and select Download Configuration Package. An implementation project .zip file is created.

To import the file:

1. In the Setup and Maintenance work area, click the Tasks icon then click the Manage Configuration Packages task.

2. On the Manage Configuration Packages page, in the Search Results section, click Upload.

3. Choose the implementation project .zip file.

4. Click Get Details to verify that the selected file is correct. If needed, click Update to select a different file.

5. Click Submit.

6. When the warning message appears, click Yes. The upload process starts. Once the upload is done, the status changes to Completed successfully.

   Note: Click the Refresh icon to update the status.

Enter the Reference Key

The Administrator enters the reference key in the provisioning screen in the production environment. The key is provided by the partner.

Here's the list of supported characters for the reference key:

• ~
• !
• *
• (
• )
• -
• _
• .

Note: There must be no space and no & character in the reference key.

Activate the Integration

The Administrator activates the integration in the production environment.

1. In the Setup and Maintenance work area, go to:

   • Offering: Recruiting and Candidate Experience

   • Functional Area: Recruiting and Candidate Experience Management

   • Task: Recruiting Category Provisioning and Configuration

2. On the Category Provisioning and Configuration page, locate the partner and click the Edit icon.

3. Click Activate.

Once the integration is active, the status changes from Provisioned to Active.

Enter a User Account for the Partner

The Administrator enters user accounts to be used by recruiting users for the partner on the production environment. Those accounts must exist already on the partner side.

1. In the Setup and Maintenance work area, go to the following:

   • Offering: Recruiting and Candidate Experience

   • Functional Area: Recruiting and Candidate Experience Management

   • Task: Recruiting Category Provisioning and Configuration

2. On the Category Provisioning and Configuration page, click the Edit icon for a partner.

3. Click Assign User Account.

4. Enter a user name and description. The description is useful, for example, for recruiters posting a job requisition to partners or selecting a package for background check.

5. Click OK.

Packages associated with the user account are retrieved upon user account activation.

• For background checks, the administrator can also edit and save the account. This will refresh the list of associated packages.
• For assessments and tax credit screenings, deactivating and reactivating the account will refresh the list of packages associated with such account.
• Note that refreshing packages can also be done at any point of time by the partner using the account packages update service.

Run Scheduled Processes

You need to run theses scheduled processes:

• Perform Recruiting Candidate Selection Process Actions
• Send Candidate Screening Requests to Partners

For details, see Scheduled Processes in Oracle Recruiting Cloud.

Note: You can use location-based access (LBAC) to control user access to tasks and data based on their roles and computer IP addresses. If you activated LBAC, it might prevent access from external locations (IP). As a result, you're responsible to provide a Public custom role for the partner user calling the REST services. If the role isn't public, the REST services can't be called from outside the firewall. For details, see Overview of Location-Based Access