MSR Recruitment Fixed Features 2026-1

Please note: this list is subject to change until the release date of the first test version, scheduled for 30 January 2026.

INDEX

• 86676 | Improved error handling and clearer error messages
• 89345 | Error messages and missing tiles for portal users with Admin rights
• 89782 | ‘Clear search fields’ button did not work on candidate search screen
• 90614 | Candidate portal could not be opened when role code was empty
• 90769 | Various UI/UX improvements
• 91272 | Consistent date format in filenames of generated documents
• 92202 | Incorrect password change option shown for SSO or login token users
• 92212 | Skill order not applied correctly
• 92281 | Improved display and formatting of date fields in portal field sets
• 92488 | Fewer errors during nightly Outlook Sync subscriptions
• 92536 | Improvements in GDPR Data Clean-up processes
• 92996 | Account sorting in Match list corrected
• 93666 | Error when downloading documents from the portal resolved
• 95556 | Documents without file extension could not be stored in external data sources
• 97758 | Document generation failed with empty or non-existing fields in document name
• 97954 | Error when processing multiple appointments for the same application
• 98095 | Lookup field showed ID instead of name in search results
• 98372 | Process Builders removed from the package
• 99212 | Contact Person record types could not be excluded in Maia Match
• 99421 | Adjustment to CV Document Type
• 100960 | WhatsApp messages are not loaded in the Utility Bar

CONTENT

86676 | Improved error handling and clearer error messages
In several areas of the application, unclear or technical error messages were shown, or error logging was missing altogether. This made it difficult for users and administrators to understand what went wrong or which configuration needed adjustment. This has been improved. Error messages have been clarified, errors are handled more consistently, and logging has been added. Users now receive understandable messages in case of incorrect settings or exceptional situations, and processes that do not require action are no longer presented as errors. This results in a more stable application and makes configuration issues easier to identify and resolve.

89345 | Error messages and missing tiles for portal users with Admin rights
When a Contact record in MSR also had the Portal Admin role, two issues occurred in the portal: certain tiles were not visible and error messages appeared when opening specific tiles. This was caused by portal roles not being retrieved correctly during Admin login. In addition, errors occurred when logging in with an Admin account without a linked Contact or Candidate record. This has been fixed. The portal now first checks for a regular Contact or Candidate record and only then for an Admin user. For Admin users without linked data, a special role (“nodata”) is now provided so the portal can handle this correctly.

89782 | ‘Clear search fields’ button did not work on candidate search screen
When using the Portal Controller with record type Search Candidate, the ‘Clear search fields’ button did not work. Previously entered search criteria remained visible and the search could not easily be reset. This has been fixed. Clicking ‘Clear search fields’ now correctly clears all entered search data.

90614 | Candidate portal could not be opened when role code was empty
If Portal Role 10 was enabled for a candidate while the corresponding Portal Role 10 Code in Domain__mdt was empty, the candidate could not log in to the portal and a NullPointerException occurred. The logic has been updated so the rule is skipped when the role code is empty. Candidates can now log in successfully even if the role code is not filled.

90769 | Various UI/UX improvements
Several improvements have been made to the user interface, including better visibility of the close button in Flows, correct handling of long account names, restored scrollbars where required, consistent display of percentage values including the % symbol, and resolving errors when adding or removing columns in the Job Bench. These changes improve usability and consistency across the application.

91272 | Consistent date format in filenames of generated documents
Date and time stamps in document filenames were not consistent and varied by document type or configuration. This has been resolved. All generated documents now use a single, consistent date format in the filename.

92202 | Incorrect password change option shown for SSO or login token users
When logging in via SSO or a login token, users could still see the option to change their password. Although this did not pose a security risk, the option should not have been shown. This option is now hidden when users log in via SSO or login token.

92212 | Skill order not applied correctly
Skill sorting could be incorrect or inconsistent. Sorting is now based on translated skill names (where available) according to the user’s language. In addition, evaluation-type skills in Search Persons are now displayed using the correct translations.

92281 | Improved display and formatting of date fields in field sets on the portal
Date fields in portal field sets could be displayed incorrectly, cause errors when saving, or ignore the user’s locale. These issues are resolved. Date fields are now displayed correctly, can be saved without errors, and respect the portal user’s language and locale settings.

92488 | Fewer errors during nightly Outlook Sync subscriptions
Unnecessary errors occurred during nightly Outlook Sync tasks, for example when processing subscriptions of inactive users. The sync now only processes subscriptions for active users and verifies valid user links, resulting in a more stable synchronization.

92536 | Improvement in GDPR Data Clean-up processes
An error occurred when deleting more than 10,000 action records during GDPR processing. A separate batch now removes old records first, preventing errors and improving stability.

92996 | Account sorting in Match list corrected
Sorting by Account in a Match list was based on internal IDs instead of account names. Sorting has been corrected and now works properly in both ascending and descending order.

93666 | Error when downloading documents from the portal resolved
Downloading documents from the portal failed when document fields were only configured as Detail Fields. This has been fixed. Documents can now be downloaded correctly without requiring the field to be added as a List Field.

95556 | Documents without file extension could not be stored in external data sources
Documents without a file extension in the filename could not be stored in external systems such as SharePoint or Google Drive. The system now uses the standard Salesforce FileExtension field, allowing documents to be stored correctly even without an extension in the filename.

97758 | Document generation failed with empty or non-existing fields in document name
If a document name contained empty or non-existing fields, document generation failed. These fields are now ignored, allowing documents to be generated successfully.

Updating multiple appointments for the same application caused an error due to duplicate processing steps. This has been fixed by merging duplicates before processing.

98095 | Lookup field showed ID instead of name in search results
In New Search Accounts with tree view enabled, lookup fields showed record IDs instead of names. This has been fixed and lookup fields now display record names correctly.

98372 | Process Builders removed from the package
Due to Salesforce ending support for Process Builder as of 01-01-2026, delivered Process Builders have been phased out of the MSR package. Existing active Process Builders remain unchanged for customers who still use them.

99212 | Contact Person record types could not be excluded in Maia Match
Not all relevant person record types were available for exclusion in Maia Match. Configuration has been updated so all candidate-related record types, including Contact Person, can now be excluded. Non-candidate contacts are no longer indexed unintentionally.

99421 | Adjustment to CV Document Type
It is no longer possible to store a CV document type on an external data source such as SharePoint or Google Drive. CVs are generally accessed very frequently, causing organizations to quickly run into Salesforce API limits. If you now select this option, you will receive a notification.

100960 | WhatsApp messages are not loaded in the Utility Bar
In some situations, the WhatsApp message center in the Utility Bar did not open correctly when navigating from the Home page to a record page. Messages were only loaded after refreshing the page multiple times. This has now been resolved.