Bob HR to JSM Assets

Please review instructions here to get started with setting up an Assets import configuration. You can then access OnLink app from the “Manage your apps” menu to further configure and set the field level mapping. Here’s an example configuration:

Set a descriptive name for this map
Set source system to Bob HR
Asset Schema is pre-filled. This is the schema in JSM Assets on which you started the configuration.
Select the Object Type within your schema.
Optionally, enable scheduling
Attribute mapping - see below for more details.

Sample User Object Schema

Here’s a sample mapping config:

key:root.id=WorkerID
map:root.displayName=Name
map:root.email=JiraUser
map:work.title=Title
map:work.reportsTo=Manager
map:work.startDate=HireDate
map:work.department=DepartmentName|Name=${work.department}
map:work.reportsTo.email=ManagerUser

To get the full list of fields and the format to be used (e.g. root.firstName vs work.startDate), use a tool like Postman to call this “GET” API https://api.sandbox.hibob.com/v1/people/. Only fields that do not have a “parent” should use the root suffix. Examples are displayName, companyId, firstName, etc. For all other fields, use the appropriate parent e.g. work.startDate, address.city, home.mobileNumber, etc.

Here’s a breakdown of some of the mapping configuration items:

Key or Map	Description

Key or Map	Description
`key:root.id=WorkerID`	The keyword “key” refers to using Worker_ID (from Bob report) as a unique identifier. This allows OnLink to update the record. WorkerID is a text attribute.
`map:root.displayName=Name`	Maps Display Name from Bob custom report to Name text attribute. Additional Bob fields can be found in this API ref.
`map:root.email=JiraUser`	The emailAddress field containing email address of worker is mapped to JiraUser, which is an attribute of type “User”. Here OnLink looks-up the Atlassian User object based on the email address.
`config:data_limit=100`	Optional. Set parameter to limit the number of users to pull from Bob. This can be used for initial testing.
`filter:field_path=filter_value`	Optional. You can set filters where field_path is a valid Bob API field path (e.g. work.department), and filter_value is a static value. You can add multiple filter lines and also set multiple filter values using a pipe (“\|”) symbol. For e.g. `filter:field_path=filter_value1\|filter_value2\|filter_value3`
`config:humanReadable=APPEND`	Optional. If not set, the Bob API returns machine-readable values only. Possible values: APPEND or REPLACE
`config:inactive=true`	Optional. Add this line to include inactive workers

OnLink processes data in two steps - Get Data and Import Data. To manually test, you can click on Get Data first and then wait until you see “No more pending records. Data will be imported on next Import run.” message in Job Logs. Then, click on Import. Production runs are fully automated based on the schedule you choose.