Skip to content
Textkernel Release Notes
Integrations
latest

Textkernel Integrations - Release Notes Archive

Looking for current release notes?

View current release notes on the Bullhorn Hub

November 24, 2025

Fixed

  • A bug has been fixed in the Sourcebox user interface, where using the Export button triggers a "Not Available" message.

November 5, 2025

Enhanced

  • The Textkernel Search & Match integration with Bullhorn Platform ATS has been enhanced to improve its throughput by introducing additional concurrency.

June 30, 2025

Enhanced

  • Salesforce Integration 6.33.0: Labels were renamed from Jobs Data to Market IQ to reflect the new name of the product.

Fixed

  • Salesforce Integration 6.33.0: Corrected a bug causing infrequent flow failures during Textkernel Log records creation.
  • Salesforce Integration 6.33.0: A bug has been resolved where embedding the TKPortal UI in Contact/Job records would trigger multiple platform events.

May 2, 2025

Fixed

  • Salesforce Integration 6.30.0: An issue occurred when installing the package in an org where the object Individual was disabled. This has now been resolved.
  • Salesforce Integration 6.30.0: A bug in the Best Matching widgets, which caused unnecessary indexing of a record, has been fixed.

April 23, 2025

Enhanced

  • Textkernel Portal users can now have more than 1 single active role configured. This provides more flexibility regarding what a user sees when looking at the content loaded inside Textkernel Portal

April 16, 2025

Enhanced

  • Talentsoft Bug Fix – Vacancy Search LogicFixed an issue where removing a tag caused the search to return no results due to incorrect query structure. The vacancytitle terms were treated with AND logic instead of OR, making the query too restrictive. This has been corrected to ensure proper grouping and expected results.

April 14, 2025

Enhanced

  • Talentsoft Bug Fix – Vacancy Search LogicFixed an issue where removing a tag caused the search to return no results due to incorrect query structure. The vacancytitle terms were treated with AND logic instead of OR, making the query too restrictive. This has been corrected to ensure proper grouping and expected results.

February 28, 2025

Enhanced

  • Salesforce Integration 6.29.0: An issue occurred under certain conditions when more than 4,000 external candidates were pushed into Salesforce via the Automation API. This has now been resolved.
  • Salesforce Integration 6.29.0: Support for placements and contact lists has been added to the vacancy data mapping.

February 14, 2025

Enhanced

  • Salesforce Integration 6.27.0: There is a new TK Portal layout option to embed portal in a tab within a Candidate or Job page. This enables improved UX, for example to show matching Candidates on the same page as the Job. The configuration is in the documentation:https://developer.textkernel.com/Salesforce/master/admin-guide/workflows-embedded-tkportal/
  • Salesforce Integration 6.27.0: In the admin interface, the "UI Component Settings" configuration panel has been renamed "Match Component Settings"

December 2, 2024

Enhanced

  • Salesforce Integration 6.18.0: for search indexation, both custom settings - "Use TMF Version 2" and "Custom Indexation User Name" under "Textkernel Indexing Service Settings" from previous release have been removed. The integration now always uses TMF Version 2 and the appropriate custom indexation user name. This is not a breaking change. Please refer to:https://developer.textkernel.com/Salesforce/master/data-mapping/processing-edu-work-exp-items

October 31, 2024

Enhanced

  • 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
  • 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
  • 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.
  • 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".
  • 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
  • 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".

Deprecated

  • 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

September 10, 2024

Enhanced

  • 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
  • Salesforce Integration 6.14.6: fixed bug related to permission set for recruiter user to add a missing permission

September 3, 2024

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.
  • Salesforce Integration 6.14.4: added the possibility to disable Platform Event logging if you don't want to use the monitoring panel.
  • Salesforce Integration 6.14.4: updated the branding from Jobfeed to Jobs Data
  • Salesforce Integration 6.14.4: removed the custom code switch to enable Orgid_ prefix from Platform Events
  • Salesforce Integration 6.14.4: fixed redirections to List Views inside the package to make it compatible with SF changes in Summer Release '24

July 8, 2024

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
  • 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.
  • 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.

June 18, 2024

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.

Fixed

  • 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
  • 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.
  • 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.
  • 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.
  • 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.

Removed

  • 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).

May 1, 2024

Enhanced

  • Sourcebox user names can now include @ and . symbols. For example, this makes it easy to use an email address as the user name.

April 23, 2024

Enhanced

  • UI styling in Textkernel Portal landing pages has been updated to reflect new Textkernel branding standards.

April 22, 2024

