MSR Recruitment Fixed Features 2026-2

INDEX

• 96076 | Documents not visible in SharePoint when using team placeholder in folder path

• 100449 | Postal code not always enriched during CV parsing without full enrichment configuration

• 100729 | Unread WhatsApp messages not highlighted when opening Message Center

• 100742 (MSR-1195) | Images are now displayed directly in document preview

• 100743 (MSR-1208) | Externally stored documents open correctly again in the portal

• 101825 | Skill sharing rules now also respected on the Experience Cloud Portal

• 101961 | Improvement in sending emails to candidates

• 102076 | Improvement in processing CVs with many skills

CONTENT

96076 | Documents not visible in SharePoint when using team placeholder in folder path

When a document type contained a SharePoint Folder Path with a team placeholder, such as #TEAM_CANDIDATE#\Candidate\2026, the generated document was not always stored correctly in SharePoint. In this scenario, the document was successfully generated from the candidate record, but did not appear in the expected SharePoint folder corresponding to the candidate’s team.

From now on, the candidate’s team is correctly resolved when generating the SharePoint path. As a result, documents are stored in the correct SharePoint folder and are immediately visible in the SharePoint environment.

100449 | Postal code not always enriched during CV parsing without full enrichment configuration

When a CV does not contain a postal code, the Here API is used to determine the postal code of the city center. In some scenarios, this enrichment was not performed or not updated. This occurred in the following situations:

If only postal code enrichment was enabled and no other data enrichment configuration was set up, the candidate’s postal code was not filled.

If MAIA enrichment records already existed, the postal code was not recalculated when a CV was re-parsed with only a city name.

When re-parsing a CV after manually clearing the postal code field, the postal code was not enriched again.

From now on, postal code enrichment is consistently applied:

Also when only postal code enrichment is configured

Also when re-parsing a CV

Also when enrichment data already exists

As a result, the candidate’s postal code is correctly filled as soon as a city name is available, regardless of the existing enrichment configuration.

100729 | Unread WhatsApp messages not highlighted when opening Message Center

When using WhatsApp with individual user numbers, new unread messages were not always correctly highlighted when opening the Message Center. Due to a timing issue, the visual notification (highlighting) was sometimes not triggered, causing users to miss new messages.

This issue occurred during the loading of the WhatsApp component, where the configuration status check had not yet completed while message data was already available. In addition, a non-existing audio notification was triggered.

From now on, unread WhatsApp messages are reliably highlighted:

New unread messages are correctly highlighted when opening the Message Center

The solution works for individual numbers, central numbers and team-based number configurations

Unnecessary checks and unsupported audio logic have been removed

This improves the visibility of new WhatsApp messages and aligns the behavior with user expectations.

100742 (MSR-1195) | Images are now displayed directly in document preview

When opening a document in the document preview component, the system always attempted to generate an image first. As a result, no preview was shown when the file was already in an image format.

From now on, files of type jpg, jpeg, png, gif and webp are displayed directly, while other file types are still converted for preview.

100743 (MSR-1208) | Externally stored documents open correctly again in the portal

When opening documents in the portal, an error could occur in some situations when the document was stored externally. The file size of these documents was not correctly determined, causing the wrong mechanism to be used to display the document.

This could lead to issues when opening or signing documents, for example in mySign dossiers.

This has been resolved so that the file size of externally stored documents is processed correctly and documents can be opened and signed reliably again in the portal.

101570 | mySign documents remain stuck after signing in portal

When signing multiple mySign documents within one dossier, documents were not always processed correctly in the candidate portal. In this scenario, the document status remained Submitted for Approval, while the dossier itself was marked as approved.

From now on, mySign documents, including external documents, are processed correctly for newly created candidates after signing in the portal. After refreshing the document component, the correct statuses are shown and dossier processing is consistent.

101825 | Skill sharing rules now also respected on the Experience Cloud Portal

When using sharing rules for Skills (Attribute Definitions), these are now also applied in the Experience Cloud when working with skills.

This means that skills are only visible or editable for users when the applicable sharing rules allow it.

101961 | Improvement in sending emails to candidates

When sending emails to candidates, a temporary lock on related data could occur in some situations when multiple emails were sent simultaneously.

This has been improved so that emails to candidates are now processed more reliably, even when multiple messages are sent in quick succession.

102076 | Improvement in processing CVs with many skills

When reprocessing a CV for an existing candidate, an error could occur in some situations when the candidate already had a large number of skills assigned. This could prevent the candidate from being updated correctly during CV processing.

The processing of skills has been improved so that candidates with a large number of skills can now be updated without errors when re-uploading or processing a CV.

102539 | Portal menu works correctly again when opened from Business Central

When a candidate opened the portal from the Business Central environment, MSR tiles in the portal menu could not always be opened. Clicking a tile redirected the user back to the login screen.

This issue only occurred when the portal was opened via Business Central. When opened from MSR via 'View Candidate Portal', the menu worked correctly.

This has been resolved so that portal menu items now open correctly when the portal is launched from Business Central.

102141 | Prevent multiple invitations for appointments created via flow

When creating an appointment via a flow, required attendees could receive multiple invitations. The same appointment created via the Invite Required Attendees screen correctly sent only one invitation.

This has been improved so that required attendees now receive only one invitation when appointments are created or updated via a flow. This ensures more consistent scheduling and prevents duplicate invitations.