Release Notes - Connexys v 31.11.3


This article is an overview of the most important improvements and fixes for release v31.11.3


  • API Upgrade  - Important Information to note
  • Improvements
  • Fixes

API Upgrade

From version 31 onwards, the Connexys Package supports Salesforce API version 51.0.  This follows their announcement that versions 7.0-20.00, and 21.0 to 31.0 are soon to be retired:-

This enables our application to function with the most current API versions available in order to prevent any disruption caused by software referencing retired versions. 

Moving to newer versions of APIs will offer advanced capabilities with improved Salesforce security and performance. 

Our Quality Assurance Team ran extensive Regression Testing to verify that there is no adverse impact as a result of this change.

Whilst no impact was reported, we would strongly recommend extensive testing if you are upgrading from a version lower than v.31 to verify the changes have no impact on any custom configuration.









Show TK Management component in different languages


It is now possible to show the TK Management component in the user's language.

Translations will need to be added to the custom labels of the TK Management component.

To set up, Go to Setup > Custom Metadata Types > click in front of "Textkernel configuration" on Manage Records > click on Textkernel Portal > Supported languages. 

If you don't see the field, you need to add it to the page layout. Click on Edit and paste the following in the field: en,de,it,fr,es,nl > then click on Save.



Go to Setup > Users > click on your user > Edit > Language > , for example, choose: Deutsch (German) > Save.

To test :

Open TK Portal > scroll to TK Management component (Index status section).

Expected result:

TK Management component fields are shown in users language (in this example a German translation for the label (Candidates (Total) was added.


Relevant to  - Customers who monitor indexing between Connexys and Textkernel via the Management component, and wish to customise the language display



Textkernel Management - Contacts (Total) and Jobs (Total) should be displayed instead of Indexable candidates and Indexable jobs


It was reported that the query to display the number of Indexable Jobs and Candidates was timing out and unable to complete.

This is now resolved with a change to the query to display the total number of all Candidates and Jobs.

When viewing the Textkernel Management component now, users should see the fields as below -



Note - When a user doesn't have View setup and Configuration permission they will see 'unavailable' in Candidates (Total) and in Jobs (Total) - 



To test, verify the Textkernel Management component has the new fields visible, and if desired, query the count of all objects - Candidates/Contacts and Jobs to validate the results match.

Relevant to - Customers who monitor indexing between Connexys and Textkernel via the Management component












When editing jobs through the job wizard, the wizard loader keeps spinning


When launching the Job Wizard via a custom button, a parameter was defaulting to an empty value.

However, the code assumed a value to exist, and generated invalid javascript as a result.

This has been fixed by ensuring the parameter has a default value of false.

 For testing, we verified that editing a job via a custom button, using the ‘JobWizardLightning’ page is now possible.

This change also has no impact on cloning jobs, or editing jobs using the Job Wizard without a custom button.

Relevant to  - Customers who launch  the Job Wizard via a custom button.


Cloning using JobWizardLightning Button Removes Job Title/name


It was reported that when cloning a job, the cloned job gets the RecordID as the job title, not the actual job title entered in the field.

This is now resolved.  Now, all fields entered during the clone process are saved to the cloned job record, as opposed to saving the edited fields only.

Different VisualForce page sets for the Clone button were also used for testing and passed.

To test, go to a test Job, click the Clone button, and fill all mandatory fields on the form, and click ‘Save’.    All fields in the new cloned job should be visible.

Relevant to - Customers who have repeat bookings and clone jobs on a regular basis.


Was this article helpful?
0 out of 0 found this helpful


Powered by Zendesk