This article is an overview of the most important improvements and fixes for release v31.2.5
Content
- API Upgrade - Important Information to note
- 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:-
https://help.salesforce.com/s/articleView?id=000351312&type=1 https://help.salesforce.com/s/articleView?id=000354473&type=1
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, this version will initially be rolled out to Customers who have a Sandbox environment in place for further testing. Once we have confirmation that user acceptance has been achieved, we will start looking to roll this version out to the rest of our customers over the coming months.
Fixes
|
Identifier |
Description |
|
Notes |
|
CXS-2386
|
When posting jobs to Broadbean in Lightning, users were being switched to Classic when being redirected back to the main job details. |
This issue is now resolved. Users who are using the Lightning interface will remain in Lightning when posting jobs to Broadbean. | |
| CXS-2335 |
When generating CVs, edits that should have been discarded, were actually being saved, and visible once re-opening closed CV’s. |
This issue is now resolved. To solve it, we have created a new field to store generated CV data for saved and published records In case when 'Use_latest_Published_genCV_as_default_source' application setting is checked CV data for the left side of CV Generator will be taken from Saved_CV_Data__c field. The old field works as before. |
|
| CXS-2330 | In some cases when generating CVs, files were being created without a file name.
|
This has been resolved. The issue was occurring on initialization of the CV Generator. Intermittently, the ‘quickSave’ method was called before ‘getCVGeneratorData’ was executed, which is where CVPDFName is populated.
|
|
| CXS-2191 | An issue with the Textkernel candidate import service meant that users were unable to view candidate applications from CVLibrary. |
This has been resolved by adding additional parameters in the call to the import service. Now users are able to click on the ‘View Candidate’ link in Textkernel Search, view the candidate, and the CV. |
|
| CXS-2397 | After release 30(8.2) the URL in our packaged fields on the job, for example: cxsrec_Compensation_benefits_c, is displayed empty. |