Enhanced

  • Salesforce Integration 6.8.6: "Applicant ranking" is now supported as a Quick Action button. The Salesforce setup procedure is covered in the public documentation. However, please note that If you are upgrading your existing installation and want to add this, please contact Textkernel support so that we can make changes in our platform to activate the feature.
  • Salesforce Integration 6.8.6: the button to cancel and restart push indexation has been improved with new handler logic, and now it shows a spinner when it is busy.
  • Salesforce Integration 6.8.6: Javascript event origin checking has been relaxed to handle Textkernel SSO and non-SSO URLs. Some of the workflow actions from Textkernel Portal back to Salesforce (eg open candidate or match actions) were losing data because this check was too restrictive after SSO configuration changes relating to 3rd-party cookies.
  • Salesforce Integration 6.8.6: an issue was resolved where the Textkernel Indexing Status records did not properly get merged if the Salesforce merge feature was used to combine 2 candidates into 1 record
  • Salesforce Integration 6.8.6: a bug in indexation of Attachments (old Salesforce File object type) has been fixed, where an error was thrown about missing field Attachment.BodyLength
  • Salesforce Integration 6.8.6: the helper APEX functions that are used to handle upsert and deletion of records into the index now work properly when a guest site user license type triggers them via Flow or APEX
  • Salesforce Integration 6.8.6: in parsing candidate data mapping, when assigning mappings to formula fields we now filter to only show relevant target fields with the appropriate data type.
  • Salesforce Integration 6.8.6: in candidate indexation data mapping, we now support the Salesforce compound address field type as a mapping source for relevant fields.
  • Salesforce Integration 6.8.6: "Find similar candidates" is now supported as a Quick Action button. The Salesforce setup procedure is covered in the public documentation. However, please note that If you are upgrading your existing installation and want to add this, please contact Textkernel support so that we can make changes in our platform to activate the feature.

April 19, 2024

Enhanced

  • Sourcebox user names can now include @ and . symbols. For example, this makes it easy to use an email address as the user name.

April 16, 2024

Enhanced

  • In Textkernel's support for Bullhorn Automation Auto-match, we now optionally support a custom match query template that is different from the query template used by other match users. To be clear, this change is not related to the Textkernel Platform's Automatic Match feature.

March 19, 2024

Enhanced

  • Textkernel Portal has been updated to use Textkernel's new logo.

March 11, 2024

Enhanced

  • Salesforce Integration 6.5.0: new layout v2 is included for Textkernel Imported Candidate to use the new Skill data model
  • Salesforce Integration 6.5.0: Textkernel logos have been updated to reflect the new branding. This change affects new installations, but during package upgrades, the existing app logo is retained, in case it was customized.
  • Salesforce Integration 6.5.0: Plural labels for Imported Work Experience and Imported Education have been adjusted to drop the incorrect usage of s.
  • Salesforce Integration 6.5.0: Previously, if data segregation search policies were defined in Salesforce, they were always used by the Automatch widgets, even when data segregation was disabled. The behaviour has been fixed so that they are now only applied if/when data-segregation is enabled.
  • Salesforce Integration 6.5.0: during indexation, if a CV/resume binary is larger than 3 MB the Candidate is excluded from indexation. Files larger than this are not supported because of constraints on size of Salesforce API payloads.
  • Salesforce Integration 6.5.0: Jobfeed Japan is now supported.
  • Salesforce Integration 6.5.0: when importing Jobfeed Leads, if normalized skills are enabled, these are now extracted and made available. Please refer to the skills data model documentation for more details:https://developer.textkernel.com/Salesforce/master/admin-guide/skills-data-model/
  • Salesforce Integration 6.5.0: new Skills data model introduced during Candidate parsing. Please review new skills data model documentation for more details:https://developer.textkernel.com/Salesforce/master/admin-guide/skills-data-model/Important: if you need to continue using the old Skills data model temporarily for backwards compatibility, check the custom setting discussed in the documentation to ensure it is set properly.

February 8, 2024

Fixed

  • Recent TK Portal enhancements to support Google Chrome's new 3rd-party cookie blocking behaviour showed an extra step during SSO flows more frequently than was necessary. The screen is still needed sometimes, but it will now appear less frequently after this change.

January 24, 2024

Enhanced

  • Salesforce Integration 5.21.0: support for the Labour Market Insights product (formerly called Jobfeed), has been extended to include additional countries: Australia, Ireland, and New Zealand.
  • Salesforce Integration 5.21.0: the error logging messages have been improved to provide more details when search indexation encounters errors constructing the API callout to add, update, or remove records from the Textkernel index.
  • Salesforce Integration 5.21.0: in the "Indexation status" table under monitoring tools, the reset errors button behaviour has been enhanced, so that the button resets temporary errors in addition to permanent errors.
  • Salesforce Integration 5.21.0: in the "Indexation status" table under monitoring tools, the behaviour is improved, so that severity code 2 errors are grouped as permanent errors.
  • Salesforce Integration 5.21.0: the Textkernel Indexing Status object has a new layout version, v2, which shows additional technical fields relating the indexation. This makes debugging easier. Salesforce admins can switch to the new layout in their org, or manually merge the changes into the layout deployed in their org.

