MSR Recruitment Fixed Features 2025-3

INDEX

• 85822 | Managed fields for event start and end times removed
• 88165 | Various corrections in translations
• 88808 | Rejection reason not updated in Rejection Flow component
• 89010 | Application status sometimes not visually updated in Workflow
• 89159-94718-96119-96754 | Functionality of Edit button in document list adjusted
• 89293 | Application Process filter Created by ID/Last Modified by ID caused error
• 89448 | Inactive team still visible in Workflow filter and as email sender
• 89571 | Documents not visible in portal tile Customer Vacancies
• 89869 | Workflow tile kept loading indefinitely
• 89948 | Unselected skill in portal saved as 0-star skill
• 90163 | Formatting buttons available in email template with extended letterhead
• 90172 | Improvements in functionality of privacy link in sent emails
• 90389 | Vacancy status check unnecessarily triggered by anonymisation
• 90798 | No-reply email address selectable as sender
• 91466 | Error when uploading checklist document Agreement
• 91680 | Valid Until and Document Number in Person document
• 92434 | Workflow refresh button did not always work correctly
• 92828 | Processing LinkedIn profile or CV sometimes caused an error
• 92945 | Technical limit of Search People/Accounts sometimes reached
• 93677 | Skill Board Component not visible in Experience Cloud Portal
• 94679 | Candidate update failed due to Last CV field limit

Update version 7.34.2 (October 13, 2025)

• 92351 | Managed field 'Match: Account' and Implementation Status of Report Type
• 94559 | Customer could not always open document tile in portal
• 96122 | Improvements in the Experience Cloud Portal
• 96267 | Address in portal truncated to 30 characters
• 96592 | Questionnaire: display question based on multi-select picklist
• 97022 | Reviewing applications via the customer portal failed due to an issue with CustomerJobsController

Update version 7.34.4 (October 24, 2025)

• 91422 | Automatic formatting of mobile numbers now only applied when using WhatsApp
• 97322 | Workflow filter on Business Label no longer worked
• 97428 | Preview of document uploaded via portal sometimes did not work
• 97509 | XML node Placement Detail re-added

Update version 7.34.5 (November 3, 2025)

• 95696 | Error message ‘Too many DML statements’ in DeleteDocumentsBatch
• 97856 | Portal login from MSF did not work for Combi customers
• 97876 | Workflow tile could not be opened when using field names containing ‘From’
• 97962 | Extended user rights for platform events

Update version 7.34.6 (November 5, 2025)

• 98077 | Navigating to Home mistakenly deleted uploaded CV

Update version 7.41.10 (November 21, 2025)

• 98013 | Error when saving documents due to inactive user
• 98148 | ‘Load All’ button missing in Candidate Resume Previewer
• 98241 | Searching with multiple Skill criteria returned no results
• 98243 | Checklist validation failed when multiple statuses required items

Update version 7.41.12 (November 27, 2025)

• 98330 | WhatsApp questionnaire not marked as completed when using a template
• 98451 | Questionnaire answers failed for restricted picklist fields
• 98683 | Error caused by too many SOQL queries in checklist bulk validation resolved
• 98802 | Error when modifying columns in the Applications tab

Update version 7.41.15 (December, 2025)

• 98907 | Triggered flows on platform event 'Notification'
• 99104 | Opening a job application on the candidate portal caused an error
• 98466 | Lead Score processed incorrectly for email activities and 'No activity' rules
• 98711 | Negative decimal values displayed as positive
• 99408 | Field updates from WhatsApp questionnaires sent via template were not processed
• 99651 | Latest CV field not updated when parsing via API

Update version 7.41.16 (January, 2026)

• 98907 | Triggered flows on platform event 'Notification'

CONTENT

85822 | Managed fields for event start and end times removed
Several managed custom fields related to event start and end times were previously phased out and labeled with the suffix Deprecated. In this release, they have been removed from the managed package, so you can safely delete them if no longer in use.

Removed fields:

• Object: msf__Event__c, field: msf__End_Time__c (datetime)

• Object: msf__Event__c, field: msf__Start_Time__c (datetime)

• Object: Activity, field: msf__UserTimeZoneOffset__c (formula)

If you still use these fields in email or document templates, replace them with the standard Salesforce fields Event.StartDateTime and Event.EndDateTime.

Note: The fields msf__Start_time__c and msf__End_time__c (both formulas) on the Activity object were phased out in an earlier release. We also advise replacing these as described above.

88165 | Various corrections in translations
Here is a brief overview of components and languages where corrections have been made in translations or missing translations have been added:

