Mercury v33 Itemised Release Notes - April 2025

Shortlists

73905: 

Removed Video Call Type & ID IDEA-01415 

What: 

Video Call ID has been removed from the interview stage when progressing a Shortlist and Video Call Type is now non mandatory  

Where: 

Shortlist - Update Interview. Please note, this has only been applied to the ‘Update’ method.  

How: 

Call ID no longer shows, and call type is not mandatory 

Why: 

This will reduce the amount of information that is needed when progressing a candidate as this is often created by the client directly.   

55241: 

Shortlist - Reschedule Interview Shortlist Update 

What: 

When ‘Rescheduling’ an Interview via the ‘Update’ method, the existing ‘Shortlist Update will be amended to show the Interview being rescheduled.   

Where: 

‘Update’ from Mercury Shortlist form ribbon 

How: 

Original Shortlist Update will be appended to show ‘RESCHEULED’ if rescheduling an Interview 

73316: 

Email on Submit - Selected CV is selected in Email Editor 

What: 

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.   

Where: 

Shortlist ribbon - Update - Submit 

How: 

When Submitting a Candidate, select a CV and ensure the Send CV by Email toggle is toggled on 

Why: 

This means that you don't have to search for a CV and select it again in the Email Editor which will make it quicker for you to send. 

80932: 

Contact Search Buttons 

What: 

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. 

Where: 

Contact entity  

How: 

By clicking one or more records from the sitemap or by opening the record itself. 

Why: 

This enables you to open a search in the context of a candidate or client contact. 

77457: 

Opening New Mercury Search from a Hot List 

What: 

You are now able to open Mercury Search from a Hot List in the CRM  

Where: 

Triggered by a button or action on the Hot List form  

How: 

From Hot List you will see a Search button  

Why: 

This means that you can open New Mercury Search directly from a Hot List, bringing it in line with Legacy Search functionality. 

82078: 

Email editor UI to check user config 

What: 

We have added an error message which is shown to the User if ‘Personal Setting’ not set to send emails on behalf of another  

Where: 

Message is displayed within the Email Editor when opening. Setting is under ‘cog’ and ‘Personalisation Settings’ 

How: 

 When opening the email editor the message will be shown.

Why: 

This gives you flexibility over how you want to use the email editor – 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. 

82078: 

Email From should be Read-Only

What: 

From field should not be editable on any email form in Mercury

Where: 

When creating an email outside the mercury email editor

How: 

 When an email record is opened the From field is read only

Why: 

This will improve your data quality and transparency.  

72044: 

Furthest Status colours not showing on Vacancy menu 

What: 

The colours on 'Furthest Status' are now aligned with 'Status Reason' on a Vacancy.

Where: 

Vacancy entity views 

How: 

The UI styling now matches 'Furthest Status' colours with 'Status Reason' 

Why: 

This will give a more consistent user experience with a consistent look and feel across Mercury 

81704: 

Vacancy SharePoint Document Location Create 

What: 

On creating a new vacancy a default document location is now created   

Where: 

When create a New Vacancy or Updating an existing Vacancy with no Document Location  

How: 

Create a new vacancy, navigate to Related --> Documents --> Open Location.   

Why: 

This will automatically create the SharePoint Document Location for a Vacancy which will make it easier to use as you no longer need to navigate to the 'Documents' tab to trigger the creation 

24508: 

Hot List view updates 

What: 

All the Hot List views have been updated with the following columns: Name, As A, Owner, Created On, and Modified On  

Where: 

From Hot Lists on the Mercury Site Map 

How: 

Go to any Hot List view to see the changes 

Why: 

This will enable recruiters to see more details and important information when they are looking at Hot Lists.  

58960: 

'Show state lookup?' Field is now a toggle on Country record 

What: 

We have made the ‘Show State Lookup Field’ a toggle on the Country record 

Where: 

Mercury Admin → Support → Countries 

How: 

While creating and updating a Country record 

Why: 

This will give a more consistent user experience as it matches the user interface across Mercury. 

63824: 

Hiring Manager to Filter on Info 

What: 

Hiring manager on an info record 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. 

Where: 

Info record or Quick create and info record 

How: 

Create or update an info record 

Why: 

This now means that when you are selecting a Hiring Manager you will only see the Client Contacts at the selected Client which will improve your experience and mean you won’t be able to select individuals that are not associated with that Client.  

79153: 

Switch Timesheets & Expenses 

What: 

