Below is an itemised list of what has been released in version 34 of Mercury.
UI/UX Enhancements
| 91376 | New 'Board View' available |
What: | The brand-new Board view gives you a quick and easy way to progress your candidates through the shortlisting, interview and placement process. The Shortlist Board view works like a Kanban board and allows you to quickly and easily drag and drop candidates through the various recruitment stages. |
Where: | Vacancy – Candidates - Shortlists – Board View |
Why: | Simple to use drag and drop functionality makes it easy and quick to understand where your candidates are at any point in the recruitment process. |
| 63027 | Worker Type Compliance |
| What: | New entity which allows Customer to group Compliance that is specific to a particular type of worker. This will reduce the duplication of Agreements. When on a Placement, users will be able to build up Compliance from different sources (Agreement & Worker Type). Specific users can now create worker types and add compliance criteria to them. |
| Where: | Mercury & Admin & Worker Types |
| Why: | This will enable you to add suitable Compliance items relevant to a particular type of worker which will mean you will no longer need to create multiple Agreements. |
| 63037 | Adding Worker Type to Placement ℹ️Click for additional information |
| What: | Consultants are able to add one or more worker types to a Placement. |
| Where: | Mercury Placements Worker Types section. This will be on as default but can be hidden via its own config ENABLE_WORKERTYPES_VISIBILITY |
| Why: | This will enable users to associate relevant a Primary Worker Type and Additional Worker Types with a Placement and link the appropriate Compliance items. |
| 63036 | Banner on Worker Type |
| What: | Added a function that will check for related Placements on the Worker Type Form and show a banner to tell you if a related Placement exists. |
| Where: | On the Worker Type information main Form |
| Why: | This will enable uses to quickly and easily see if a Worker Type has been previous linked to a Placement. |
63038 | Worker Type on Extension |
| What: | Ensure that the Worker Type(s) chosen on a Placement are Extended to a new Placement, along with Compliance items attached, adhering to existing rules. |
| Where: | On Placement; Worker Type (SubGrid) |
| Why: | This will make sure that the relevant data and information is shown on the newly extended Placement |
| 63093 | Remove Compliance when removing Worker Type on Placement |
| What: | Compliance Statuses are deactivated/deleted based on its validity and confirmation status when a Worker Type on the Placement is removed. Compliance Status records are only deleted when its validity is invalid and its confirmation status is outstanding. In all other scenarios they are deactivated. |
| Where: | Placement Forms |
| Why: | This means that there will not be any unnecessary Compliance on a Placement that is no longer needed, and you will not need to delete them manually which will save you time. |
| 80697 | Worker Type on Clone |
| What: | When a Placement is Cloned this will ensure that the Worker Type(s) chosen on a Placement are Cloned to a new Placement. |
| Where: | Placement |
| Why: | This will make sure that the relevant data and information is shown on the newly cloned Placement. NO compliance will be added to that cloned Placement |
| 88224 | Placements View on Worker Types |
| What: | Users can view Placements associated with a Worker Type directly from the Placements tab in the Worker Type form. |
| Where: | Mercury; Admin; Worker Types; Placements. Visibility of this section is controlled by the config: ENABLE_WORKERTYPES_VISIBILITY |
| Why: | This allows you to easily view and manage Placements linked to a Worker Type, supporting Compliance and associated tracking without navigating to each Placement. |
| 63087 | Add Existing Compliance Criteria to Worker Type |
| What: | Users have the ability to add a new/existing Compliance Criteria to a Worker Type and for that to cascade to relevant Placements that are not Completed, Cancelled or Terminated. |
| Where: | Worker Type Form |
| Why: | This means that users will not have to create duplicate Compliance Criteria when creating a Worker Type Compliance. |
| 80696 | Remove Compliance from Worker Type |
| Why: | When removing a Compliance status from a Worker Type, the relevant rules are applied;
|
| Where: | Placement Worker Type Compliance |
| Why: | This means that users will not need to remove Compliance from these Placements manually |
| 88143 | Worker Type when Convert to Perm |
| What: | When a Placement is converted to a Permanent Placement, any worker types are copied over to the new Placement. The new Placement will then inherit any Compliance associated with those Worker Types. |
| Where: | On a Contract/Temporary Placement, there is ribbon button called Convert to Permanent. |
| Why: | This means that all the relevant information is copied over and users will not need to add them manually. |
| 88375 | Duplicate Worker Type Code |
| What: | When creating a Worker Type, if a user adds a 'Code' that already exists they will get a message to let them know what the error is when trying to save the record. |
| Where: | Worker Type Form |
| Why: | This will give you information about any duplicate codes, that you can rectify in order to successfully save the record |
| 80695 | Worker Type within Placement Validation |
| What: | Users have the ability to add 'Worker Type' Compliance to the new Placement Validation process within Mercury. |
| Where: | New Placement Validation Form |
| Why: | This will ensure that Recruiters are either populating the Worker Type or reviewing it before submitting a Placement for Validation — supporting early compliance checks. |
| 88309 | Candidate Company SharePoint Location |
| What: | A SharePoint document location is now automatically created when a Candidate Company is created. Note - To ensure an existing Candidate Company document location is generated, either select Documents from the Related menu or run the flow Create or Update Candidate Company SharePoint Loc from the ribbon |
| Where: | Mercury - Admin – Section - Candidate Company |
| Why: | You will not need to navigate to the Documents tab to trigger the creation of the location, saving you time. |
| 85577 | Add Compliance Status for Candidate Company on Placement |
| What: | When adding a Worker Type or Agreement with Compliance linked to a Candidate Company, any Compliance Evidence created is also linked to the Candidate Company. |
| Where: | This logic applies during the creation of Compliance Evidence records—triggered from Worker Type or Agreement forms in Mercury. |
| Why: | This enables you to easily identify and navigate directly to the related Candidate Company from the Compliance Evidence, improving visibility and efficiency. |
| 83086 | Associate Compliance Criterion to Candidate Company |
| What: | When setting a Compliance Criterion, we have added the option for the evidence to be linked to a 'Candidate Company' so that they can build up required pieces of Compliance for a Candidate Company umbrella company. |
| Where: | Compliance Criterion main Form |
| Why: | This will allow you to easily build up required pieces of Compliance for a Candidate Company /umbrella company. |
| 92663 | No Candidate Company on Placement - Compliance Status |
| What: | Automatically set a Compliance Status record to Valid or Invalid based on the Compliance Criterion’s “If Missing Evidence” value and whether the related Placement has a Candidate Company.
|
| Where: | This logic runs during the creation of Compliance Status records in the system, especially when the evidence is linked to Candidate Company. |
| Why: | This means that you know that you don’t need to collect evidence when a Candidate Company is missing, and the Compliance Criterion says it’s still valid, saving time and avoiding unnecessary actions. |
| 92665 | Changing Candidate Company on Placement - Compliance Status |
| What: | When changing the Candidate Company on a Placement, the Compliance Statuses update to reflect the new Candidate Company. If the Candidate Company is removed, the system uses the “If Missing Evidence” setting from the Compliance Criterion to decide whether each Compliance Status remains valid or becomes invalid, so it's clear which Compliance items are still required. |
| Where: | On update of the Candidate Company field in the Placement record. |
| Why: | To ensure Compliance Status records reflect the correct Candidate Company or handle missing ones properly, maintaining accurate Compliance tracking. |
| 84981 | Sort Email Templates A-Z |
| What: | Users now have the ability to sort Email Templates in the Email Editor alphabetically (A-Z). The order is specifically special characters, numeric and then alphanumeric. |
| Where: | In Mercury, select a Candidate and choose Email--> To candidate. When the Email Editor has loaded click Insert-->Insert Template from the menu. |
| Why: | This will make it easier for users to quickly identify a template to use when creating an email, instead of having to scroll up and down in an un-ordered list of templates to find what they want. |
| 83095 | Upload Multiple Documents to SharePoint |
| What: | Users are now able to upload multiple Documents from their SharePoint environment via a new “Open SharePoint” button. Note – If you receive 401 unauthorised error, this is because the connection to SharePoint hasn't been established. To resolve this, simply open the SharePoint location. |
| Where: | Go to one of the enabled entity's record and then go to Related Documents. This will show a SubGrid with the new Open SharePoint button |
| Why: | This allows users to upload a wide range of documents for all entities that have SharePoint enabled without having to do it one, or having to open the SharePoint location, saving time and providing a better user experience. |
| 89168 | Use Mercury Form as Default |
| What: | Mercury Forms are now the default choice across the different places they are used. The Legacy UCI forms are still available to select if you wish to. |
| Where: | Contact, Placement, Client and Vacancy entities. |
| Why: | This will make it easier to access and use the new Mercury Forms |
| 83088 | Auto Calculate Financials on Rate Change |
| What: | Auto Calculate Financials for a Placement will automatically update when changing Standard Rate. This is only applicable for 'Hourly & 'Daily' rates and based on the values (Hours per Day) on the Placement. |
| Where: | Mercury Placement and UCI Form |
| Why: | This functionality will mean that you will not need to manually recalculate the values or update the relevant fields, saving you time and effort. |
| 15687 | User / Team Security Access for Recruiter |
| What: | We have created a new Security Role to give edit permissions on the Users and/or Teams record. Mercury administrators will need to assign this new role to users who need the permission, and the following roles will no longer be able to edit users or teams records.
|
| Where: | Mercury Admin - Security |
| Why: | To enable admins to decide who should be able to make changes on the Users and Teams entities. New role is called ‘Mercury - Can edit user and team records’. |
| 85688 | Source on Spec Send |
| What: | Ability to record a Source on a Spec Send |
| Where: | Spec Send & Sources within Mercury |
| Why: | This will enable you to identify where a Spec Send originated from for greater reporting and tracking |
| 79830 | Rename 'Accounts Contacts' |
| What: | To improve consistency across the Mercury Platform we have changed the name of Accounts Contacts to Invoice Contacts in the Client entity. If this is populated on the Client, it will automatically populate 'Invoice Contact' on any Placement created for that Client. |
| Where: | Client Entity |
| Why: | Consistency is important as it improves the user experience of working in Mercury. |
| 81199 | Timesheet & Expenses Control |
| What: | We have changed “Create Timesheets” and “Create Expenses” so that they are now toggles in order to improve the consistency of user’s experience of Mercury. |
| Where: | Mercury Placement Form |
| Why: | Consistency is important as it improves the user experience of working in Mercury. |
| 83015 | Candidate Pay on Temp Placements |
| What: | Candidate Pay information is now viewable in the Temporary Terms section of the Basic Info tab. |
| Where: | Basic Info tab of Mercury Placement form for Temporary Placements |
| Why: | This enables you to easily see the actual amount the candidate will be receiving. |
| 83165 | Difference in Calculated Values between Contract & Temp |
| What: | We have standardised the Calculated Values fields across both Contract and Temporary Placements. The fields are now the same and also appear in the same order to give a consistent user experience across both areas. |
| Where: | Contract and Temporary Placements |
| Why: | Consistency is important as it improves the user experience of working in Mercury. |
| 87350 | Vacancy Tab Changes |
| What: | The Vacancy section had a lot of tabs making it difficult to see all of the information. We have therefore moved the Advert Details tab to the Job Details tab. In addition, the Advert Text 1 and 2 fields are now Rich Text editors. In v35 we will be making other fields Rich Text as well. |
| Where: | Vacancy Tab of Mercury Vacancy Form |
| Why: | This will help to simplify your experience of the Vacancy tab, making it easier to use |
| 85026 | Hierarchy on Vacancy lookups |
| What: | The hierarchy filter is now applied on the Hiring Manager and End Client/End Contact lookups in the New Vacancy Form. This means that when changing the Contact (if more than one Hiring Manager exists), the Hiring Manager will show records related to Client field on both the Legacy and New forms. The same goes with End client and End contact |
| Where: | Vacancy Form |
| Why: | This brings parity to the functionality between the Legacy UCI form and the New Vacancy Form. |
| 83093 | Placement Owner on Extension |
| What: | You are now able to decide who the Owner of the Extended Placement should be by using existing configuration. If adding Owner (ownerid) into the EXCLUDE_FIELDS_EXTEND_PLACEMENT, the Owner of the Extended Placement will be the individual who pressed the Extend button. |
| Where: | Update to the 'EXCLUDE_FIELDS_EXTEND_PLACEMENT' Configuration record and this will then take effect when extending a Placement. |
| Why: | This will mean that it is simpler to ensure that business process and ownership rules can be created and followed for Extended Placements. |
| 74627 | Create Mercury Advert after posting a Job to Broadbean and Logic Melon (IDEA-01388 & M23477) |
| What: | When a Job is posted to BroadBean and/or Logic Melon a Mercury Advert is now automatically created. |
| Where: | Advert Table. This can be found under ‘Related’ on a Vacancy or via Advanced Find. |
| Why: | This will allow for a better understanding of which jobs are being posted and assess the use of job boards. |
| 83091 | Change Client |
| What: | You are now able to change the Client & Client Contact on a Placement. To enable this, Security settings need to be changed – please go to the support portal and raise a ticket if you would like to do so. This will then show a new “Novate” ribbon button |
| Where: | Placement Form |
| Why: | This will allow you to make any necessary amendments to the Client associated with a Placement. If a Placement has been created for the wrong Client (different Division or Child Client), you can now change the Client & Client Contact on the Placement. A new Placement will be created with the New Client & Client Contact selected. Please note, the below fields will be cleared when running this process;
|
| 89140 | Daxtra On Demand - Record Parsing Method |
| What: | The method used to upload a CV using Daxtra On Demand is now recorded in the Source Spool field. |
| Where: | When parsing using Daxtra On Demand |
| Why: | This makes it easy for you to see which method (API, Manual etc) has been used to parse the CV. |
| 89140 | On Demand - Latest Source Field Within Upload Modal |
| What: | Users are now able to update the ‘latest source’ field when they parse a CV via Daxtra On Demand. |
| Where: | When manually parsing a CV. |
| Why: | This will enable you to easily update the field should you need to. |
| 77692 | Removal of Placement Audit Events |
| We've taken the decision to stop creating Placement Audit Events when an incremental update is made to a Placement. We've found no Customer is utilising this information and creating these records has a negative impact on Storage. In future releases we will be looking to completely remove the table from Mercury. The Placement Audit Event records can now be deleted, if you wish to reduce the Storage impact these records are having. | |
| 65310 | “Validate Placement” Form Not Loading Correctly without Mercury Security (M21151) |
| Our New Placement Validation process inadvertently required Users to have either ‘Mercury - Recruiter’ or ‘Mercury - Recruiter w/o Create Client’ security role to access. This is now resolved meaning you can continue to use your custom security roles and use the New Placement Validation process. | |
| 91058 | Additional configurability – Hidden & Mandatory fields. |
| We've added some additional configurability for Hidden & Mandatory fields within Mercury. You or the relevant Administrator can create a configuration record (similar to the existing ones) for a particular entity and any field specified will be hidden or made mandatory. |
Software Fixes
| 87399 | PDF CV Rendering fails when using WopiFrame.aspx CV Preview Url |
| An issue was found where CV Previewing was not working for PDF documents. This is now working as expected. | |
| 75146 | Sending Email in quick Succession will delete Attachments - IWI |
| When sending emails to a Client Contact or Candidate Contact, the attachments were being stripped if they were sent within a very short period to the same contact. This is now resolved. | |
| 85048 | Line Breaks in Email Editor |
| Previously, the Email Editor had an option to add a line break but after an update the line break default was 1.0 and users were unable to edit it. This has now been resolved. | |
| 85733 | Addresses within Interview |
| When selecting an Address within Update Candidate for a Face to Face meeting, all Addresses were being shown instead of Addresses associated with the Client. This is now resolved. | |
| 87250 | Gross Profit Currency not visible - M27645 |
| An issue was identified where True Gross Profit and True Weekly Gross Profit currency fields were missing on the Placement UCI form. The issue was only affecting Contract Placements and has now been resolved. | |
| 83330 | Placement Validation - Populating Postcode field when Config is empty |
| When the Placement Validation config is empty it was still displaying the Postcode/Address fields for the entities. This is now working as expected. | |
| 84338 | Placement Validation shows "Fixed Term Contract" always |
| “Fixed Term Contract” field was always showing when validating a Permanent placement when this field is not present in the PLACEMENT_VALIDATION_PLACEMENT.CRIMSON_PLACEMENT Configuration Item. This is now working as expected. | |
| 84453 | Mercury Vacancy - Agreement Lookup has recent filter |
| When searching for an Agreement on the Mercury Vacancy form, the recent filter was being applied to the lookup, so any recently viewed or created agreements can be added to the vacancy, even when incompatible. This has now been resolved. | |
| 84460 | Setting financial details, fields lock and unlock incorrectly |
| When setting Values in the Financials section, the fields were unlocking and locking incorrectly. These are now working as expected. | |
| 88344 | Progress Candidate > Accept Offer script error from Shortlist Home Grid |
| When a user attempted to use the Progress Candidate functionality to Accept Offer from the Shortlist Home Grid, nothing happened, and a script error was shown in the browser console. This has now been resolved. | |
| 81782 | Locked List on Mercury Placement |
| Not all fields specified as being locked within the Config were showing as locked on the UCI Form & Mercury Placement Form. This has now been resolved. | |
| 84791 | Finalised Field not locked in Header & Type to be unlocked - Mercury Placement Form |
| The Finalised field was not locked on the header of the Mercury Placement form and type was editable. This has now been resolved. | |
| 89624 | Unable to create Contract Vacancy > Margin error |
| When creating a new Contract Vacancy, Margin & Markup were incorrectly being specified as mandatory. This has now been resolved | |
| 82158 | Mandatory Financials on Shortlist at Selected |
| An issue was identified where users were unable to save a Shortlist without inputting financial details at 'Selected' stage. This has now been resolved. | |
| 91107 | Geocoding for Hong Kong doesn't work as expected |
| An issue was identified where geocoding of Locations in Hong Kong were not working as expected. This has now been resolved. |