• Appointment pop-up screen: various labels (German)

• Vacancy, Applications: various labels (German)

• The term Current for work experience in generated documents (German)

• Error message for failed CV parsing (German)

• Search People / Search Accounts: labels Search by distance and Activity timeline (German)

• Custom Settings, CM Sign settings: labels for reminder emails (German, English)

• Account: field VAT Business Posting Group (Dutch)

• Document type, Checklist, and Document list: field Valid until (French)

88808 | Rejection reason not updated in Rejection Flow component
When choosing a rejection reason in the flow component, the corresponding standard rejection text should be displayed automatically. This did not display correctly after interrupting the flow, though the text was still saved to the record. From now on, the update is correctly shown in the flow component.

89010 | Application status sometimes not visually updated in Workflow
In two cases, application status did not update visually in the Workflow screen until after manual refresh:

• When rolling back a status using the step Undo last step.

• When status was updated through a flow.
  In both cases, the status is now updated immediately on screen.

89159-94718-96119-96754 | Functionality of Edit button in document list adjusted
In the document list, you can click the arrow next to each document to see more options. The Edit button sometimes did not work for externally stored documents, and no explanation was provided. The button now always works. If fields such as Document Number and Validity are relevant for the document type, they can now also be edited for externally stored documents (SharePoint or Google Drive).

It is no longer possible to change the document type afterward if the new type has:

• A different value in the Save To External Data Source field. In other words, a locally stored document cannot be converted to an externally stored type, and vice versa.

• A different value in the Generate field. In other words, an uploaded document cannot be converted to a generated type, and vice versa.

• Different requirements for fields such as Document Number or Valid From/To that would result in fewer available fields. For example, a document where Valid From/To is displayed or required cannot be converted to a document type where these fields are not relevant.

The list of available document types now automatically shows only the permitted types, preventing mistakes.

89293 | Application Process filter Created by ID/Last Modified by ID caused error
Using Created by ID or Last Modified by ID as a filter in the Application Process screen no longer triggers an error.

89448 | Inactive team still visible in Workflow filter and as email sender
Inactive teams are no longer used when the Workflow filter Team is applied and are no longer selectable as email senders.

89571 | Documents not visible in portal tile Customer Vacancies
A space in the setup name of a document type no longer causes the Documents field to disappear from a Customer Vacancies tile (controller type SFCustomerJobs).

89869 | Workflow tile kept loading indefinitely
Workflow tiles using conditions on certain objects sometimes failed to load when no custom columns were defined. Standard columns are now displayed in such cases, ensuring the tile opens normally.

89948 | Unselected skill in portal saved as 0-star skill
On the portal, users can assign star ratings to skills. A skill left unselected (0 stars) was still saved as a skill with 0 stars, creating confusion. From now on, unselected skills are not saved.

90163 | Formatting buttons available in email template with extended letterhead
When using an email template with an extended letterhead, all formatting buttons are now available to edit the body text. Previously, only a limited set of formatting functions was available.

90172 | Improvements in functionality of privacy link in sent emails
If a person had been anonymised, they could still use a privacy link from a previously sent email. From now on:

• A friendly message is shown instead, and anonymised candidate records are no longer updated.

• The confirmation page is always displayed, even when the link is clicked multiple times on the same day.

90389 | Vacancy status check unnecessarily triggered by anonymisation
During anonymisation, updating an application always triggered a check to see if the linked vacancy status needed adjustment. For vacancies with many applications, this could lead to a query limit error (50,001 row limit). This check is now only performed when the application status is actually updated.

90798 | No-reply email address selectable as sender
In Salesforce Setup (Email → Organization-Wide Addresses), email addresses can be configured with purposes such as User Selection or Default No-Reply Address. No-reply addresses can no longer be selected as senders in our mail component.

91466 | Error when uploading checklist document Agreement
When uploading a document for a checklist item on the Agreement object, no error message appears anymore.

91680 | Valid Until and Document Number in Person document
The fields Valid Until (ID_Validuntil) and ID Document Number (ID_Docno) are now correctly merged into generated Person documents.

92434 | Workflow refresh button did not always work correctly
When making a change on another tab and refreshing the Workflow component with the internal refresh button, the counters on the tiles were not updated until a full screen refresh. This has been corrected.

92828 | Processing LinkedIn profile or CV sometimes caused an error
If your list of characteristics (msf__Skills__c) is quite extensive and you use Maia Skill Enrichment, an error could occur when processing a LinkedIn profile via the Nixz plug-in or a CV via the Resume Dropbox. As a result, the profile was not processed correctly. A system adjustment now ensures that this error no longer occurs and that profiles are processed correctly again.

