MSR Recruitment Fixed Features 2026-04

INDEX

• 100612 | Portal application fails when multiple candidate duplicates exist
• 100958 | Various visual inconsistencies resolved when using SLDS2
• 101792 | Various display issues in Skills component and star rating
• 102101 | Search components visually deviate from Salesforce standard UI
• 102229 | CV parsing can produce errors due to invalid characters, dates and OCR processing
• 102801 | Negative duration in working days when processing job applications
• 102853 | Close button and surrounding buttons not visible in WhatsApp conversation window
• 102980 | Email action for candidate without email address showed "null" instead of a clear message
• 103049 | Unexpected blank lines in lists in generated documents
• 103411 | Multi-select picklist values showing technical values in list columns
• 103755 | CV and cover letter could be swapped for applications received via job boards
• 103912 | Granting portal access could fail for contact persons with spaces or special characters in their name
• 104115 | Sort order of completed tasks in the Activity Timeline could differ from the displayed date
• 104514 | CV Dropbox in the Utility Bar remained open after saving a new candidate
• 104651 | Unclear error message when using a WhatsApp template with an image header in a flow
• 105311 | Confirmation email for privacy choice was not saved in the Activity Timeline
• 105511 | Visibility condition based on a picklist was not correctly evaluated on the portal
• 105611 | Documents larger than 4 MB could not be opened or signed in the portal
• 105734 | Creating a job vacancy on the portal failed for non-English portal users

CONTENTS

100612 | Portal application fails when multiple candidate duplicates exist

When a candidate applied via the portal without being logged in and multiple duplicates of that candidate existed (three or more records), the application could not be created correctly. In this situation, the candidate was not linked to the application because the Contact was not processed correctly during the duplicate check. The candidate is now processed correctly even when multiple duplicates exist, ensuring the application is always linked to the correct candidate.

100958 | Various visual inconsistencies resolved when using SLDS2

When using the new Salesforce theme SLDS2, several minor visual inconsistencies occurred in the application. The following issues have been resolved:

• In the components used to select fields for display (for example in Search Persons or Application Process), the borders of the field lists were not correctly rounded and the focus on the search bar did not work correctly.
• Unintended white space was displayed before skill names.
• The font in Document Search and Search Persons was not proportional.
• The Search Now button still displayed borders from the old theme (SLDS1).
• In Text Search, an unwanted continuous line was displayed at the default criterion.
• On a long flow screen, the footer with the Next button was not displayed, making it impossible to navigate to the next screen without first collapsing sections on the screen.

All these visual inconsistencies have now been corrected.

101792 | Various display issues in Skills component and star rating

Several display issues occurred in the Skills component and when using rating stars. Stars were not displayed in the configured theme colour, could appear blurred, and in some cases it was not possible to remove skills with long names. Components could also overlap or not scale correctly on smaller screens. Rating stars now match the configured theme colour and are displayed more sharply. Improvements have also been made to the Skills component, including correct truncation of long names, better scaling behaviour and correct display of elements, making the component more consistent and user-friendly.

102101 | Search components visually deviate from Salesforce standard UI

In the Search Persons and Search Accounts components, non-standard UI elements were used, causing components such as the 'Search Now' button and object selection to visually deviate from the Salesforce interface. This resulted in an inconsistent user experience, particularly when using different themes. These elements now align with standard Salesforce UI components, making the display more consistent and better aligned with the rest of the application.

102229 | CV parsing can produce errors due to invalid characters, dates and OCR processing

When processing CVs, errors could occur in certain situations — for example when saving the CV text, processing dates, or reading documents. This could result in error messages or incomplete parsing of data. CV processing has now been improved so that invalid characters in CV text are ignored, invalid dates (such as 0001-01-01) are no longer processed, courses and certificates are better recognised as education records, and OCR processing of documents is more reliable. CV processing is now more stable and fewer errors are displayed.

102801 | Negative duration in working days when processing job applications

When job applications were received at the weekend and processed on a working day, the calculated duration in working days could be a negative number. For example, a processing time from Sunday to Monday morning was incorrectly displayed as negative. The duration in working days is now calculated correctly, always showing a logical and positive value.

102853 | Close button and surrounding buttons not visible in WhatsApp conversation window

In the WhatsApp component in the action bar, the close button and surrounding buttons could fail to appear for certain conversations. This affected conversations where the window was closed, displaying the message that the conversation would only open once the recipient responded to a sent template message. The issue did not occur when the conversation was opened from the candidate page. The close button and surrounding buttons are now displayed correctly in this situation as well.