January 23, 2024

Fixed

  • Messages are now added in non-English languages in Textkernel Portal for the new SSO login flow that is sometimes needed as a result of Google Chrome's breaking change to block all cross-domain cookies. (Previously the messages in the new flow were only available in English).

January 15, 2024

Enhanced

  • It is now possible in TK Portal to hide some of the Textkernel tabs when instantiating the TK Portal iFrame inside the enclosing system. This is handled using a new URL parameter that is discussed in the documentation.

January 10, 2024

Enhanced

  • An issue was fixed where in some cases default values were not being applied in the Sourcebox configuration. This manifested itself for some customers using the split-screen to review parsed data in the "split-screen" view.

January 2, 2024

Enhanced

  • Salesforce Integration 5.19.0: enhancement for Textkernel Portal feature users.Google Chrome is rollling out a breaking change to 1% of users starting January 4, 2024: the change blocks all cross-domain cookies, including non-tracking functional cookies. This enhancement updates our integration's single-sign on protocol to be compatible with the change. Please refer to the one-time configuration instructions for a change that is needed with this package upgrade:https://docs.google.com/document/d/1KOokWns3dkO2Ngr-4G6ctah37hTNt0yX1pfeZgp7k2I.After the upgrade and configuration change, please note that users need to clear their browser cookies for the change to take effect.

December 19, 2023

Enhanced

  • Salesforce Integration 5.18.8: when displaying the Candidate Engagement SmartInbox on the candidate record, the extra tabs from other textkernel applications are now suppressed, since they are not needed in this context.
  • Salesforce Integration 5.18.8: a bug was fixed where, in some cases the scheduled ImportedCandidateParsingBatch job that picks up Textkernel Imported Candidate records was scheduling itself to run 1 day in the future instead of 1 minute in the future.
  • Salesforce Integration 5.18.8: in the monitoring panel, when resetting indexation errors with the "Reset errors" button, we now also reset severity code 2 errors in additional to severity code 3 errors.
  • Salesforce Integration 5.18.8: the Textkernel Imported Work Experience object has a new layout version, v2, which shows the professions coding information (eg ONET, ISCO). Salesforce admins can switch to the new layout in their org, or manually merge the changes into the layout deployed in their org.

Fixed

  • Salesforce Integration 5.18.8: the Candidate Engagement integration now allows repeated submission of the same candidate engagement request instead of suppressing duplicate requests in Salesforce.
  • Salesforce Integration 5.18.8: when using the feature to generate missing Textkernel Indexing Status records, the new "Is Candidate" field for pull indexation is now set properly.
  • Salesforce Integration 5.18.8: during standard push indexation, a bug has been fixed where the new fields "Index request when busy" and "Removal request when busy" were not reset after being handled.

November 27, 2023

Enhanced

  • Salesforce Integration 5.17.3: a new/updated layout v2 is added for the Textkernel Imported Work Experience object. The new layout shows the normalized profession information and labels (eg class, group, ONET, ISCO). Layout changes in SFDC managed packages cannot update existing layouts in customer orgs, so admins wishing to adopt these layout changes should manually update their layouts.
  • Salesforce Integration 5.17.3: an issue was fixed where a trigger inside a test class caused errors when the managed package was installed in a sandbox environment using a site license.
  • Salesforce Integration 5.17.3: the indexation data-mapping UI has been enhanced to make it clear that checkboxes should always be used as the control when filtering records from indexation instead of using a formula function field.
  • Salesforce Integration 5.17.3: a new panel is available in the Monitoring tab allowing the Salesforce admin to see the status of requests submitted to Textkernel Candidate Engagement.

Fixed

  • Salesforce Integration 5.17.3: in unusual cases where 50,000+ daily external candidate import events were pushed into Salesforce using the automation API, an issue blocked the events from being processed in the first attempt. This capacity issue has been addressed.
  • Salesforce Integration 5.17.3: an issue has been fixed in the parsing data mapping configuration UI where sometimes the incorrect Salesfroce Record options were shown.
  • Salesforce Integration 5.17.3: a bug was fixed in the push indexation process. In rare cases, when all elements of a mapped item group (for example contact_lists) were removed from a candidate, the item group was not being fully cleared from the TK index.
  • Salesforce Integration 5.17.3: input validation has been updated for "Schedule indexing status reset" panel to better highlight when the frequency is incorrectly set to less than 60 minutes.

October 30, 2023