92945 | Technical limit of Search People/Accounts sometimes reached
In environments with large numbers of person or account records, certain searches could hit a technical limit, resulting in incomplete search results warnings. Search performance has been optimised to reduce this risk.

Additionally, an issue was fixed where Optional scores were not visible when searching for people from a vacancy.

93677 | Skill Board Component not visible in Experience Cloud Portal
The Skill Board was previously only visible for the logged-in user. Recruiters can now also view and use the Skill Board on other person records, provided they have read and write access.

For this, the Portal Skill Board Matrix component in Experience Cloud must use the parameter {!recordId} as Record ID.

94679 | Candidate update failed due to Last CV field limit
For exceptionally large CVs, an error could occur during parsing when creating or updating the candidate. The error message was: CV Last CV: data value too large. The system attempted to store the entire CV text in this field. If the CV contained more characters than the field allowed (theoretical maximum: 131,072 characters), the error occurred. From now on, the text in the Last CV field is truncated safely, just below the maximum limit.

Update version 7.34.2 (October 13, 2025)

92351 | Managed field 'Match: Account' and Implementation Status of Report Type
This item resolves two issues related to managed fields.
If an account was deleted while it was still linked to a Match, this could cause problems in the Match List component. To prevent this, the configuration of a managed field has been adjusted as follows:

On the object Match (msf__TalentPoolMember__c), the managed field Account (msf__Account__c) includes a setting called What should happen if the lookup record is deleted? To prevent the above issue, this setting has been changed to: Do not allow deletion of the lookup record that is part of the lookup relationship.

In addition, the implementation status of several managed custom report types has been updated. These were previously set to In Development, which meant that reports based on these types were not available to all users. The status has now been changed to Deployed.

94559 | Customer could not always open document tile in portal
When a contact opened a tile in the customer portal displaying documents, an error sometimes occurred. This happened when the contact person also had documents of the same document type. This no longer prevents the tile from opening.

96122 | Improvements in the Experience Cloud Portal
When signing a document with mySign, the three predefined signatures are now displayed in three different fonts. In addition, documents with more than three pages can now be downloaded for review. Finally, after completing the signing process, a clearer message is displayed confirming that there are no remaining documents to sign.

96267 | Address in portal truncated to 30 characters
An address (street name + house number) entered in the portal was previously truncated to a maximum of 30 characters. The same occurred when processing a CV. This behaviour has now been corrected.

96592 | Questionnaire: display question based on multi-select picklist
When configuring a questionnaire, you can now display or hide a question based on the response to a multi-select picklist. Previously, this caused a No answers defined error. The functionality now works correctly.

97022 | Reviewing applications via the customer portal failed due to an issue with CustomerJobsController
During the final testing phase of version 2025-03, an issue was discovered that caused an error when opening the portal tile displaying customer vacancies. Because of this problem, the release date unfortunately had to be postponed. This issue has now been resolved.

Update version 7.34.4 (October 24, 2025)

91422 | Automatic formatting of mobile numbers now only applied when using WhatsApp

Do you use the WhatsApp feature (Custom Settings → WhatsApp Settings → Use WhatsApp)?

Then it is required that mobile phone numbers include a country code (e.g. +31). For certain countries, mobile numbers on the Contact object are automatically adjusted when entered without a country code. This happens based on an environment setting, namely Company Information → field "Default Environment".
An additional check is performed on known prefixes. For example, if your "Default Environment" is set to Dutch (Netherlands), the first 0 is automatically replaced with +31 when the number starts with 06. A similar logic applies to the following "Default Environment" values: Dutch (Belgium), French (Belgium), German (Germany), German (Austria), German (Switzerland), English (United Kingdom), and English (United States) for mobile number prefixes used in those countries.

What changes if you do not use the WhatsApp feature?

From now on, this automatic formatting logic is applied only when the WhatsApp feature is active. This means that if the feature is not enabled, mobile numbers entered without a country code will no longer be adjusted automatically..

97322 | Workflow filter on Business Label no longer worked
In an early version of the 2025-03 release (7.34.3), an error occurred that caused the workflow filter on Business Label to stop working. This issue has now been fixed.

97428 | Preview of document uploaded via portal sometimes did not work
A document uploaded via the portal and stored within Salesforce is now correctly displayed in the preview again.

