Welcome to the Release Notes for the latest version of Mercury. This document is designed to give you an overview of all of the changes made in the upcoming release. We have also produced another flavour of the release notes - a fully itemised list of all changes, plus important additional information for System Admins.
Version 33 will be released on the following schedule:
Date | Start time | Release Groups |
Tuesday 8th April 2025 | 09:00 BST | Sandbox Customers' environments |
Saturday 19th April 2025 | 05:00 BST | Non-Sandbox Customers' live environments |
Saturday 26th April 2025 | 05:00 BST | Sandbox Customers' live environments |
Information about version 33
Microsoft 2025 Release Wave 1
Each year, Microsoft release two product updates called Waves. Recently the first wave of 2025 began rolling out.
As Microsoft Partners, we always look at how the Wave release could affect Mercury, to ensure that your experience is consistent and stable, and we also look at where we can bring the latest features and functionality into Mercury.
Our development teams have been thoroughly testing Wave 1 2025 and we can confirm that there will not be significant impact on Mercury users, and you should see no real change in the version 33 release of Mercury.
We are in the process of assessing if there are any advancements that we can factor into further releases, and we will keep you updated as and when there is more news about that.
Users may notice changes to the interface which aligns with the latest Microsoft design system. This will provide us with more options to work with design in future releases.
Clients with a Sandbox environment may wish to test the new features against any customised functionality.
If you have any questions about the Wave release or would like more information, please take a look at the Microsoft Release page or raise a request on our Support Portal.
New Look
Just over a year ago, Microsoft made the "New Look" available to Power Platform users, surfacing the latest Microsoft Fluent Design-based elements for a "modern, refreshed look".
The release of V33 sees Mercury fully adopting the New Look functionality. It will roll out as part of the release and the New Look toggle will be removed.
Please note, we have extensively tested the New Look feature since it was made available and it is purely aesthetic in nature with no changes to functionality, if however you do notice something that you think may be associated with the New Look functionality please raise a ticket via the support portal and we will look into it for you.
Legacy Search decommissioned
Version 33 of Mercury sees Legacy Search decommissioned and the only Search experience is now Mercury Search.
We know that a change like this can take some getting used to and so we have a range of resources to support you on a dedicated Knowledge Base section and some great Webinar recordings that you can access anytime.
There have also been some developments as part of the v33 release to further improve your experience of Search which you can see below.
v33 Highlights
A big focus of this version of Mercury has been around improving the consistency of the user experience to make Mercury easier to use. Throughout these release notes you will see that this is something that we have concentrated on.
In addition, here are some of the highlights to look out for:
Open Mercury Search in context
As part of New Mercury Search becoming the only Search experience, you are now able to launch Search in the context of a Candidate or a Client Contact. This will make it quicker and easier for you to find the right candidate and fill vacancies.
See more information below.
Shortlist enhancements
We’ve made some UI/UX enhancements to this important area of Mercury – particularly when you are using the Update method. In addition, a particular highlight is that when a Shortlist is Submitted via the Update button and a CV is selected, then the selected CV will appear and be prepopulated in the Email Editor if you chose to Send CV by Email.
See more information below.
Enhanced CV handling
There have been several improvements made for customers who are using TextKernel or DaXtra on Demand for parsing CV data to enhance this experience, making it simpler and more streamlined.
See more information below.
v33 UI/UX Enhancements
The following UI and UX enhancements have been completed as part of the v33 release.
For full information please refer to the itemised release notes.
Shortlist
We’ve made it easier for you to manage Shortlists within Mercury. Please note these are only in relation to the Update Method.
When on the Shortlist record the Video Call type has now been removed and the call type is no longer mandatory.
When rescheduling an interview the existing Shortlist Update will be amended to show that the interview being rescheduled.
When a Shortlist is submitted, and a CV is chosen the selected CV will appear and be prepopulated in the Email Editor (if you choose to Send CV by Email).
Relates to 73905, 55241 and 73316
Search
To make it quicker to get the search results you are looking for we have made the following changes
When you click on Search from a contact record you will see the option to either Search Candidate or Search Client Contact.
Selecting Search Candidate will open the Candidate view of Mercury Search and will show you suggested vacancies for that individual.
If you select Search Client Contact, the Client Contact view of Mercury Search will Open.
If you select Search Candidate from a Vacancy this will work in the same way that the previous “Match to Vacancy” functionality worked.
You can now also open Search from a Hot List. When you select this method, Mercury Search will open with the Hot List filter applied.
Relates to 80932 and 77457
We have introduced an information message to make it clearer about the permissions that are needed in order to have emails send automatically. If you “allow other users to send email on your behalf” emails can automatically be sent, otherwise the emails will be created as a draft.
The “From” field on an email form in Mercury is now locked so that you are not able to edit who the email is being sent from. This will improve your data quality and transparency.
Relates to 82078, 85756
Vacancy Entity
When you create a new vacancy a default document location will now automatically be created in SharePoint which will make it easier for you as you no longer need to manually create a Document area.
The Furthest Status colours on the vacancy menu are now aligned with the Status Reason on a Vacancy to give you a more consistent look and feel across Mercury.
Relates to 72044 and 81704
Hot Lists
We have update Hot List views with the following columns: Name, As A, Owner, Created On and Modified On. This will give you more detail and important information at a glance when looking at Hot Lists.
Relates to 24508
Country Record
We’ve updated the Show State Lookup field on the Country Record so that it is now a toggle. This gives you a more consistent user experience as it matches the user interface across Mercury.
Relates to 58960
Info Record
When looking at a Hiring Manager on an Info record, it now returns contacts within it's client hierarchy. Clearing a client will clear the hiring manager. Changing a client will auto populate the hiring manager to the client's primary contact. If client is empty and a hiring manager is selected, the client will be auto populated with the hiring manager's client.
Relates to 63824
Placement Form
On the new Placement form we have switched the positions of the Timesheets and Expenses tabs to improve the user experience as it brings the positions in line with the Legacy UCI form.
Relates to 79153
Contact Record
The fields for ‘Original Source’ & ‘Latest Source’ are now updated following a parse of a CV. This will give you a better understanding of how a CV has been parsed (either via the API or manually) so that if there are any queries it will be easier to trace the source.
Relates to 75148
Integration Updates
Here’s a list of updates to our integrations – please note that you will only be able to see these updates if you are using these integrations within Mercury.
LogicMelon
LogicMelon is now fully embedded within Mercury to make it easier to manage your adverts without needing to have multiple windows open.
Relates to 76360
Idibu
We have changed the POST method when using Idibu to remove the character limit that the previous method had. This means that you can now post longer job descriptions without worrying about giving over the character limit.
Relates to 78832
TextKernel
Candidate Source is now populated when a Contact is created via TextKernel parse.
Relates to 66428
TextKernel and DaXtra
We have made a number of enhancements to the TextKernel and DaXtra on Demand integrations to improve the CV parsing experience and improve data quality.
Introduced a message to give you information when uploading a document for parsing via Upload CV or Update by Parse to advise you to check that the CV being uploaded is the correct one for the record.
Introduced a message when you are uploading a new CV using Upload CV or Update by Parse to advise that a new Contact will be created and that you should check to see if the Contact already exists.
The Existing Contact field is now read-only when reviewing a CV
We have renamed the buttons that are used for saving parsed CV data to make it clearer as to what action is being performed. The 'Save to Candidate' button is replaced as follows:
If creating a new candidate, show the button 'Create Candidate' on Processed status only
If updating an existing candidate, show the button 'Update Candidate' on Processed status only
Save & Close has been removed
Relates to 69616, 66318, 75142 and 75158
Software Fixes
Here is a list of fixes we’ve put in place in Mercury v33:
|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Important additional information for Mercury System Admins
If you are a Mercury System Admin of an organisation using bespoke customisations, please see the additional information here.