Bullhorn Features

Tracks

Some Bullhorn systems have a number of Placement and Job Tracks. For more information on how these work contact Bullhorn support. InTime is not aware of the different tracks during import so you need to ensure that any fields that are mapped to 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 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 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 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 InTime will receive when reading that field. Therefore it is important that the Value list contains the data you expect to appear in InTime.

FAQ

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

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

Q. If i manually update a field in 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 InTime?

A. Unfortunately not, this is due to a limitation of the Web Services Interface.