97509 | XML node Placement Detail re-added
The XML node Placement Detail was missing for customers using only Mysolution (Recruitment). This node has been re-added so that fields from the Placement Detail object can once again be correctly included in placement documents.

Update version 7.34.5 (November 3, 2025)

95696 | Error message ‘Too many DML statements’ in DeleteDocumentsBatch
When running the DeleteDocumentsBatch, the error message ‘Too many DML statements: 151’ could occur. The cause was that the batch size was set to 200 in multiple places (such as in BatchController.runDeleteDocumentsBatch and DeleteDocumentsBatchScheduler), exceeding Salesforce limits. The batch size has now been reduced to 100 to prevent this error from recurring.

97856 | Portal login from MSF did not work for Combi customers
For customers using the hybrid portal (MSR + MSF), the portal could no longer open automatically from MSF. After updating to MSR release 2025-03 and MSF release 25.01.0900, clicking Open Resource Portal redirected the user to the login page instead of logging in automatically as a resource.

When the same action was performed from MSR, the automatic login still worked correctly.

The cause was that MSF’s OpenPortalController did create an unrestricted token, but not the associated Token__c record. This behaviour has now been aligned with openCustomerPortal (LWC) in MSR, so that a valid Token__c record is also created when called from MSF. From now on, the portal opens correctly, and the user is automatically logged in as a resource.

97876 | Workflow tile could not be opened when using field names containing ‘From’
When opening certain Workflow tiles, an empty tile appeared with the error message [object Object]. The cause was in the query configuration of the tile: if a field name contained the word ‘From’ (e.g. msf__Valid_From__c), the query was interpreted incorrectly.

The parser used the first occurrence of the word from instead of the actual SQL keyword FROM, causing an error when loading the tile.

The parsing logic has now been adjusted so that field names containing ‘From’ or similar terms no longer cause errors. Workflow tiles now open correctly, even with such field names.

97962 | Extended user rights for platform events
If users did not have permissions for certain platform events—such as DocumentGenerated, Incoming Message, Notification, Outlook Event, Resume Parsed and Track Batch Progress—errors could occur. For example, the DocumentGenerated event could cause a document to be submitted for approval before it was saved in the external data source.

This issue has been resolved. The required platform events have now been added to the object permissions via AccessToAllMysolutionRecruitmentClasses, allowing all users with these permissions to perform processes correctly.

Update version 7.34.6 (November 5, 2025)

98077 | Navigating to Home mistakenly deleted uploaded CV
This issue only occurs for customers using the Triple My app. This version will be installed in your environment upon request.

When creating a new candidate record in the Triple My app via the Resume Dropbox, clicking Home in the navigation bar incorrectly reopened the CV processing screen instead of the home page. If Cancel was then clicked, the previously uploaded and saved CV was unintentionally deleted.

This behaviour has been corrected. From now on, clicking the Home button correctly opens the start page, and any previously processed CV remains saved.

Update version 7.41.10 (November 21, 2025)

98013 | Error when saving documents due to inactive user
When signed documents were returned from mySign to Salesforce, an error occurred. The document could not be linked to the correct Salesforce records if one of the involved users was no longer active. As a result, saving the document failed and the record was not updated correctly.

This has now been fixed. When a document is saved or linked, an active user is automatically used to perform this action. Documents are now processed correctly again, even if previously involved users are inactive.

98148 | ‘Load All’ button missing in Candidate Resume Previewer
In the Candidate Resume Previewer component, used both on the Contact object and within the Job Bench, the ‘Load All’ button for loading additional pages of the document was missing. This button is now visible again, allowing all available pages of a candidate’s CV to be displayed correctly.

98241 | Searching with multiple Skill criteria returned no results
When searching for candidates via Job > Search Persons, candidates were sometimes not found when multiple Skill criteria were combined. This occurred particularly when the second Skill criterion was marked as Required. Even if candidates matched all Skill criteria, the result list remained empty. Only after changing the search parameter from ‘At least 1 selected value’ to ‘All selected values’ did the correct candidates appear. This has now been fixed. From now on, candidates are returned correctly when combining multiple Skill criteria, regardless of whether one or more criteria are marked as Required.
Note: the earlier changes of fixed feature 92945 are reverted by this fix. A future feature will reintroduce this improvement in a refined form.

98243 | Checklist validation failed when multiple statuses required items
When several checklist items were required across different statuses, the system validated only one of these statuses instead of all relevant ones. As a result, a user could change the status of, for example, a candidate or application without completing all mandatory checklist items. This has been corrected: when a status is changed, the system now correctly checks whether all required checklist items are completed for all relevant statuses.

