(AI KB) PCS 2.5 – Bullhorn API Setup and Requirements

 

Purpose: This guide is to outline the steps and requirements to set up Bullhorn Integration for PCS 2.5.

 

For Release Information and Full Fledge Installation Material, Please Reference: (AI KB) PCS 2.5 Release Information & Installation Link – American Innovations Support Center

 

Function and Limitations:

This feature allows all Bullhorn RMU readings across multiple Bullhorn Web accounts to be on a single import and schedule. The mapping of each facility and the readings associated with PCS fields is intuitive and user-friendly, and the mapping will leverage your existing Bullhorn Bridges to create the initial mapping on the tool, so there is limited setup needed. 

 

This does place a limitation on the feature: There is only one schedule that can be applied to this import. Once all the accounts from Bullhorn Web are integrated, there will be an option to set the schedule of the import. This import will leverage the same schedule for all units on all accounts linked. For customers that need different reporting schedules across groups in a specific account or across different Bullhorn Web accounts, the current Bullhorn Bridge setup via the Extract token will need to be used. 

 

 

To begin, the user that is setting up Bullhorn Integration will require the “Client Admin” Permission on ALL accounts to be linked. In Addition, this will need to be a PCS Admin as well.

 

Please see the guide below on how to determine if you have "Client Admin" access on Bullhorn Web and how to obtain it if not:

 

(AI KB) How to tell if you are a Client Admin and how to add a Client Admin in Bullhorn Web

 

(Critical) Please Note:

The integration function can only be run once. If you want to test it further, a restoration of the database will be required at that time.  This feature will allow an admin to link all of the Bullhorn Web accounts to the integration dashboard once ready. Please see the link below for the configuration and requirements for this one-time setup.

 

Additional Information: You will need to be logged into both PCS as the Admin as well as Bullhorn Web with the Client Admin role to proceed.

 

1. To begin, the PCS Admin will go to Tools > Bullhorn Integration in PCS.

 

 

2. In Bullhorn Web, the Client Admin will have the “Bullhorn API” option available to them.

 

 

Choosing the Bullhorn API Option will bring up the menu to create one. Please be aware, there is only one API needed per Bullhorn Web account!

 

 

 

3. Click the “Add New Credential” option next and this will prompt you for a name. We suggest that you name this as the same account ID as the import for easy reference.

 

4. Hit “Save” and this will create a new credential:

 

 

 

5. Click on the magnifying glass icon next to the created date to obtain the relevant info to link in PCS:

 

 

The API Client ID and API Client Secret will both be automatically generated with a copy function next to each. These are the items you will need to add this account to PCS 2.5’s Bullhorn Integration. Below is the integration  configuration where you will input the API Client ID and API Client Secret to link an account:

 

 

 

 

 

Once the API Client ID and API Client Secret are in PCS, click Save in the top right hand corner

 

 

 

You can then proceed to link any other Bullhorn Accounts needed in the same way AFTER clearing the API Client ID and API Client Secret via the "Clear" button

 

 

 

Example of more than one account:

 

 

 

 

 

 

 

**This can be done for as many accounts as needed. Please ensure ALL accounts are linked to PCS before you run the Bullhorn Mapping!**

The final step before you run the Mapping is to set the schedule for import at the bottom.  This will be the import cadence for ALL Bullhorn RMUs on all linked accounts.

 

 

The Bullhorn Integration will use all of your current Bullhorn Bridges for the initial mapping. We suggest that you keep these bridge definitions during the transition to Bullhorn Integration while disabling their schedule and removing access from PCS Users who should not be running their own imports. This can be done via a custom Security Role in PCS.

 

Please contact Support if you need assistance in customizing the security role.  

 

For Further Assistance Please Submit a Technical Support Ticket