Bullhorn Features

Tracks

Some Bullhorn systems have a number of Placement and Job Tracks. For more information on how these work contact Bullhorn support. RSM InTime is not aware of the different tracks during import so you need to ensure that any fields that are mapped to RSM InTime contain the same data and format for all tracks.

Cloning

Some Bullhorn systems offer the ability to clone placements. This creates a copy of an existing placement which is given a new unique ID so from RSM InTime’s perspective it is simply treated as a new separate placement.

Change requests

The only point a Bullhorn change request has any impact on RSM InTime is when it is finally approved as this is when it commits the changes to the placement. It will then generate an update event and RSM InTime will then import the updated details.

Display List and Value list

In the Field mappings section of Bullhorn each field has a Display List and Value list. The Display list is what Bullhorn users see on screen when viewing the placement, candidate etc. The Value list is what is actually stored in the database and is what RSM InTime will receive when reading that field. Therefore it is important that the Value list contains the data you expect to appear in RSM InTime.

FAQ

Q. Will RSM InTime update placements that are not longer in the import status e.g. ’Approved’?

A. RSM InTime will only create placements in the configured status but once the placement or participants exist in RSM InTime it will continue to process updates for these regardless of the status in Bullhorn.

Q. If i manually update a field in RSM InTime will it be overwritten by the next Bullhorn update?

A. Yes, if it is a field that is mapped by default or by a customisation, otherwise no.

Q. Can documents or files be synchronised to RSM InTime?

A. Not currently.

Q. Can Bullhorn encrypted fields be mapped to RSM InTime?

A. Encrypted fields can be mapped to RSM InTime through the REST API but not SOAP.

Q. Can Confidential fields be mapped to RSM InTime?

A. Yes confidential fields can be mapped to RSM InTime as long as the RSM API user has the appropriate access rights. Please be aware that once in RSM InTime the field will have no specific access control as it would in Bullhorn. Any users who can normally see that field will be able to see its value.  

Q. How can I get the Consultant IDs for reference migration? They are not in the User Interface.

A. You can see this is the Bullhorn User List Report. To generate a user list from bullhorn you must have admin access.

Navigate to:

Menu > Admin > Users > Select an Action > Generate Userlist > Enabled: “All” > Format : “Excel 2000” > Generate Report

Screenshots below…

1.

2.

3.