102980 | Email action for candidate without email address showed "null" instead of a clear message

When clicking the email action for a candidate without an email address, the text "null" was displayed instead of a clear message. A suitable message is now shown when a candidate has no email address.

103049 | Unexpected blank lines in lists in generated documents

When generating documents from a job application, text from a rich text field containing bullet points could be displayed incorrectly. In some cases, extra blank lines or breaks were added in unexpected places. The formatting of bullet lists is now better preserved, so generated documents from job applications are displayed more consistently.

103411 | Multi-select picklist values showing technical values in list columns

In various list views, multi-select picklist fields could display technical values instead of the correct labels. This meant the underlying API value was shown instead of the translated or user-friendly field value. Multi-select picklist values in list columns are now displayed correctly with their corresponding labels. This applies to Search Persons, Search Accounts, Match Lists and Application Process, among others.

103755 | CV and cover letter could be swapped for applications received via job boards

When a job application arrived via a job board with multiple attachments (for example a CV and a cover letter), the cover letter could be saved as the CV and vice versa, because the order of attachments is not always consistent. When multiple attachments are present, the file name is now checked first to determine the correct document type. If a file name contains the term "cv", it is saved as the CV and the other file as the cover letter. If that is not the case, the system checks whether a file name contains the term "candidature"; if so, that file is saved as the cover letter and the other as the CV. If neither file name provides clarity, both documents are saved as cover letters, ensuring the CV is at least retained and can later be manually re-uploaded for parsing if needed.

103912 | Granting portal access could fail for contact persons with spaces or special characters in their name

When granting portal access to a contact person with a space or special character in their name (for example a surname prefix such as "van"), this could lead to an error message, preventing the portal user from being created. This was because the generated nickname or alias was in some cases not unique, without this being correctly detected in advance. Spaces and special characters are now correctly removed when determining the nickname and alias, and a better check is performed to verify whether the generated value is already in use. A unique nickname and alias are now automatically assigned, even when names are similar.

104115 | Sort order of completed tasks in the Activity Timeline could differ from the displayed date

In the Activity Timeline, completed tasks were sorted based on the completion date, while the date displayed with the task was the original due date (Activity Date). This could cause the order of tasks to not match the dates you saw, which could be confusing. Tasks are now sorted based on the Activity Date, consistent with the standard Salesforce timeline. This applies to both completed and open tasks, so the order always matches the date you see.

104514 | CV Dropbox in the Utility Bar remained open after saving a new candidate

When using the CV Dropbox in the Utility Bar, the panel remained open after a CV had been processed and the new candidate record had been saved. The new record was opened in the background but was not visible because the panel was blocking the view. The panel now closes automatically once the candidate has been successfully saved.

104651 | Unclear error message when using a WhatsApp template with an image header in a flow

When using the flow action to send a WhatsApp template with an image header, a technical error message appeared without a clear explanation. The user could not determine from this message what went wrong or how to resolve it. Templates with a media header (image, video or document) are currently not supported via the flow action. A clear message is now displayed when such a template is selected, making it immediately clear that a template without a media header must be chosen.

105311 | Confirmation email for privacy choice was not saved in the Activity Timeline

When a candidate responded to a privacy reminder via the portal — by giving consent or requesting data removal — the corresponding confirmation email was not saved in the Activity Timeline of the contact record. The initial privacy reminder was visible in the timeline, but the confirmation email was not saved, leaving the consent audit trail incomplete. Confirmation emails for granting consent and for data removal requests are now also saved in the Activity Timeline.

105511 | Visibility condition based on a picklist was not correctly evaluated on the portal

When using field visibility on the portal, a condition that depended on a picklist field was not correctly evaluated. This caused a field to remain hidden even when the configured condition had been met. Visibility conditions based on picklist fields are now correctly evaluated and applied.

105611 | Documents larger than 4 MB could not be opened or signed in the portal

When a candidate clicked Sign for a mySign document larger than 4 MB, an error occurred and the document did not load in the preview. mySign documents of any size are now correctly loaded in the portal preview and can be signed without errors.

105734 | Creating a job vacancy on the portal failed for non-English portal users

When creating a job vacancy via the portal, an error could occur when the portal user's language was set to Dutch or any language other than English. The record type was looked up based on the translated name rather than the language-independent internal name, causing the lookup to return no result. The record type is now always looked up correctly, regardless of the portal user's language setting.

Overview of this release

🔗 Find all features from this release here