Salesforce Integration 5.3.23: the Automatic Match UI widgets now present data using the Salesforce user's preferred locale settings for: date, date-time, and currency fields.

Enhanced

Salesforce Integration 5.3.23: recruiters can now import a record from Jobfeed search results in the Jobfeed portal search UI inside Textkernel Portal.

Enhanced

Salesforce Integration 5.3.23: Jobfeed Switzerland is now supported for all Jobfeed workflows.

Enhanced

Salesforce Integration 5.3.23: This is a breaking change for the external candidate import feature currently in beta: 1 The name of the automation APEX class used by the webhook's integration user has changed to “AutomationApiRestService”, and the automation API webhook naming convention is now: https://*ORG_DOMAIN*.my.salesforce.com/services/apexrest/Textkernel1/AUTOMATION_API_WEBHOOK

Enhanced

Salesforce Integration 5.3.23: an issue was fixed where recruiters saw an "Unknown Error" message when importing Jobfeed Jobs into Salesforce. The import still worked in spite of the error message.

Fixed

Salesforce Integration 5.3.23: Fixed spelling mistakes on 2 fields in the search candidate mapping page in the Textkernel configuration app

Fixed

Salesforce Integration 5.3.23: Jobfeed import widget has been fixed so that account names containing '&' symbol can be imported.

Fixed

Salesforce Integration 5.0.10: beta release of a new feature allowing recruiters to manually import external candidate profiles into Salesforce from the Textkernel external candidate search results. After finding candidates in external candidate databases, recruiters can click a button to import the profile information into their Salesforce ATS, keeping their Candidate database up to date with the latest and best Candidates.

Added

PersonCustomObjectInstance events are now supported in the Bullhorn Connector.

Enhanced

Salesforce Integration 4.10.10: an issue was fixed where the Textkernel App threw a Javascript / Aura Component Error: “Failed to initialize a component [Cannot access 'r' before initialization]”. The issue was triggered by a change in Salesforce platform behaviour relating to its Lightning Web Security component.

Fixed

An issue is fixed in the Bullhorn native integration, for customers using the legacy external searcher flow to import external candidates into Bullhorn. The owner is now being set properly again after this update.

Fixed