|
|
|
Release Notes - 26.05.02 (May 26)Release: This release consists of the development undertaken under the sprints: 26.05.01, 26.05.02. Key Features: Updates include new auto responsive skills search bar, error handling on document preview, minor UI and bug fixes. Upgrade Date: 30/05/26 |
|
|
|
|
|
|
EnhancementsSKILLS - New Auto-Responsive Skill Search Bar The Search bar on the Skills tab of all main entity records has been updated to be responsive as you are typing, rather than needing the user to press 'Enter' or 'Tab':
CONTACT - Mark As Leaver 'Reason' Field Mandatory Setting The 'Reason' field on the 'Mark As Leaver' workflow will no longer be hardcoded as mandatory. This will now be based on a Global Setting. Admin > Global Setting > Contact > Make the reason section on Mark as Leaver mandatory: Yes/No
COMPANY - Company Registration Number field added to Overview Tab Further to demand, the Company 'Registration Number' has been added to main Overview tab on the Company record.
|
|
|
|
Bug FixesGetDocumentHTML Error Handling The code used to establish the HTML needed to generate the document preview on the CV Parser, and on all main entity records (when uploading a new document), required extra error handling. These updates help to capture and prevent situations where performance issues can occur.
History Document Refresh When scrolling through histories, it was raised that a history attachment can appear one history and then stay in the preview pane for the next history (if that next history did not have an attachment). This has now been resolved.
Company Name Search on Contact Lookup Partial View It was raised that when doing a Contact lookup, and using the 'Company Name' field, this was not only returning Companies with the same name. This has now been resolved.
Candidate Type Search - Incorrect Results When performing a search on the Candidate Type field, there was an incorrect statement being used in the SQL which could result in similiar coded 'Type' codes being found. This was a unique scenario and only relevant for clients using their own custom lookup codes. This has been resolved.
|
