Release Notes - Connexys v31.8.2


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


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









Captcha is now implemented on the Job Alert Mobile page and Mobile Search Apply page


In v31.7.1 we introduced the ability to enable Captcha in a few areas.  This has now been extended to the Job Alert Mobile Page.  Once enabled, users will see a checkbox that must be ticked to verify that they are a real person.  For full details, please refer to the Release Notes for 31.7











Proposal portal link does not load if duplicate application settings with different language values are present


This issue is now resolved. Cloning Proposal Portal related Application Settings with different Languages, no longer results in the error : 'Error generating content:List has more than 1 row for assignment to SObject' being displayed in the Portal.



In some cases, candidates cannot be anonymized, an error message “Attempt to de-reference a null object” appears.


This is now resolved. The issue appeared where there were no labels of fields - e.g. ‘Owner’ in the Chatter Feed on initialization of the VisualForce page. We now check if the field is in the keySet and if not, get the Label of the Field Name. Users must ensure that a label for record ‘Owner’ exissgt, and has translations for it, if translation is required.

This change does not impact any logic in the anonymization process.




When using HTML for creating hyperlinks in forms, and using a word like 'Link' (< a href ="url">link text < /a > the capital letter (in this case L) is changed into a small letter.



This has now been resolved.

The issue was happening because of a RegExp to convert all special merge items (such as link, link.proposal, candidate etc) to lowercase.

This issue was verified as fixed in the case of requesting updates for candidates, creating proposals, and sharing with hiring manager,


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