Enhanced

  • Salesforce Integration 5.13.4: preview of upcoming match automation feature added to package and public documentation. The feature will allow Texkternel to automatically publich a platform event with the best-matching candidates whenever a new job is created in Salesforce.
  • Salesforce Integration 5.13.4: preview of upcoming candidate engagement feature added to package and public documentation. The feature will allow recruiters or Salesforce automation to trigger automatic candidate engagement communication via Whatsapp.
  • Salesforce Integration 5.13.4: preview of upcoming high-throughput indexation feature added to package and public documentation. The feature will enable faster search indexation for large enterprise customers, especially during initial platform setup.
  • Salesforce Integration 5.13.4: a new scheduled job periodically runs in the background to check indexing status records to see if the indexation request is hung, and if so, it resets the request so that it will be automatically retried.
  • Salesforce Integration 5.13.4: a new monitoring panel shows the Salesforce admin the number of platform events and the event action type for the events that the Textkernel integration generates. Admins can see how many events were published in the last hour and in the last day.
  • Salesforce Integration 5.13.4: a new monitoring panel shows the Salesforce admin the status of candidate profiles being parsed and converted. The panel also allows the admin to reset errors.

Fixed

  • Salesforce Integration 5.13.4: in recruiter CV parsing, a bug was fixed where leaving out a fieldset configuration from the de-duplication setup could cause an error. Now the screens don't show fields, but the misconfiguration does not break the entire flow any more.

September 27, 2023

Fixed

  • Salesforce Integration 5.6.16 (hotfix): a bug was fixed where guest site users could not update mapped candidate records, because the indexation Flow trigger did not properly handle access permissions. This release is a hotfix that has been pushed to all orgs running version 5.6.x.

September 15, 2023

Fixed

  • Salesforce integration 5.6.12 (hotfix): During search indexation, the push indexation architecture was incorrectly trying to index records that were locked with the "Submitted for ..." status. In addition, a bug was introduced in 5.6.10 that caused indexation jobs to sometimes crash. This release is a hotfix that has been pushed to all orgs running version 5.6.x.

September 11, 2023

Enhanced

  • Salesforce integration 5.6.10: starting with package version 5.6.4, the "is Locked" field on the Textkernel Indexing Status (TIS) record is no longer used to lock the record; instead the new "Submitted for..." status values indicate that the TIS record is locked. However, in some cases the TIS record "is Locked" field was still being set and checked. This issue is now fixed.
  • Salesforce integration 5.6.10: Under Textkernel Monitoring, the indexation status table has been updated to show the new "Submitted for ..." status values.
  • Salesforce integration 5.6.10: During search and match configuration, under Indexation settings, the "Indexing status records" panel has been updated to count TIS records having the new "Submitted for ..." status values.

August 23, 2023

Enhanced

  • Salesforce integration 5.6.8: Infrequently, when re-starting indexation, SFDC admins see a generic error message: “Can not schedule Batch”. The log message has been updated to give more details about the error.
  • Salesforce Integration 5.6.8: when importing candidate data (with recruiter CV parsing or importing from external sources), all parsed data fields are now truncated when loading the data into Salesforce. Previously, there were infrequent data-specific cases where long text fields blocked the entire import operation. Now the import will proceed with truncated data.

Fixed

  • Salesforce Integration 5.6.8: Two new fields were recently added to the Textkernel Indexing Status (TIS) records in the package: RemovalRequestWhenBusy__c and IndexRequestWhenBusy__c. A bug has been fixed to make these new fields visible to all users. All TIS fields should be visible to all users so that the indexation mechanism works properly.
  • Salesforce Integration 5.6.8: a bug was fixed in the Search and Match Setup area, where the button to generate missing Textkernel Indexation Status records was ignoring the filtering formula field values.

June 27, 2023

Enhanced

  • Salesforce Integration 2.6.4: for search and match use cases, there is a breaking change to improve the indexation infrastructure. When a record has been submitted to the APEX Flex queue for indexation or removal, instead of using the "Lock" field on the Textkernel Indexing Status (TIS) record to indicate it is busy, we now set a meaningful value on the Status field: either "Submitted for indexation (Push)", or "Submitted for removal (Push)".In addition, we have improved the lock management in the invocable APEX classes ("Upsert record to Textkernel index", and "Delete record from Textkernel index") so that if the TIS record is being actively indexed when a new indexing request is made via the classes, then that request will be handled without a record-locking conflict.When installing this version, the Salesforce admin needs to follow the special upgrade procedure outlined here:https://drive.google.com/file/d/1lJA6HxkCjb7mnCz_fpWQWsLkCfiweSxF
  • Salesforce Integration 5.6.4: a data volume/capacity limitation was addressed in the search infrastructure, so that it is now possible to use the "Generate Missing Status Records" feature for Salesforce orgs with 20+ million Candidate records.
  • Salesforce Integration 5.6.4: When configuring the candidate or vacancy data mapping for search indexation in the Salesforce app, it is now possible to map up to 10 custom text fields, 5 custom date fields, and 5 custom number fields.
  • Salesforce Integration 5.6.4: when configuration the candidate data mapping for search indexation, the optional "Job Submissions", "Placements", "Contact Lists", and "Comments" are now enhanced to support 5 custom text fields, 3 custom date fields, and 3 custom number fields.

