On the PDF Preview page, documents will now render directly within Onboarding365 when viewed
on a mobile device. Onboarders will no longer need to open a PDF document in another browser tab
in order to complete the document.

The Direct Deposit and Canadian Direct Deposit documents can now customize the pay option titles
for “Direct Deposit,” “Pay Card,” and or “Payroll Check.” These changes can be made from the “Advanced” tab of these documents in Document Management.

The Resume Parsing tool has been enhanced to set the CityID for the Onboarder who’s resume is
being parsed when an exact match is found against the City in the parsed resume.

The ‘Lived In City’ document rule is now available in the ‘All Document Rules’ Data View report. The data view can be filtered by ‘Lived In City’.

The ‘Lived In City’ rule is also now available in the ‘Document Rules History’ Data View report.

We now support assigning Document Rules for the ‘Lived in City’ field.

Note: This new feature requires the ‘City Validation’ feature to be enabled. Any onboarding
candidate profiles completed prior to this rule being turned on will be forced to select a validated city
the next time the profile is completed.

A new Agency Setting, ‘City Validation’, has been introduced. When enabled, the City field in the
Profile will only be editable for an Onboarder after they have selected a state. The field will no
longer accept any string but will instead show the user a potential City associated with the selected
State as they are typing in the City Field.

Note: Enabling this setting will change our SOAP validation – when initiating an Onboarding the
CountryID field will now be required.

Please be aware of any existing SOAP integrations before enabling this setting.

Resolved an issue where auto-created Client and Client Offices in Onboarding365 were successfully
created but set to ‘Inactive’.

Also resolved an issue where the assigned business key format for auto-created Client and Client
Offices was not supported by Mapped Entities in Bullhorn.

Profile Extension values captured in an onboarding profile can now be successfully flowed back to
Bullhorn ATS.

A new System Setting, “o365DirectDepositFlowback” has been introduced.

When this setting is set to ‘TRUE’, then Onboarding365 Direct Deposit Data will automatically
flowback to the DirectDepositAccount entity in Bullhorn when an onboarding moves to a ‘Complete’
status.

We resolved an issue where Onboarders were not being removed from the I-9 Warnings tab of
the I-9 Dashboard after documents that had expired or were going to expire were resolved
with a Form I-9 Section 3.

We also resolved an issue where the Signature.Employee and Signature.HR fields displayed while
previewing a document in Document Management were incorrectly being displayed.

The UI for the Onboarding Document List page on mobile devices has been updated. The document
statuses are no longer presented as clickable buttons but instead displayed as plain text.

The following frontend field validations have been added throughout the Onboarding365 in order to
better align with existing database-level field limits:

● Notification Email Addresses
● Vendor Postal Code
● Field Rep Email Address
● Agency Name
● Receipt Number (SSN)
● Onboarder URL
● Vendor URL
● Business Key (Payroll Data tile)

Custom Attributes have been enhanced to now include two different Custom Attribute Types — Free
Options Entry’ and ‘DropDown Options List. The new ‘Free Options Entry’ Custom Attribute Type
will allow you to send any value through for a particular Custom Attribute when utilizing the
Onboarding365 REST API V2.

‘Free Options Entry’ Custom Attributes are not supported by Document Rules nor can they be
modified by editing an Onboarding. This new function is designed to be used through a REST
integration.

The ‘DropDown Options List’ Custom Attribute Type remains consistent with previous Custom
Attribute functionality, where only pre-configured values are considered valid.

Any custom web form field data that is captured during an onboarding in Onboarding365 can now
be flowed back to Bullhorn.

A new System Setting, “Auto-Create O365 Clients and Offices” has been introduced.

When set to ‘TRUE’, any Company record that is created or updated in Bullhorn automatically
creates or updates a corresponding Client record in Onboarding365. The data that syncs from the
Bullhorn Company record to the Onboarding365 Client record is the ‘Name’ field.

Additionally, any Location record that is created or updated in Bullhorn automatically creates or
updates a corresponding Client Office record in Onboarding365. The data that syncs from the
Bullhorn Location record to the Onboarding365 Client Office record is the ‘Title’, ‘Address’, ‘City’,
‘State’, ‘Zip’, and ‘Country’ fields.

Two new System Settings have been introduced — ‘O365EducationHistoryFlowBack’ and
‘O365WorkHistoryFlowback.’

When set to ‘TRUE’, any candidate Education History and/or Employment History data captured
during profile completion in Onboarding365 will automatically flowback to the ‘CandidateEducation’
and ‘CandidateWorkHistory’ entities in Bullhorn once a candidate’s onboarding reaches a “Complete”
status.

