Release 2022.12.0 on Saturday, November 5, 2022 contains user experience improvements, security & audit improvements, and improvements related to the BrightMove integration framework based on webhooks. There are also several major behind-the-scenes changes that are being deployed with appropriate feature switches in place (to disable the new capabilities). These behind-the-scenes changes are needed for future releases over the coming months.

In this release, we made user experience improvements related to the candidate source attribute when searching for candidates within Power Search. Some users that have large numbers of candidate sources were unable to view the source list easily. This release includes logic & performance improvements to the source lookup, that allows for a candidate source list result set in excess of 50 sources.

In this release, we improved the logic in the candidate dashboard pane to no longer include the counts of jobs related to deleted client records.

When using the dark mode theme, we found certain fields to not be visible. Changes in this release allows for users who have selected the dark mode theme to be able to view all of the fields with contrast.

In this release, we fixed a logic error in one of the activity data services that has affected RPO customers. The change that is being introduced in this release fixes a logic error by including both the RPO parent and RPO child account activity IDs as part of the data service execution. This is to reduce duplicate records which are returned in some scenarios.

In this release, we made it possible for users with the Administrator role to see the last login date for accounts within their instance. By going to the Employee Profile > Audit tab, administrators can now see the last login date of the user.

Webhooks are used to integrated with 3rd party services via web services. In this deployment, we added support to handle the merge of applicants and client contacts to downstream services. Webhooks are invoked or fired when events occur.

When two applicants are merged within ATS, the primary applicant is considered the surviving record and the non-primary applicant does not have survivorship. Upon merge, the UPDATE webhook is fired on the primary applicant and the DELETE webhook is fired on the secondary applicant.

When two client contacts are merged within ATS, the primary client contact is considered the surviving record and the non-primary applicant does not have survivorship. Upon merge, the UPDATE webhook is fired on the primary client contact and the DELETE webhook is fired on the secondary client contact.

Note: The client contact webhook events were created in this release. Prior to 2022.12.0 they didn't exist.