Fixed

  • Salesforce Integration 5.6.4: in recruiter CV parsing, a bug has been fixed that prevented the mapping of parsed geocoordinate data to the converted candidate object in Salesforce.
  • Salesforce Integration 5.6.4: a bug was fixed to improve the stability of the background job that parses textkernel imported external candidate records that were imported from the Source UI.
  • Salesforce Integration 5.6.4: in the recruiter CV parsing workflow, a bug was fixed relating to the manual deduplication flow. The fix is a breaking change, so please review the configuration instructions here:https://drive.google.com/file/d/1lJA6HxkCjb7mnCz_fpWQWsLkCfiweSxFWhen the admin decides which fields should be reviewed by the recruiter, previously the field names of the target converted candidate, work experience, and education objects needed to match the field names of the internal Textkernel imported candidate, work experience, and education object. That restriction is now removed to provide the intended data model mapping flexibility.Now the admin should define a fieldset on the converted candidate / work experience / education objects to indicate which fields should be displayed during de-duplication pop-up window. The fields in the window must all be mapped fields in the parsing data mapping. Note that, it is not possible to map to a custom formula field on the target converted candidate / work experience / education objects, because they are not writable and cannot be mapped.

February 28, 2023

Enhanced

  • 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.
  • Salesforce Integration 5.3.23: recruiters can now import a record from Jobfeed search results in the Jobfeed portal search UI inside Textkernel Portal.
  • Salesforce Integration 5.3.23: Jobfeed Switzerland is now supported for all Jobfeed workflows.
  • 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

Fixed

  • 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.
  • Salesforce Integration 5.3.23: Fixed spelling mistakes on 2 fields in the search candidate mapping page in the Textkernel configuration app
  • Salesforce Integration 5.3.23: Jobfeed import widget has been fixed so that account names containing '&' symbol can be imported.

December 12, 2022

Added

  • 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.

November 29, 2022

Enhanced

  • PersonCustomObjectInstance events are now supported in the Bullhorn Connector.

November 11, 2022

Fixed

  • 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.
  • 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.

November 7, 2022

Enhanced

  • Salesforce Integration 4.10.9: enhanced indexation engine to work for Salesforce orgs using Bullhorn Connexys to parse/create Candidate records.

Fixed

  • Salesforce Integration 4.10.9: fixed an uncommon issue during search indexation where an error was recorded "Start did not return a valid iterable object".
  • Salesforce Integration 4.10.9: fixed an issue during search indexation where an invalid CV/resume with enormous file size caused an out-of-memory error "Apex heap size too large".

October 19, 2022

Enhanced

  • For finding duplicates in Bullhorn candidates, email address has now been given more weight than the combination of first and last name. This means that candidate records that share the same email address will be considered more likely to be duplicates.

September 21, 2022

Enhanced

  • Salesforce Integration 4.10.6: in the Search and Match feature, when Platform Events are emitted from either TK Portal or the Automatch widgets, their parameters are now harmonized to have the same structure. Furthermore, in previous versions, the record IDs returned by Platform Events had a prefix of the SFDC Organization ID followed by "". Starting with this release, the OrgID prefix is removed to make it simpler to use the Platform Events in Flows, APEX, or other Salesforce automation.The Unlocked Component package is also updated to version 2.0.3 to be compatible with the new Platform Event structure.
  • Salesforce Integration 4.10.6: the Search & Match indexation infrastructure now checks whether any mapped data fields changed since the last successful indexation from Salesforce into Textkernel's search index. If there was no change on a mapped field, there is no need to re-index the data. This significantly improves indexation throughput when records are updating/changing inside Salesforce.
  • Salesforce Integration 4.10.6: in the Search and Match features, when the Candidate/Vacancy record has not yet been indexed, the automatic matching widgets in Salesforce now automatically index the starting record so that matches can be presented to the Recruiter.

Fixed

  • Salesforce Integration 4.10.6: in the Search and Match feature, a problem was fixed where Candidate re-indexation failed in this scenario: 1) a Candidate was added to the Textkernel index; 2) then the filter logic calculation changed so that the Candidate was correctly removed from the Textkernel index; 3) then the filter logic calculation changed so that the Candidate should be re-indexed into the Textkernel index.
  • Salesforce Integration 4.10.6: in the Search and Match feature, when using the package's invocable Apex classes for indexation, the feature to immediately update/insert a Vacancy into Textkernel's index no longer requires a package license or permission set. This change allows non-recruiter Salesforce users to update Vacancies without causing package-access problems.
  • A bug was fixed for API integrations with Sourcebox. The bug occurred when a TMF was submitted to Sourcebox, and at the same time an empty file as a CV (or an invalid non-CV file) was also included. The fix is that we cover this case to add a "No CV" definition to the Trxml Document, which enables the TMF to be indexed in search.