The positions of the Timesheets and Expenses tabs have been switched.  

Where: 

Mercury Placement Form.  

How: 

Update the tab order in ‘Mercury Placement Form’ 

Why: 

This brings the new Mercury Placement Form in line with the legacy UCI form 

75148: 

Update Latest and Original Source on parse - Contact Record 

What: 

The fields for ‘Original Source’ & ‘Latest Source’ are now  updated following a parse of a CV  

Where: 

‘Original Source’ & ‘Latest Source’ fields on a Contact  

How: 

These fields will now be populated regardless of how the CV is parsed (on demand or email)  

Why: 

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. 

76360:  

LogicMelon iFrame 

What:  

LogicMelon is now fully embedded within Mercury.  

Where: 

Vacancy Form within Mercury.  

How: 

Rather than having a new window open when trying to post a job, a new tab will show on the Vacancy, called ‘Manage Adverts’ 

Why: 

Rather than having new windows open and directing Users away from Mercury, we are keeping everyone in Mercury. 

78832: 

Overcome character limit on Idibu integration by moving to HTTP POST  

What: 

We have changed the POST method for to HTTP POST which will mean there are no longer character limits imposed.   

Where: 

Mercury Vacancy and UCI forms  

How: 

Go to Vacancy - Manage Adverts  

Why: 

This will enable users to post longer job descriptions rather than be constrained by character limits imposed in the alternative POST method. 

66428: 

Candidate Contact Status not populating via TextKernel - M22627 

What: 

’Candidate Source to be populated following a Contact being created via TextKernel Parse. 

Where: 

‘Candidate Status’ field on a Contact 

How: 

Will be set to ‘Never Placed’ when a new Contact is created following either manual creation or a Parse via Daxtra or TextKernel.  

Why: 

To ensure data is keep up to date and for consistency when creating a new Contact manually 

69616: 

CV Document 'Upload CV' Message - Individual Contact record 

What: 

Information message when uploading a document for parsing within Mercury 

Where: 

Upload CV or Update by Parse ribbon buttons on a Contact. Please note, this is only for Customers using TextKernel Parsing or Daxtra on Demand Parsing  

How: 

When you upload a CV via Upload CV or Update by Parse you will see a message advising to check that it is the correct CV that you are uploading.  

Why: 

This gives a better user experience, reminding you to check that the CV that is being uploaded is the correct one for the record 

66318: 

Upload CV Info Message - List of contacts 

What: 

We have added an information message to confirm that a new Contact will be created following this parse and Users should check to see if the Contact already exists first  

Where: 

‘Upload CV’ or ‘Update by Parse’ ribbon buttons on a Contact. Please note, this is only applicable for Customers who have TextKernel and Daxtra on Demand set up. 

How: 

 When you select Upload CV or Update by Parse you will see the message.

Why: 

Avoids duplicates being created within Mercury. This gives a better user experience, reminding you to check to see if a candidate already exists which will help to reduce duplication of records.  

75142: 

Change buttons for saving parsed CV data 

What: 

We have renamed the ribbon buttons when ‘Reviewing’ a Parsed CV  

Where: 

‘Parsed CVs’ within ‘Admin’ Area of Mercury App. Please note, this is only applicable for Customers who have TextKernel and Daxtra on Demand set up, along with the option to review parsed CV’s.  

How: 

Removed ‘Save & Close’ option from ribbon and changed name of the other buttons to reflect the action that will take place.  

Why: 

Simpler and more intuitive ribbon names, which will provide a simplified user experience by reducing the same options and making it clearer what each of the options do. 

75158: 

Read-only Existing Contact field in edit screen for CV parsing on demand 

What: 

We have made it so that Existing Contact’ field is now read only when reviewing a CV  

Where: 

‘Existing Contact’ field on Parsed CV. Please note, this is only applicable for Customers who have TextKernel and Daxtra on Demand set up, along with the option to review parsed CV’s.  

How: 

Locked the field on the form  

Why: 

Users shouldn’t have been able to change the Contact during review of a CV. This will help improve data quality and reduce accidental changes. 

77772: 

Financials from Agreement on Mercury Vacancy 

Not all ‘FINANCIALS’ from the Agreement were being copied to the Vacancy when adding. All values will now be added to the Vacancy when adding an Agreement including; Margin % & Mark-up.  

71283: 

Placement Start Date not Mandatory 

