Release Notes - Connexys v31.10.7


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


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









Add user friendly error messages for Captcha


Better, user friendly error messages have now been implemented when exceptions occur if Captcha is enabled.  The following labels were updated:

Captcha_timeout_exception -> 'Please click the checkbox in Captcha again to indicate that you're not a robot.' (New metadata)

Captcha_verification_failed -> 'Captcha verification failed. {0}'

Invalid_input_secret -> 'Captcha configuration is invalid (The secret parameter is invalid or malformed). Please contact your administrator.'

Missing_input_secret -> 'Captcha configuration is invalid (The secret parameter is missing). Please contact your administrator'

No_response_key -> 'Please click the checkbox in Captcha to indicate that you're not a robot.'


Latest Gen CV not added as attachment to workflow step


This issue is now resolved.

Because of the difference of CV creation with Documill and VisualForce template, the latest generated CV (Documill) couldn't be found.

 To fix the issue, a statement to check the way of CV creation was added.

For testing, we verified that the generated CV automatically gets added to the workflow step that it was generated in as an attachment or link for both Documill and the VisualForce CV generator.

The following setting needs to be enabled for the step: 'Add latest Generated CV to Email'.

Go to Connexys Setup > Workflow steps > Share candidate with hiring manager. Verify that the settings are setup as follows:













Textkernel Portal does not properly recognize partial updates


It was reported that most TK indexing status records are for FULL_UPDATES instead of PARTIAL_updates. PARTIAL_UPDATES should be processed significantly quicker because this skips the CV parsing stage of indexing. 

It was identified that the triggers (the activity or action) that initiates the indexing process - FULL or PARTIAL, were incorrect.  These have now been updated as follows:-

  • New Candidate FULL
  • Existing Candidate PARTIAL
  • New CV FULL (specific cv not the other docs)
  • New/changed Hard criteria PARTIAL
  • New/changed Education PARTIAL
  • New/changed Employment PARTIAL
  • New Job application  - 
    • FULL update on Job; FULL  update on Candidate (with new cv) 
    • PARTIAL update on Candidate (without cv)
  • Changed Job application:  NONE (no action taken)
  • New/changed Talentpool PARTIAL

For testing, we verified that creating and updating the following record types triggered FULL or PARTIAL updates as expected above.

  • Contact
  • Candidate
  • Job Applications



Large backlog of records to be indexed for TK Portal


It was reported that a large number of backlog of records can be queued up for indexing by TK Portal.

This was due to the ownership of indexing status records being the Site User, and not the same as the owner of the candidate records.  Now the owner of the status record is the owner of the candidate record, and these records are now without sharing and updates to these records are performed with the appropriate permissions.

For testing, we verified that new candidate records created by your user were visible in TK Portal, and candidates created in response to job applications were visible in TK Portal as expected.  This testing verifies that the above logic change with ownership handling does not affect visibility of candidates.




When a candidate is indexed in TK, a System.DmlException: invalid record id error is thrown on the cxsCandidateTrigger. This results in the candidate not being updated.



This is now resolved.

This error can occur when two separate transactions are both trying to index and update the same record. If the index transaction finishes first, the record will be deleted before the update transaction has a chance to finish.

For Connexys, this has the effect that when applying for a job with Work Experience and Education entries, it created two status records since this is handled into two transactions: the candidate itself and the WE and EDU creation future.

For testing, we verified the following scenarios after this change, completing all fields for the candidate, including creating Education and Work History entries:-

  • Create a candidate and job application using a Javascript Apply Form
  • Create a candidate using Search Apply Form
  • Create a Job Application from a CV using the Javascript Source Box form

In all cases, the tests were passed, no error messages were shown in the debug logs, and the candidate was visible in TK Portal.



Deleted Hard Criteria still appears on a candidate in TK Portal


This has now been resolved.  

To reproduce this issue, locate two test candidates that are visible in TK Portal.  One candidate should have a language value in the Hard Criteria section.  Edit the candidate, and delete the language from the candidate, save and confirm a PARTIAL_UPDATE has been completed.  Back in TK Portal, the language will still appear.

With this change, the above scenario is no longer recreated, deleted Hard Criteria, are no longer visible on a Candidate in TK Portal

We have now added the possibility to have empty nodes in the TMF template, by adding attribute bhtk:allowEmptyNode="true".  For example,  for Candidate object and language hard criteria type node will look like:


<ItemGroup key="tr1__language__c" bhtk:allowEmptyNode="true" bhtk:iterationObject="cxsrec__cxsHard_criterium__c" bhtk:iterationField="cxsrec__Candidate__c" bhtk:iterationSelector="cxsrec__isLanguageSkill__c">
<Item index="0">
<Field key="tr1__language__c" bhtk:object="cxsrec__cxsHard_criterium__c" bhtk:field="cxsrec__Hard_Criterium_Value__r.Name">
<Value />
<Field key="level" bhtk:object="cxsrec__cxsHard_criterium__c" bhtk:field="cxsrec__Level__r.Name">
<!-- Send either the level code OR the langprofi_code. Not both. -->
<Value /> <!-- Free text field. Will be normalized to a language proficiency code. -->


Template set up is accessed from: Setup ->Custom Metadata Types -> Textkernel object configurations -> Manage Textkernel object configuration->  Candidate (or needed sObject) -> Template field


For Connexys it would be logical to add this new flag (bhtk:allowEmptyNode="true") to Skills, Languages and Talent Pools sections



It is possible to click the Submit/Send button multiple times on the cxsUpdateProfileRequest



This has now been resolved.  

As this is a public page, we have implemented a captcha to prevent users being able to click the submit button multiple times.

With the captcha enabled, the 'Submit/Send' button on the 'Request Update page' will be disabled upon click, preventing any extra submissions.

The above scenarios as tested in CXS-2665 were also tested in conjunction with this change, and were all passed. 


CXS-2804 Heap Size limit being hit by cxsPositionWebservice.getPositionsByIds  

This has now been resolved.  

It was reported that users were unable to post jobs, and were blocked with an error ‘System.LimitException: Apex heap size too large’

The cause of this was down to logic that was cleaning up HTML code in the Position fields twice, first when position records are inserted, and again when jobs are requested via web services.

We have made some changes to the logic as follows.

When the Enable_StylingCleanup_for_PositionWebservice setting is NOT checked, the following fields will NOT have the basic HTML formatting stripped (font colours and styling):-

  • job requirements
  • compensation benefits
  • job description
  • company information
  • Contact info

Please note that for large data sets, we strongly suggest that requests for jobs to the webservice are batched up into smaller chunks as the heap size limit could still be met, even with these improvements.

To verify the change, go to Connexys Setup>Connexys only settings>Application Settings>All settings>Enable_StylingCleanup_for_PositionWebservice


With the above setting enabled (Boolean Value field is ticked), font/styling is removed from Position web service, so jobs should be received by your website, without html formatting applied.

With the above setting disabled (Boolean Value field is unticked), font/styling is retained and passed on in the jobs returned via the web service.


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


Powered by Zendesk