September 20, 2022

Fixed

  • Salesforce Integration 4.9.2: fixed an issue where TK indexing status records generated using the "Generate missing records" button in the admin interface had an incorrect configuration for partial updates.
  • Salesforce Integration 4.9.2: fixed an issue where some STRING type fields were missing from some of the mapping pages when configuring Recruiter CV parsing.

Added

  • SFDC Integration 4.9: Enhanced the indexation architecture, so that Candidates CV are only reparsed during indexation to TK when necessary (eg when Candidates are first created). This is a significant throughput enhancement to the indexation infrastructure.

September 19, 2022

Enhanced

  • Salesforce Integration 4.8.3: fixed an indexation issue on the Vacancy object where CustomMultiText and CustomNumeric fields were not being indexed, even when the Salesforce administrator had mapped them.

Fixed

  • Salesforce Integration 4.8.3: fixed an issue during indexation where Candidate.CustomText10 was incorrectly mapped to Candidate.CustomText2 during indexation to the Textkernel Search Index.
  • Salesforce Integration 4.8.3: fixed an issue where a false error message popped up mentioning the Platform Event ID when importing a Jobfeed Job from the external Jobfeed searcher inside Textkernel Portal.

June 11, 2022

Enhanced

  • Salesforce Integration 4.7: during the Search & Match indexation process, occasionally the integration logged an unclear message "attempt to dereference a null object". That message has been updated to provide more meaningful details/explanation for the Salesforce administrator.
  • Salesforce Integration 4.7: under Search and Match Setup, when the Admin is exporting and importing the Candidate Data Mapping, the configuration file now supports the option "Use Attachment instead of File Object"
  • Salesforce Integration 4.7: during recruiter CV parsing, sometimes the widget cleared the CV status after conversion, which prevented the recruiter from directly clicking through to view the converted candidate record. That behaviour has been adjusted so that the widget retains the import status longer.
  • Salesforce Integration 4.7: when importing a Textkernel Jobfeed Job into Salesforce from the Account widget, a link to the Account is now saved to the Textkernel Jobfeed Job record to preserve the relationship on the record.

May 9, 2022

Enhanced

  • Salesforce Integration 4.6: updates to ensure that recruiter-facing UI text labels in the Textkernel packages are defined as custom labels, allowing customer SFDC admins to customise them for their integration, and/or translate them using the standard Salesforce translation workbench tool.
  • Salesforce Integration 4.6: the recruiter parsing flow now allows a customer admin to configure a partner-managed multi-tenant parsing pipeline.
  • Salesforce Integration 4.6: when checking to see whether a Salesforce User has a required Textkernel package permission set, we now also check to see if the Permission Set was assigned inside a Permission Set Group

Fixed

  • Salesforce Integration 4.6: the APEX feature allowing fast indexing of Vacancies has been fixed to set the correct indexing priority again.
  • Salesforce Integration: fixed a problem where the Automatch widget for a Candidate had incorrect errors about data field access permissions. The issue occurred when the Contact object was configured as the Candidate object.

April 9, 2022

Enhanced

  • Salesforce Integration 4.5: a new widget is available for the Vacancy page which shows the best matching Candidates for that Vacancy, inside Salesforce. A configurable button can be used to trigger workflow actions from the widget, or recruiters can click through to view the full match results.
  • Salesforce Integration 4.5: a new widget is available for the Candidate page which shows the best matching Vacancies for that Candidate, inside Salesforce. A configurable button can be used to trigger workflow actions from the widget, or recruiters can click through to view the full match results.
  • Salesforce Integration 4.5: a new widget is available to import job postings from Jobfeed into Salesforce from the Salesforce Account view.
  • Salesforce Integration 4.5: Jobfeed jobs can now be imported into Salesforce in batches when viewing Jobfeed searcher results in the search and match features.
  • Salesforce Integration 4.5: recruiter CV parsing now extracts skills from CVs. Skills are not mapped to the converted Candidate object as part of this feature, but Flow or APEX can be used to map the parsed skills to the internal skill data model as needed.
  • Salesforce Integration 4.5: recruiter CV parsing now extracts work experience and education items from CVs, and they can be mapped to the target Converted Candidate object.

March 28, 2022