A new System Setting, “Onboarding365ReasonforCancelling” has been introduced.
Any values set in this new system setting will be displayed as picker options in the “Reason for
Cancelling” field when a user attempts to cancel an onboarding. If no values are set in the
“Onboarding365ReasonforCancelling” setting, then a free-form field will be displayed in place of the picker.

Once an onboarding is cancelled, a note will be created using the selected value as the body of the
note. If the onboarding is cancelled from the Candidate record a note will only be captured on the
Candidate record. If the onboarding is cancelled from the Placement record the note will be
captured on both the Candidate and Placement records.

We resolved an issue where HR Session fields (Session.FullName, Session.JobTitle,
Session.HRCurrentDate) were not pulling over to PDF documents as expected.

Candidates will no longer be required to enter their password when completing the Electronic
Signature Acknowledgement page.

A new ‘Form I-9 Section 1 Review’ workflow has been introduced for the Form I-9 document that
when enabled, requires a Form I-9 certifier to first confirm or reject Form I-9 Section 1 prior to
completing Section 2.

If a Form I-9 Section 1 is rejected, a new Form I-9 will automatically be assigned to the onboarding
and the rejected Form I-9 Section 1 will be removed from the onboarding (but still accessible via the
View Deleted option in the Options menu).

The ‘Form I-9 Section 1 Review’ setting can be enabled by navigating to the “Advanced” tab of the
Form I-9 document in Document Management, and selecting this option.

Note: If your agency currently has the ‘Automated I-9’ setting set to ‘ON’, it is recommended that this
feature not be turned on at this time.

The following REST API endpoints have been introduced and can used to create or update Clients or
Client Offices:

● POST/Agency/client
● PUT/Agency/client
● POST/Agency/clientoffice
● PUT/Agency/clientOffice

The REST GET Onboarding/onboardingdocument and Onboarding/onboardingdocuments will now return
custom web form data in the form of a key value pair array as JSON in the ‘additionalInfo’ field.

Document Score (‘score’) is also now included in the response.

A new document expiration type called ‘Days Since Termination’ has been introduced which can be
used to set a document’s expiration based on the number of days since an employee was terminated.

● Updated the Onboarding Menu icon in Bullhorn to the new Onboarding365 logo.
● Updated the header of the Onboarding page to read ‘Onboarding’.
● Updated the Candidate and Placement Onboarding tab to read Onboarding365.
● Updated the Onboarding Setup menu item to read ‘Onboarding365 Setup’.
● Updated our issues log so that Onboarding365 issues will now appear as ‘Onboarding 365
Flowback’ or ‘Onboarding365ServiceError’.

When cancelling an onboarding from Bullhorn ATS, users will now be able to capture a note at the time of cancelling. When the Cancel action is taken from the Candidate record the note will reference the Candidate, when the Cancel action is taken from the Placement record the note will reference the Candidate and Placement. The Note action will default to ‘Onboarding Cancelled’ but can be customized by Bullhorn Support.

Introduced a REST /Onboarding/employee/terminate and /Onboarding/employee/unterminate end
points that can be used to terminate or un-terminate an employee.

We have a bug fix for the Password Reset function where some users were receiving an error message upon attempting to reset their password.

For the Direct Deposit and Canadian Direct Deposit documents, we’ve implemented the following UI
enhancements to the Document Settings page:

● Renamed the “Additional” tab to now read “Advanced”
● Renamed the ‘Custom Pay Method Jurat Statement’ option to ‘Custom Pay Method
Acknowledgment Statement’,
○ Note: This is the checkbox label that is presented to the onboarder in the web form
● Added the ability to customize the Jurat Statement for all payment types.
● Removed the ‘description’ from the following fields on the Advanced tab on the Document
Management tool as the fields are self-explanatory:
○ Custom Pay Method Title
○ Custom Pay Method Description
○ Custom Pay Method Jurat Statement
○ Custom pay method Logo URL

Mapped Entities now supports the ability to send data from a Candidate or Placement custom object to Onboarding365.

This endpoint is used to update the ‘Placement Start Date,’ ‘Placement End Date,’ and or ‘Placement
Actual End Date’ values on an Onboarding.

We have updated the California withholding tax document from the 2020 version to the 2021 version.

We have added an ‘Additional’ tab to the document management tool for both Direct Deposit and Canadian
Direct Deposit. This new tab allows an Onboarding user to setup Custom Pay Methods, including
tools to configuring ‘Custom Pay Method Title,’ Custom Pay Method Logo URL,” Custom Pay Description,’ and ‘Custom Pay Method Jurat Statement’ on both the Direct Deposit and Canadian Direct Deposit document.