MSR Recruitment Fixed Features 2026-03

INDEX

• 95375 | Documents remain visible on portal with inactive document types

• 98595 | Error when searching for candidates without applications resolved

• 98837 | Rich text fields now correctly displayed in email component

• 100074 | Applying for a job no longer possible in read-only portal mode

• 101183 | mySign signature is now placed on all matching tags in a document

• 101598 | Inactive users no longer visible as email recipient

• 101921 | Improved styling and consistency of 'Upload a CV' component

• 102052 | User-friendly error message when sending email without recipients

• 103161 | Error retrieving signed CM Sign documents via batch process resolved

• 103466 | Email not correctly sent when using CC in Mail component

• 103659 | Clickable images in emails referred to wrong link

• 104782 | Sorting by owner in matchlist gave an error

• 105387 | Creating a candidate via the Enter key bypassed required field validation in CV preview screen

CONTENTS

Version 8.11

95375 | Documents remain visible on portal with inactive document types

After an earlier change to the portal configuration, existing documents could become invisible on the portal when the associated document type was set to inactive. This meant candidates could no longer view previously uploaded or generated documents. This has been adjusted so that existing documents linked to an inactive document type remain visible on the portal and can be opened and downloaded as normal. Additionally, the behavior for inactive document types has been updated. It is no longer possible to create new documents for an inactive document type, but existing documents remain fully available for viewing and management.

98595 | Error when searching for candidates without applications resolved

When searching for candidates based on vacancies without applications, an error could occur. In this scenario the search query was not built correctly, resulting in a system error. This issue occurred when filtering on 'has no applications' for a vacancy without linked applications. This has been resolved so that the search query executes correctly and the expected results are shown. Candidates without applications for the selected vacancy are now displayed correctly again.

98837 | Rich text fields now correctly displayed in email component

When using the email component with automatic rendering, 'Rich text area' fields (such as job descriptions) could be displayed incorrectly. Instead of formatted text, HTML tags were visible in the email. This issue occurred with automatic rendering of emails, while manual rendering did produce the correct result. This has been resolved so that these fields are now correctly displayed as formatted text, both with automatic and manual rendering. This makes the content of emails consistent and easy to read again.

100074 | Applying for a job no longer possible in read-only portal mode

When the candidate portal was opened via the 'Open candidate portal' button from Salesforce, it was opened in read-only mode. In this situation it was however still possible to apply for a job via the vacancy overview, whereby an application was created for the relevant candidate. This behavior has been adjusted. In read-only mode it is no longer possible to make changes or create new data, including submitting applications. This brings the functionality back in line with the expected read-only behavior of the portal.

101183 | mySign signature is now placed on all matching tags in a document

For documents that use multiple mySign tags for a single signer, the signature was in some situations only placed on the first instance of such a tag. As a result, the remaining signature tags of that signer in the same document were not filled in. This has been resolved. When a signer signs a document, the signature is now placed on all associated tags in the document.

101598 | Inactive users no longer visible as email recipient

When using the custom email component, inactive users could be selected as a recipient when composing an email. This deviated from standard Salesforce behavior, in which inactive users are not available as a recipient. Inactive users are no longer shown in the list of available email recipients, bringing the behavior back in line with standard Salesforce functionality.

101921 | Improved styling and consistency of 'Upload a CV' component

The 'Upload a CV' component (Resume Dropbox) deviated from standard Salesforce styling on several points. The title formatting was inconsistent, no consistent title notation was used, and the border styling did not match other standard components. Additionally, the appearance could give the impression that files could be dropped anywhere on the tile, which was not the case. The component has been updated to align with standard Salesforce Lightning styling. Among other things, the title has been updated to 'Drop a Resume', the visual layout has been simplified, and the component can now also be correctly added to the utility bar.

102052 | User-friendly error message when sending email without recipients

When sending an email, a technical error message was shown when no recipients had been selected. From now on a clearer explanation is provided of what needs to be done to send the email successfully.

102485 | File name of externally stored documents cannot be changed

For documents stored on an external data source (SharePoint or Google Drive), it was not possible to change the file name after generation. As a result, the original file name was always used when sending documents.

It is now possible to change the file name, and this name is also used when sending the document as an attachment.

103161 | Error retrieving signed CM Sign documents via batch process resolved

When retrieving signed CM Sign documents, the batch process could in some situations get stuck when documents were stored externally. As a result documents were not retrieved and processing stalled. From now on the retrieval of signed documents is executed correctly again, including when using external storage.

103466 | Email not correctly sent when using CC in Mail component

When sending an email via the Mail component, it could happen that the recipient in the 'To' field received no email, while the recipient in CC received the email twice. From now on emails are sent correctly to all specified recipients, with each recipient receiving exactly one email.

103659 | Clickable images in emails referred to wrong link

When sending emails, it could happen that clickable images referred to the wrong URL. This occurred when links were automatically enriched, causing the image itself to be opened instead of the correct link. From now on links behind images continue to work correctly and refer to the correct destination.

104782 | Sorting by owner in matchlist gave an error

When sorting by the "Owner" column in a matchlist, an error message was shown and the sort function did not work. This has been resolved. Sorting by the owner of a contact in a matchlist now works correctly.

105387 | Creating a candidate via the Enter key bypassed required field validation in CV preview screen

In the CV preview screen of myParse, a candidate record could be created immediately by pressing Enter while a field was selected. Required field validations from the configured field set were not checked, allowing incomplete or invalid records to be created. A candidate can now only be created via the Enter key after all required fields have been validated.

Overview of this release

🔗 Find all features from this release here