Enhanced

  • Salesforce Integration 4.4.1: There is a new version (2.0) of the Unlocked Components package which should be used with versions 4.x:https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1v000001pIgUAAU
  • Salesforce Integration 4.4.1: the integration now supports indirect SFDC users of the Search and Match indexation infrastructure without requiring a TK package license or permission set assignment. (Indirect users are non-recruiters who need to change Candidate and/or Vacancy records)

Fixed

  • Salesforce Integration 4.4.1: a bug has been fixed where some Salesforce users with the Textkernel Recruiter permission set were unable to use the matching component.
  • Salesforce Integration 4.4.1: an issue has been fixed where, for some configurations, the exported Candidate and/or Vacancy data mapping contained extra information, and could not be imported back into Salesforce.

February 10, 2022

Added

  • Documentation on how to integrate with TK Portal is now available athttps://developer.textkernel.com/

January 27, 2022

Enhanced

  • This version of Sourcebox introduces a change where alert, prompts and confirmation dialogs no longer appear as browser prompts, but instead are consistent with the rest of the look and feel of the application. This does not affect their functionality, which remains the same. This is in response to Google Chrome deprecating the usage of these functionshttps://chromestatus.com/feature/5148698084376576

December 13, 2021

Fixed

  • Salesforce Integration 3.2.1: Fixed an issue where matching buttons in Salesforce did not work in some situations

November 15, 2021

Enhanced

  • Salesforce Integration 3.2: Fixed a UI issue where the Textkernel Portal Settings configuration page asked to save changes even when the changes had already been saved.
  • Salesforce Integration 3.2: add support so that saved search alert emails include links which can be clicked to redirect the user into the Salesforce search results environment.

November 8, 2021

Enhanced

  • Bullhorn search & match environments can now support the field JobOrder.location

October 25, 2021

Added

  • Salesforce Integration 3.1: New permission set called "Textkernel - Manager Access" allows managers to view TK search usage reports

September 27, 2021

Enhanced

  • Salesforce Integration 3.0: The default global search document access policy is now properly set when customers are not using data segregation.
  • Salesforce Integration 3.0: The Textkernel search data model has been enhanced so that work experience and education items will be merged in the search index (ie, merge SFDC structured data with data extracted from the CV/Resume). Important: to take advantage of this change when upgrading from older package versions, customers will need to reindex all data to Textkernel Search. Customers should coordinate this upgrade with Textkernel support.
  • Salesforce Integration 3.0: Two new buttons are available on the Textkernel Indexing Status record to enable SFDC admins to see what data is being sent from Salesforce to the TK search index. “Get TK Record XML” downloads the structured data being sent to Textkernel, and“Get TK CV/Vacancy File" downloads the binary CV/Vacancy being parsed when sent to indexation.

August 24, 2021

Enhanced

  • Salesforce Integration 2.6: Enhancement to Search/Match indexation settings, where admin can directly set the limit of indexation jobs to be submitted to the APEX Flex queue. This new control replaces the previous thread limit control, which is now deprecated as we simplify throughput management.
  • Salesforce Integration 2.6: new feature for Recruiter CV import/parsing where optionally a Record type can be defined when creating imported records inside Salesforce

Fixed

  • Salesforce Integration 2.6: We have fixed a scenario where the admin user could not disable the search and match indexation job using the cancel button.

August 6, 2021

Fixed

  • Salesforce integration 2.5.2: fix issue where sometimes TK indexation process would schedule next job too far in the future.

July 29, 2021

Added

  • Salesforce integration 2.5: new feature to support fast indexing of Vacancies, via new parameter on APEX method, including a Platform Event to confirm when the fast index operation is complete.

Enhanced

  • Salesforce integration 2.5: add ability to disable Trigger inside package checking for CV-Attachment changes for cases where customers maintain a Trigger outside of the package
  • Salesforce integration 2.5: Enhancements to batch indexing process, so that it limits the number of indexation batch jobs submitted to the Salesforce APEX Flex queue to better share with other Salesforce processes. Also set a lower default job limit of 20 rather than 100.

Fixed

  • Salesforce integration 2.5: fix on language tag being sent from Salesforce into TK during indexing to improve match results for Salesforce candidates without a CV

July 19, 2021

Enhanced

  • Salesforce integration 2.4: add support for using Salesforce Attachment object to represent Candidate CVs (previously only supported File object)
  • Salesforce integration 2.3: performance optimisation on queries running in Salesforce to more efficiently support users with millions of Candidate / Vacancy records

July 12, 2021

Enhanced

  • Salesforce Integration 2.2: change external index field on Textkernel Indexing Status record so that it is always indexed by Salesforce

Fixed

  • Salesforce integration 2.2: fix scaling issue affecting customers with several million Candidates where some queries we causing the indexation setting page to load slowly.

June 29, 2021

