MSR Recruitment Fixed Features 2025-3

INDEX

• 85822 | Managed fields for event start and end times removed
• 88808 | Rejection reason not updated in Rejection Flow component
• 89010 | Application status sometimes not visually updated in Workflow
• 89159-94718-96119 | 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
• 91680 | Valid Until and Document Number in Person document
• 92434 | Workflow refresh button did not always work correctly
• 92945 | Technical limit of Search People/Accounts sometimes reached
• 93677 | Skill Board Component not visible in Experience Cloud Portal

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.

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 | 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.

Finally, the document type CV can never be changed to another type, and other types cannot be changed into CV.

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.

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.

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.