Previously, the Placement Start Date was not mandatory, even though it is listed in the MANDATORY_CONFIG in the Placement UCI and Mercury Placement forms. This has now been rectified.  

66387: 

Calculated Values not updating when Placement Extended 

Extending a Temp or Contract Placement did not always recalculate Calculated Values for the new duration stipulated, instead it retained values from the original Placement. This has now been changed so that the Calculated Values recalculate on the Extension, taking into consideration the Start and End dates. 

72043: 

Activity Owner changing on Re-assign of Contact 

‘Activities’ were having their Owner changed when the Owner of a Contact was changed. This has now been fixed.  

75077: 

Cancelled Placement Approval still able to Approve / Reject 

The ‘Approve/Reject’ button on completed ‘Placement Approval’ records is now hidden. 

69621: 

Activity Grid not preserving selected environment Phone Calls in iframe 

There was an issue where the ‘Activity Grid’ under ‘Recruiting’ tab was not preserving the correct environment in the Mercury Account. This has now been fixed.  

78905: 

Vacancy UCI backup form deleted from core solution  

There is a patch available that will re-instate the ‘Vacancy UCI’ backup if it has been removed from the ‘Vacancy’ entity and ‘UCI backup’ form.  If you would like this patch please raise a support ticket via the Support Portal.  

80545: 

Console errors in contact, vacancy, agreement, shortlist 

Console errors were seen on load of ‘Contact’, ‘Vacancy’, ‘Agreement’ and ‘Shortlist’ – this has now been fixed.  

77613: 

Source not Filtering to Vacancy Sources  

On the 'Mercury Vacancy' form, the 'Source' field was not filtering correctly – this has now been fixed so that ‘Candidate Source’ can be selected as well as ‘Vacancy Sources’. 

79981: 

Email editor selected template using name instead of subject  

The email editor was selecting a template based on the subject instead of the name – this has now been changed. 

80514: 

Spelling options in Email Editor 

Previously users had to press ctrl + right click to see the spell check in the Email Editor, now they can simply right click to use spell check. 

80601: 

Contact Recruiter View 404 Error  

The recruiter view iFrame was failing to load in some entities – this has now been fixed. 

80905: 

Email Editor HTML from Template  

Previously, when inserting a Dynamic Email Template into the Email Editor, all HTML styles were removed. This has now been fixed so that the styling now stays. 

80913: 

Placement extension error for multioptionset fields - "There was an error generating the XML document"  

There was a Placement extension error for multi-option set fields, this has now been fixed.  

81815: 

Error occurs in Email Editor when Dynamic Email Template does not have a subject 

There was an error in the Email Editor when a Dynamic Email Template did not have a subject. This has now been rectified. 

65091: 

Last Contacted on Hotlist M22756 

‘Last Contacted’ was inadvertently removed when looking at Contacts on a Hot List. Please note, depending on the ‘Context’ of the Hot List will depend on the column visible; 
Candidate Hot List = Last Contacted 
Client Contact Hot List = Last Contacted As Client  

69991: 

Is Margin Only not showing on Mercury Placement 

‘Is Margin Only’ field was not visible when using Mercury Placement Form, we have now added this back. 

72045: 

Contact Activity View not showing Activities  

On the Candidate Tab of the Mercury Contact form the following activities are now available - Candidate Phone Calls, Candidate Emails, Candidate Appointments   
On a Client Contact tab of the Mercury Contact form the following activities are now available – Client Contact Phone Calls, Client Contact Emails, Client Contact Appointments 

80478: 

EWI - Address Cascade throws error when using BPF  

Resolved an issue which prevented Users from updating ‘Post Code’ on a Client via a Business Process Flow 

84671: 

Script error on client when Recruiter Portal url is empty 

A script error was seen on load of client entity when 'RECRUITER_PORTAL_URL' didn’t exist or value was null. This has now been fixed.  

78067: 

Script error on Client lookup 

There was a script error on the ‘Mercury Contact’ form – this has now been resolved. 

72039:  

Initial Team not set on Placement Create 

When a new placement was created there was an issue where an initial team was not being set up. This has now been resolved and you can view the initial team associated with the placement via the Audit History. This is only applicable for Placements created after v33. 

81778: 

Agreement Details on Vacancy - fee not being populated 

Previously the financial details were not being populated from an agreement when a new vacancy was being created via the vacancy forms. This has now been resolved. Note – please check that the financial detail defaults are correct – for permanent it should be Fee % and Fee Based On, and for contract it should be Margin % and Markup %