Update version 7.41.12 (November 27, 2025)

98330 | WhatsApp questionnaire not marked as completed when using a template
When a questionnaire was sent via a WhatsApp template, the invitation status did not change to Answered after all questions were completed. The questionnaire remained in Partially answered. The cause was that, when using a template, no completion screen was shown after the final question. This screen normally triggers the invitation to be marked as Answered. As a result:

• the answers were not stored as completed,

• resending the same template to the same person produced an error because the flow attempted to start on an invalid completion page.
  This has now been fixed. For questionnaires sent via a WhatsApp template, the completion event is processed correctly and invitations are automatically set to Answered. Questionnaires can now be completed again and answers are stored correctly.

98451 | Questionnaire answers failed for restricted picklist fields
When completing a questionnaire, a Single answer value could not be saved if it was linked to a restricted picklist field. During processing, a semicolon was unintentionally added to the value, causing it to no longer match a valid picklist option. As a result, the field was not updated and an error appeared in the linking log. This is now fixed. The value is processed correctly again without additional characters, allowing restricted picklist fields to be updated successfully based on questionnaire responses.

98683 | Error caused by too many SOQL queries in checklist bulk validation resolved
After the earlier fix for the 101-SOQL issue in checklist validation (fixed feature 98056), the same error could still occur when running the bulk validator. When validating multiple documents at once, too many queries were executed, causing the process to stall and the checklist validation not to complete. This has now been resolved. Bulk validation now uses an optimised retrieval method that keeps the number of queries within limits. Checklist documents are validated reliably again, even when large batches are processed.

98802 | Error when modifying columns in the Applications tab
When editing or adding columns in the Applications tab within a vacancy, an error occurred as soon as the settings were saved. This issue occurred in certain browsers, preventing the column view from being updated. This is now fixed. Column adjustments work correctly again and changes are saved without errors in all supported browsers.

Update version 7.41.15 (December, 2025)

98907 | Triggered flows on platform event 'Notification'
In a flow where the platform event Notification__c was specifically used for documents stored on an external data source, the field Record_Id__c was not always populated correctly with the document ID. This issue has been resolved.

99104 | Opening a job application on the candidate portal caused an error
With the portal controller Job Application Overview, active job applications can be displayed on the candidate and customer portal. If document fields were included in this controller, it could, in some cases, produce an error when the candidate or contact attempted to view the details. This was caused by a limit being reached while retrieving the related documents. This has now been prevented.

98466 | Lead Score processed incorrectly for email activities and ‘No activity’ rules
Two issues occurred while processing Lead Scores:

• Lead Score for email opens and clicks
  When Lead Score rules were configured for Email opened or Email clicked, Person Lead Score records were not always created correctly. In some cases, repeated opens or clicks incorrectly created duplicate records, or no score was recorded at all. This has been fixed. Lead Scores are now created and updated correctly based on the number of opens and clicks per email, without creating duplicate records.

• ‘No activity’ rules ignored record type filters
  For Lead Score rules of the type No activity, configured record type filters were not taken into account. As a result, Lead Score rules could be applied to persons for whom they were not intended. This has been fixed. When applying No activity rules, all conditions of the Lead Score rule are now checked correctly, including record type and status. Only valid Lead Scores are created.

98711 | Negative decimal values displayed as positive
When using a numeric field in a document template with a negative decimal value between -1 and 0 (for example -0.50), the value was displayed as a positive number. This has been corrected. The value is now shown with a minus sign, correctly indicating a negative number.

99408 | Field updates from WhatsApp questionnaires sent via template were not processed
For WhatsApp questionnaires sent via a template, configurations to update objects and fields based on questionnaire answers were not executed, even though they were set up correctly. This has now been fixed. When a WhatsApp questionnaire sent via a template is completed, linked object and field updates are processed correctly again based on the provided answers.

99651 | Latest CV field not updated when parsing via API
When a CV was processed via the API, the Latest CV field was not updated correctly. Although the new CV was uploaded and processed successfully, the field still contained data from a previous CV. As a result, the most recent CV was not always used for further processing, such as text search functionality. This has now been fixed. When parsing a CV via the API, the Latest CV field is now updated correctly with the newly parsed CV content, ensuring the most up-to-date CV is always used.

Update version 7.41.16 (January, 2026)

99787 | Appointment participants are not saved via the create-edit event component
When an appointment was created via a screen flow using a create-edit event component with only a required participant, this participant was not always added to the appointment after saving. We have now made an adjustment to ensure that the participant is added in all situations.