Enhanced

  • Salesforce integration 2.1.2: add support to data model mapping tool for 3 additional custom objects on Candidate and 5 additional custom objects on Vacancy
  • Salesforce integration 2.1.2: fix error during recruiter CV parsing where status of conversion showed OKOK instead of OK
  • Salesforce integration 2.1.2: enhanced error checking during admin configuration page, so that if the admin navigates away without saving changes they see a pop-up warning telling them to save their changes.

June 8, 2021

Enhanced

  • Salesforce Integration 2.0.2: Fix scrollbar on side of Textkernel App mapping configuration pane

May 18, 2021

Fixed

  • Fixed issues with CV upload and editing profile when using IE11 in mobility setups.

May 3, 2021

Added

  • Salesforce Integration 2.0.0: For Recruiter CV Parsing: allow admin to map parsed data fields to custom environment objects.
  • Salesforce Integration 2.0.0: For Recruiter CV Parsing: allow admin to export/import data mapping to/from a file.
  • Salesforce Integration 2.0.0: For Recruiter CV Parsing: allow recruiters to review parsed data when importing Candidate records
  • Salesforce Integration 2.0.0: For Recruiter CV Parsing: check for existing duplicates when inserting new Candidate records.
  • Salesforce Integration 2.0.0: For Recruiter CV Parsing, store parsed data onto an imported Candidate landing record

Enhanced

  • Salesforce Integration 2.0.0: Add documentation for new recruiter CV parsing feature
  • Salesforce Integration 2.0.0: Add widget to import CVs for Recruiter CV Import

March 15, 2021

Fixed

  • Fixed an issue where, in some cases our Bullhorn native integration was unable to import some of the custom text field data from the customer environment to the Textkernel Search & Match index.

Removed

  • Removing Lead Entity support from Bullhorn native integration indexation. The Lead is an optional entity, which only some Bullhorn customers use, and it is not a useful concept for our Candidate/Job sourcing and matching use case, so we are no longer indexing it.

January 27, 2021

Fixed

  • Previously, in some cases, if an existing Bullhorn username was changed inside Bullhorn, that user could no longer be synced into Textkernel portal to allow them to access Textkernel. After this change, Textkernel will allow the username to change in Bullhorn.

January 18, 2021

Added

  • Bullhorn accounts can now be configured with an additional Bullhorn action menu item that will 'Rank Applicants' when opening Textkernel Match results from a Bullhorn JobOrder. In this case, the displayed matching Candidates are filtered to show only those with JobSubmissions and/or WebResponses against the Bullhorn JobOrder, so that recruiters can quickly see the best applicants for a role to decide which ones to progress.

Fixed

  • Previously, in some cases, if an existing Bullhorn username was changed inside Bullhorn, that user could no longer be synced into Textkernel portal to allow them to access Textkernel. After this change, Textkernel will allow the username to change in Bullhorn.

January 12, 2021

Added

  • Salesforce Integration: Admin user can click a button to attempt indexing all Candidate/Job records in SFDC that had a permanent error from previous indexing attempts

Enhanced

  • Salesforce Integration: In indexation monitoring report, show counts of records with a temporary indexing error in addition to showing permanent errors.

January 8, 2021

Added

  • Compatibility for Taleo 20D.0.8

December 7, 2020

Enhanced

  • Error severity levels have been revised and updated for the Extract SOAP API, including advice on retrying strategies for better error handling. Some error IDs have been changed. For more details, refer to the Sourcebox API Reference documentation.

September 28, 2020

Fixed

  • Bullhorn users were not able to import candidates from external sources.

September 25, 2020

Added

  • New feature for the Talentsoft Marketplace Match integration for the user can set a query term / tag as either Mandatory (Must-have) or Optional (Nice-to-have).

August 31, 2020

Added

  • For users with admin rights, it is now possible to export users information in CSV format, including the status of the user and usage dates, among others. This improves the user experience, who until now relied on copy-pasting information from the screen into a spreadsheet for their reporting needs.Note: the new option can be found under the 'Users' button on the top left side of the screen. This button used to be labeled 'Add Users'.

Fixed

  • When using Textkernel's Bullhorn Native integration, and importing from an external searcher to create a new record in Bullhorn, the Candidate Inbox document should be associated to the user's Bullhorn Native User ID, instead of a shared user (i.e. 'export'). This means that documents will now be listed in 'My Documents' in the Candidate Inbox.

June 8, 2020

Enhanced

  • In the Bullhorn-native integration, de-duplication was originally designed for single-tenant environments. It has been extended to work with multi-tenant orgs so that Bullhorn BusinessUsers will only see possible duplicates according to their Departments. This does not require configuration.

January 6, 2020

Added

  • Initial release of the Talentsoft Match Integration. This is a plugin allowing Talentsoft users to automatically find the best Candidates starting from a Vacancy, and find the best Vacancies starting from a Candidate.