Salesforce integration 6.17.4: during search indexation, it is now possible to use a protocol to access Candidate CV/resume files stored outside of Salesforce. To be clear, creation of CV/resumes outside of Salesforce would be supported by the ATS and not the Textkernel integration. Please refer to the documentation: https://developer.textkernel.com/Salesforce/master/admin-guide/configure-textkernel-search-match/#optional-index-cvresumes-stored-outside-salesforce

Enhanced

Salesforce integration 6.17.4: to help customers reduce the Platform Event volume in their org, the integration no longer publishes platform events when a recruiter clicks workflow actions to OpenRecordDetailPage or import a record from Jobs Data. Previously these actions published Platform Events, but actually they are internal actions handled by the integration where the Platform Events are unnecessary

Enhanced

Salesforce Integration 6.17.4: improved error logging for issue when a field is missing/deleted from an org but it is mentioned in the indexation/parsing mapping configuration file being uploaded.

Enhanced

Salesforce Integration 6.17.4: (beta) for search indexation, added support to map 5 additional multi-select picklist fields for the base candidate and vacancy records. To use this feature, in the custom settings "Textkernel Indexing Service Settings", set "Use TMF Version 2" checkbox to "True", and change "Custom Indexation User Name" from the default value "import" to be "importv2".

Enhanced

Salesforce Integration 6.17.4: (beta) for search indexation, added several new fields to the candidate data mapping: Current/Last job title, Current/Last employer, Current/Last employment start date, Years of experience, Highest education level. Please review data mapping documentation: https://developer.textkernel.com/Salesforce/master/data-mapping/processing-edu-work-exp-items

Enhanced

Salesforce Integration 6.17.4: (beta) for search indexation, added 5 additional Custom Objects for Candidate and Vacancy data mapping. To use this feature, in the custom settings "Textkernel Indexing Service Settings", set "Use TMF Version 2" checkbox to "True", and change "Custom Indexation User Name" from the default value "import" to be "importv2".

Enhanced

Salesforce Integration 6.17.4: (beta) for search indexation, changed the merge logic for Education and Work Experience items. Please refer to: https://developer.textkernel.com/Salesforce/master/data-mapping/processing-edu-work-exp-items

Deprecated

Salesforce Integration 6.14.6: updated public documentation on TK Portal configuration because of change in Salesforce cookie setting in Winter Release ‘25. Please see: https://developer.textkernel.com/Salesforce/master/admin-guide/basic-textkernel-connector-setup/#saleforce-cookie-policy

Enhanced

Salesforce Integration 6.14.6: fixed bug related to permission set for recruiter user to add a missing permission

Enhanced

Salesforce Integration 6.14.4: candidate engagement Smart Inbox feature uses the updated TextKernel Portal Component. New component requires additional configuration, please check the updated documentation.

Enhanced

Salesforce Integration 6.14.4: added the possibility to disable Platform Event logging if you don't want to use the monitoring panel.

Enhanced

Salesforce Integration 6.14.4: updated the branding from Jobfeed to Jobs Data

Enhanced

Salesforce Integration 6.14.4: removed the custom code switch to enable Orgid_ prefix from Platform Events

Enhanced

Salesforce Integration 6.14.4: fixed redirections to List Views inside the package to make it compatible with SF changes in Summer Release '24

Enhanced

Salesforce Integration 6.12.3: updated public documentation on TK Portal configuration because of new Content Security Policy introduced by Salesforce in Summer Release ‘24

Enhanced

Salesforce Integration 6.12.3: a bug was fixed in parsing setup for candidate data-mapping, where the custom formula field was sometimes not visible on the mapping target.

Enhanced

Salesforce Integration 6.12.3: a button - reindex chunk has been provided to enable SF admin to reindex a chunk of 10,000 TIS records. The full procedure is covered in the public documentation.

Enhanced

Salesforce Integration 6.11.7: the GPA field on the Textkernel Imported Education has been updated to allow a wider range of values during recruiter CV parsing. Previously the field supported 2 digits before the decimal and 2 digits after, but now the field supports up to 4 digits before the decimal and 4 digits after.

Enhanced

Salesforce Integration 6.11.7: an issue was fixed where the Textkernel Platform Events monitoring panel did not work properly if there were more than 50k logged platform events

Fixed

Salesforce Integration 6.11.7: a bug was fixed in the button to cancel search indexation where it was incorrectly blocked by failed BatchProcessingIndexingStatuses Apex Jobs.

Fixed

Salesforce Integration 6.11.7: during pull indexation, similar to the change in push indexation, now only full updates are used instead of partial updates.

Fixed

Salesforce Integration 6.11.7: the best-matching UI widgets have been fixed so that the "search-from" context is correctly passed to TK Portal when the "View all in Textkernel" button is used. This means the proper match context can be passed through to the Platform Event when workflow action buttons are triggered.

Fixed

Salesforce Integration 6.11.7: in the indexation candidate data mapping, if the Comment concept was mapped/used without including the "Note" field, then the data was not sent for indexation. This has been fixed now.

Fixed

Salesforce Integration 6.11.7: The partial updates feature in push indexation is being disabled, so that now all push indexing operations will always be full updates. This is being done because there were some scenarios when a partial update was being done when a full update operation was needed. After upgrading to this version, full updates will repair candidate profiles in the search index whenever there is a new change on a candidate record. The impacted scenarios were: 1) customers using the legacy Attachment instead of the modern ContentVersion to represent CV/Resume files, and 2) customers using custom APEX Triggers for CV/Resume file changes, instead of the standard Trigger inside the managed package. Impacted customers may also want to reindex older candidate records. (The reindexation procedure is documented in the operational guide).

Removed