Once the HiBob (Bob) integration for Forecast is connected, you can import users, link existing user profiles, create departments and sync time-off from Bob into Forecast.
This article covers:
Importing Users from HiBob
Forecast Admins can import users from Bob to create new Forecast user profiles. Importing from Bob provides comprehensive list of all Bob employees to select from. Seat type and user permissions are defined when importing employees from Bob. Additionally, Admins can sync existing Forecast users with Bob employees who share the same email addresses.
Field mapping for Users
HiBob | Forecast |
---|---|
firstName | first_name |
surname | last_name |
title | job_title |
department | departments/name |
startDate | start_date |
To import employees from HiBob
- Click Admin in the navigation bar.
- Select Resources from the dropdown.
- Click Import Team Members from HiBob.
- Select the seat type to assign to the users and click Next.
- Select the Permissions for the users.
- Select the Team Members to import.
- Click Import Selected Team Members.
- Successfully linked users display the integration logo on the Resources > People page.
Linking Existing Users to HiBob
While importing team members from Bob creates new Forecast user profiles, it is also possible to link existing Forecast user profiles to Bob.
To link existing users to HiBob
- Click Admin in the navigation bar.
- Select Resources from the dropdown.
- Identify the user to link with Bob.
- Click the user name to open the profile.
- Scroll down to HiBob.
- Select the user from the dropdown.
- Once linked, the integration logo will display on the user record in Resources > People.
Syncing Non-Project Time
When the integration is connected, all time-off is created and managed in Bob; It is not possible to create or edit time-off directly in Forecast. Importing new users from Bob imports all future time-off booked for the user in Bob. Future time-off is any time-off booked in Bob after the date the integration is connected.
Field mapping for Policies
The integration uses the Bob Policy Non-project Time, where is_internal_time is set to FALSE. When the integration is active, all non-project time categories from Bob are imported using Bob's Get All Policy Types and posted to Non-Project Time in Forecast.
HiBob | Forecast | Details |
---|---|---|
name | name | |
N/A | is_internal_time | default to FALSE |
Field mapping for Non-Project Time
New time-off bookings are imported into Forecast through the daily sync process and appear as time-off allocations. Any changes to existing time-off must be made in Bob and will sync to Forecast.
HiBob | Forecast | Details |
---|---|---|
employeeID | person | |
policyTypeDisplayName | non_project_time | Forecast matches name with policy ID. |
startDate | start_date | |
endDate | end_date | |
approved | N/A | Time-off is imported only if approved = TRUE in Bob. |
dayPortion | monday | If morning or afternoon == 4, else 8 |
dayPortion | tuesday | If morning or afternoon == 4, else 8 |
dayPortion | wednesday | If morning or afternoon == 4, else 8 |
dayPortion | thursday | If morning or afternoon == 4, else 8 |
dayPortion | friday | If morning or afternoon == 4, else 8 |
dayPortion | saturday | If morning or afternoon == 4, else 8 |
dayPortion | sunday | If morning or afternoon == 4, else 8 |
N/A | is_soft | FALSE |
endDatePortion | N/A | If endDatePortion differs from dayPortion, and the booking length exceeds seven days, the system must create a new allocation with the same details for the last day and remove the last day from the initial booking. |
durationUnit | N/A | HOURS |
Comments
0 comments
Article is closed for comments.