Mercury 2026.3 Release Notes - August 2026

Release Notes Index▪️Release Overview▪️Role-base Impact Summary▪️Consultant Workflow and Navigation▪️Candidate Pipeline and Shortlist Management▪️Communication and Email Tracking▪️Placements, Fees and Financials▪️Admin, Integrations and Configuration▪️Advance Notice of Legacy Components Removal

 

Release Overview

This release includes practical updates grouped around the main ways recruitment teams use Mercury day to day: navigating core records, progressing candidates, managing communication, maintaining placement and finance accuracy, and administering integrations and configuration. Together, these changes help consultants work faster, reduce avoidable admin, improve data quality, and keep momentum across live vacancies, shortlists, placements, and client communication.

• Consultant workflow and navigation: Record screens, menus, workspace views, ribbon actions, and search-style controls are easier to use. This helps consultants find the right information faster, complete common actions more consistently, and spend less time moving between screens.
• Candidate pipeline and shortlist management: Shortlist progression, vacancy pipeline views, candidate status updates, interview rescheduling, and client portal engagement tracking have been improved. This gives recruiters clearer control over candidate movement and helps them keep vacancies progressing.
• Communication and email tracking: Email editor improvements, Spec Send updates, reply tracking, auditing, and better client context handling make communication easier to manage. This helps consultants follow up more reliably and keeps candidate and client activity linked to the right records.
• Placement, fees, and finance accuracy: Placement actions, validation, currency alignment, fee handling, timesheet descriptions, tax calculation, and agreement approval have been strengthened. This reduces manual correction, improves audit accuracy, and helps finance and operations teams trust the values held in Mercury.
• Admin, integrations, and configuration: Security roles, third-party iframe access, user identifiers, currencies, contact method rules, notifications, and deployment tracking have been improved. This gives CRM admins and support teams better control over configuration, access, integrations, and solution reliability.

 

Role-based Impact Summary

Recruiters and Consultants: This release reduces day-to-day friction by making key records easier to navigate, improving shortlist progression, strengthening candidate pipeline visibility, and making common actions more consistent across records. Updates from this release (Can see Audit History without Data Protection Officer role on a contact; SharePoint Client Folder Names) support faster day-to-day recruitment execution with less context switching.

Team Leads and Managers: The updated workflows improve consistency across consultants by standardising ribbon actions, shortlist handling, candidate progression, and workspace views. Item-level changes improve team consistency by giving clearer board/list standards across consultants.

Finance and Operations teams: Placement, fee, timesheet, and tax updates improve accuracy, reduce manual correction, and make finance-related records easier to review.

Compliance and Operations: Changes to audit visibility, email tracking, permissions, and configuration handling support cleaner governance and more reliable operational controls. Delivered items strengthen record quality and communication traceability, helping reduce avoidable process drift.

CRM Admins: Admin and integration updates make it easier to manage security roles, third-party access, user identifiers, currencies, and deployment consistency. CRM admins can use these changes to tighten data-source and hierarchy updates and support smoother adoption.

 

Consultant Workflow and Navigation

62979 - Contact > Related Menu Tidy Up

• What: Grouped all Mercury-related entities into a single section, arrange them in alphabetical order and ensured unique names.
• Where: Mercury Contact form > Related Menu.
• Why: To improve form usability, maintain consistency, and make Mercury entities easier to locate and navigate.

62989 - Vacancy > Related Menu Tidy Up

• What: Grouped all Mercury-related entities into a single section, arrange them in alphabetical order and ensured unique names.
• Where: Mercury Vacancy form > Related Menu.
• Why: To improve form usability, maintain consistency, and make Mercury entities easier to locate and navigate.

105530 - Address Picker Control on Mercury Contact

• What: The new style address picker has been added to the Mercury Contact form for Work Address.
• Where: Contacts --> Mercury Contact Form > Work Address.
• Why: Updated Address control which introduces ability to Search across the address without having to scroll if the Client has a long list of addresses.

 


 

108586 - Increase iframe Sections to Remove Nested Scrolling

• What: Removed the embedded scrolling on Manage Adverts.
• Where: Vacancy > Manage Adverts tab.
• Why: Iframe sections have been increased to better fit their content and reduce nested scrolling. This gives users a smoother screen experience and makes information easier to review in one place.

112969 - Mercury Ribbon Button Structure – Info

• What: Applied the ribbon button structure to Info forms, home grids, and subgrids, following the same pattern used across the application.
• Where: Available on Info forms, Info home grids, and related subgrids.
• Why: To provide a consistent and streamlined command experience for users when working with Info records across different areas of the system. This ensures actions are presented in a uniform way, making navigation easier and improving overall usability.

112972 - Mercury Ribbon Button Structure – Applicant

• What: Applied the ribbon button structure to Applicant forms, home grids, and subgrids, following the same pattern used across the application.
• Where: Available on Applicant forms, Applicant home grids, and related subgrids.
• Why: To provide a consistent and streamlined command experience for users when working with Applicant records across different areas of the system. This ensures actions are presented in a uniform way, making navigation easier and improving overall usability.

112974 - Mercury Ribbon Button Structure – Projects

• What: Applied the ribbon button structure to Project forms, home grids, and subgrids, following the same pattern used across the application.
• Where: Available on Project forms, Project home grids, and related subgrids.
• Why: To provide a consistent and streamlined command experience for users when working with Project records across different areas of the system. This ensures actions are presented in a uniform way, making navigation easier and improving overall usability.

112975 - Mercury Ribbon Button Structure – CV Documents

• What: Applied the ribbon button structure to CV Document forms, home grids, and subgrids, following the same pattern used across the application.
• Where: Available on CV Document forms, CV Document home grids, and related subgrids.
• Why: To provide a consistent and streamlined command experience for users when working with CV Document records across different areas of the system. This ensures actions are presented in a uniform way, making navigation easier and improving overall usability.

116473 - Contact 'Overview' tab

• What: There is a new tab called "Overview" available on the Contact form. It contains an IFrame that loads a web portal associated with the current Contact record. This can be hidden by config " ENABLE_WEB_UI " and will be on by default for existing Customers. If you want this turned off, please log a request via the portal.
• Where: Contacts → Mercury Contact.
• Why: So the user can view key external insights immediately upon opening the record. This matches the view within Search. You can also change the form context if the person is both a Candidate & Client Contact

117028 - Ability to view Connections on a Contact

• What: Contacts now display their active Connections directly within the main record, allowing you to quickly see who they are connected to without navigating away. Both “To” and “From” relationships, along with their roles, are clearly visible.
• Where: Mercury > Contacts > Open a Contact > General tab > Contact Details.
• Why: This makes it faster for recruiters to understand a contact’s network and relationships at a glance, reducing clicks and improving efficiency when reviewing or qualifying connections.

 

119396 - Configurable Work List / Sales Accelerator

• What: Add a new Work List area in the Mercury and Mercury Admin apps to surface Dynamics 365 Sales Accelerator functionality. Guide to follow on how to set up.
• Where: The Work List area should be placed underneath the Dashboards section in both the Mercury and Mercury Admin apps.
• Why: To provide users with quick access to Sales Accelerator work items and improve activity management and productivity.

120342 - Mercury Ribbon Button Structure – Client

• What: Applied the ribbon button structure to Client forms, home grids, and subgrids, following the same pattern used across the application.
• Where: Available on Client forms, Client home grids, and related subgrids.
• Why: To provide a consistent and streamlined command experience for users when working with Client records across different areas of the system. This ensures actions are presented in a uniform way, making navigation easier and improving overall usability.

120649 - New Applicant system views

• What: New views added to the Applicant entity which give the user clear view of Applicants in certain statuses.
• Where: Applicants > Home grid.
• Why: To assist with the new 'Workspace' experience, Consultants can quickly see applicants they own at key stages, including New, Suitable, and May Be Suitable My New Applicants - all applicants owned by the user that are at the Applied stage My Suitable Applicants - all applicants owned by the user that are at the Suitable stage My Potential Applicants - all applicants owned by the user that are at the May be Suitable stage.

128686 - Unhide Mercury Flyout on Entities where it is forcefully hidden

• What: The Mercury flyout is now always visible across all entity grids, even when no actions or buttons are available or no records are selected . This includes ensuring the flyout is no longer hidden in scenarios such as empty states or multi-select grids, and that it remains permanently visible on the Spec Send related grid.
• Where: Mercury > Entity Grids (including Client, Contact, Vacancy, Placement, Shortlist, Info, Spec Send, Agreements).
• Why: This creates a consistent and predictable user experience across Mercury, so users always know.

Bug Fixes

46049 - SharePoint Client Folder Names

Client SharePoint folder names now handle spaces correctly. This makes client folders easier to find when searching in SharePoint.

67170 - Hidden Tabs on Vacancy not working

Vacancy tab visibility settings now work as intended. Teams can hide configured tabs on the Vacancy form, helping keep the screen focused on the information users need.

106638 - Default Rates on Vacancy

Vacancy frequency values now stay as saved instead of reverting to Daily after refresh. This prevents consultants from repeatedly correcting the same field.

110118 - PostCode Labels in Mercury

Postcode labels have been made consistent across Mercury. This gives users a cleaner experience and avoids confusion caused by different label formats.

112791 - Desirable Tag not loading

Desirable tags now load more reliably when creating or editing vacancy records. This reduces refreshes and helps consultants capture vacancy requirements first time.

115000 - Quick Create Client Script Error

The script error on Quick Create Client in Mercury Admin has been fixed. This gives admin users a smoother experience when creating client records.

115470 - Similar Name Tag showing in Control

Tag controls now handle similar tag names more accurately. This helps prevent the wrong candidate tags being added and improves data quality.

118234 - PCF Tag control data is being reset

Vacancy tags are no longer cleared after opening and closing the Vacancy AI dialog. This protects entered data and reduces avoidable rework.

120883 - Idibu iframe showing the incorrect vacancies

The Idibu iframe now shows the correct vacancy when users switch between vacancy records. This helps consultants manage adverts with confidence and avoids acting on the wrong vacancy.

126748 - New Mercury Ribbon Buttons Fail to Load

Mercury ribbon buttons now load more reliably when users move around the platform. This keeps common actions available when consultants need them.

128932 - Browser tab name issue when viewing integrations screen

The browser tab name now displays more clearly when viewing the integrations screen. This makes navigation easier when users have multiple tabs open.

 

Candidate Pipeline and Shortlist Management

69063 - Update Candidate (Submit incl Multi) on Info Shortlist

• What: Users are now able to progress individual Info Shortlists of multiple to a Submit stage with the new Update UI that has also been applied to the Shortlist records.
• Where: Info Shortlist > Update.
• Why: This gives recruiters a consistent way to move candidates forward and keeps shortlist work aligned with the wider candidate update process.

88897 - Info Shortlist Update

• What: When progressing an info shortlist, these updates now appear on the Shortlist Update entity and so are visible from the Candidate timeline. Please note, this is the same record as Shortlist Updates.
• Where: Shortlist Update on Timeline.
• Why: Candidate timelines now show activity when a candidate has been submitted or progressed as an Info Shortlist. This gives consultants clearer visibility of recent activity when reviewing a candidate record.

112970 - Mercury Ribbon Button Structure – Info Shortlist

• What: Applied the ribbon button structure to Info Shortlist forms, home grids, and subgrids, following the same pattern used across the application.
• Where: Available on Info Shortlist forms, Info Shortlist home grids, and related subgrids.
• Why: To provide a consistent and streamlined command experience for users when working with Info Shortlist records across different areas of the system. This ensures actions are presented in a uniform way, making navigation easier and improving overall usability.

116475 - Vacancy 'Overview' screen

• What: There is a new tab called "Overview" available on the vacancy form. It contains an IFrame that loads a web portal associated with the current vacancy record. This can be hidden by config " ENABLE_WEB_UI " and will be on by default for existing Customers. If you want this turned off, please log a request via the portal.

• Where: Vacancies --> Mercury Vacancy.
• Why: So the User can see key external insights as soon as they open the record.

118911 - New 'Pipeline' tab on Vacancy

• What: There is a new tab called "Pipeline" available on the vacancy form and is located immediatly after the Candidates tab. It contains an IFrame that loads a web portal associated with the current vacancy record. If you want this turned off, please log a request via the portal.

• Where: Vacancies --> Mercury Vacancy.
• Why: This allows recruiters to manage candidate progression more seamlessly within the same workflow, reducing the need to switch tabs and helping them move candidates through the pipeline more efficiently.

 

120585 - Only one appointment shown in Reschedule Interview

• What: Users are now able to view all appointments relating to that Shortlist rather than the latest one.
• Where: Shortlist > Update button > Reschedule Interview.
• Why: The Reschedule Interview experience now shows the relevant active interview appointments more clearly. This supports faster rescheduling and reduces the risk of acting on the wrong interview.

123989 - Add fields to shortlist entity in core

• What: Added new fields on a Shortlist to record events from the Candidate Portal. This feature is coming soon but we have created the fields in preparation for it's release.
• Where: Shortlist > Audit & Activities > STATUS AUDIT section.
• Why: Additional fields have been added to the Shortlist entity to record when a candidate has been viewed in the Client Portal and how often. This gives consultants better insight into client engagement with submitted candidates.

124000 - Update Candidate (Client Shortlisted incl Multi) on Info Shortlist

• What: Users are now able to progress individual Info Shortlists of multiple to a Client Shortlisted stage with the new Update UI that has also been applied to the Shortlist records.
• Where: Info Shortlist > Update.
• Why: This gives recruiters a consistent way to move candidates forward and keeps shortlist work aligned with the wider candidate update process.

124001 - Update Candidate (Reject incl Multiple ) on Info Shortlist

• What: Users are now able to progress individual Info Shortlists of multiple to a Reject stage with the new Update UI that has also been applied to the Shortlist records.
• Where: Info Shortlist > Update.
• Why: This gives recruiters a consistent way to move candidates forward and keeps shortlist work aligned with the wider candidate update process.

124058 - Rejection Reason on Info Shortlist

• What: Added a 'Rejection Reason' on an Info Shortlist, allowing you to select a reason.
• Where: Info Shortlist > Form & Update.
• Why: Recruiters can now select a rejection reason when rejecting an Info Shortlist. This avoids free-text entry, improves consistency, and brings the experience closer to standard Shortlist rejection.

126403 - Kanban View on Pipeline Tab

• What: The Kanban board used on the Candidates tab is now also available on the Pipeline tab for Vacancies, displaying candidate progression for the selected vacancy within the same board view.
• Where: Mercury > Vacancies > Vacancy record > Pipeline tab.
• Why: This allows recruiters to manage candidate progression more seamlessly within the same workflow, reducing the need to switch tabs and helping them move candidates through the pipeline more efficiently.

 

128769 - Clear Shortlist Substatus once progressed

• What: Clear the Substatus field automatically whenever a Candidate is moved to a new Status .
• Where: Shortlist record – during Candidate progression (Kanban, Update, or Progression).
• Why: To prevent outdated or incorrect Substatus values from remaining after the Candidate's Status changes. This helps avoid mismatched statuses and keeps candidate progress data aligned.

When a candidate is progressed, any existing Shortlist substatus is cleared automatically. This helps avoid mismatched statuses and keeps candidate progress data aligned.

 

Bug Fixes

125369 - Customers unable to progress Shortlist due to Search Result Marker error

A missing permission that could prevent users from progressing Shortlists has been addressed. This helps consultants continue candidate progression without unexpected access errors.

126396 - SHOW_PROGRESS_CANDIDATE_RIBBON_MENU does not control Info Shortlist buttons

The Progress Candidate ribbon configuration now controls Info Shortlist buttons as expected. This gives admins better control over which shortlist actions are visible to users.

126780 - Shortlist - CV is not auto populating on Submit page

The Submit page now handles CV selection from an existing Shortlist more reliably. This reduces manual re-selection and helps consultants complete submissions faster.

126902 - Shortlist - 'Apply to Remaining' on Submit page

The Apply to Remaining option now handles candidate CV attachments more reliably on the Submit page. This helps consultants apply CV selections across multiple submissions with fewer manual checks.

128967 - 'Confirm' button not working on 'Substatus'

The Confirm button now works when adding Substatus or Feedback through the update route. This helps consultants capture candidate updates from grids and forms without losing progress.

129038 - openedFrom not being passed consistently into recruiter portal

Recruiter Portal now receives the expected context more reliably when opened from the Overview tab. This helps embedded portal screens load correctly and show the right information.

 

Communication and Email Tracking

87210 - IDEA-01544 - Increase Email editor character limit

• What: The character limits for Dynamic Email Templates, the Email Editor, and email body content have all been significantly increased to support much larger emails.
• Where: Email Body / Body of Dynamic Email Templates / Body of Email Editor.
• Why: This removes previous size restrictions that forced recruiters to cut or simplify content, enabling richer, more complete email templates. It improves efficiency, reduces formatting issues, and ensures consistency between templates and the editor, while also preventing errors at send time.

112971 - Mercury Ribbon Button Structure – Spec Sends

• What: Applied the ribbon button structure to Spec Send forms, home grids, and subgrids, following the same pattern used across the application.
• Where: Available on Spec Send forms, Spec Send home grids, and related subgrids.
• Why: To provide a consistent and streamlined command experience for users when working with Spec Send records across different areas of the system. This ensures actions are presented in a uniform way, making navigation easier and improving overall usability.

118853 - Email Reply Tracking

• What: Emails now show when they have been replied to, and the original email keeps a running count of replies. Multiple replies can be linked back to the same original email, making it easier to see the full conversation history while existing integrations continue to work as before.
• Where: Email Record.
• Why: This helps recruiters track engagement more easily, see how active an email conversation has been, and reduces the need to manually check or piece together reply chains.

120792 - IDEA-01234 - Add Spec Send button to Info Record Email Editor

• What: You can now access the Spec Send button directly from the Info record email editor, allowing you to generate and send anonymised CVs without creating additional documents. Spec Sends created this way behave the same as existing functionality, are automatically linked to the Info record, and are set to inactive immediately after sending.
• Where: Email Editor launched from Info Record.
• Why: This streamlines the process of sending anonymised CVs, saving time and reducing the risk of errors from creating duplicate documents. It also keeps your workspace clearer by automatically inactivating Spec Sends created from Info records, while maintaining consistency with existing permissions and Spec Send behaviour.

127479 - Consider 'As A' context before setting initial client

• What: Following your feedback we are skipping populating 'BCC' field with Client when Contact is both Candidate and Client Contact and 'As A' context of the activity is set to 'Candidate'.
• Where: Email.
• Why: If the email is addressed to contact as a 'Candidate', we don't want it to show up on Client's timeline.

Bug Fixes

109968 - Multiple spec sends created per email

Sending one email with copied recipients and an attachment no longer creates multiple Spec Send records. This keeps communication records cleaner and avoids duplicated follow-up activity.

116884 - Regarding lost from Email Editor emails (so no data parsed)

Email Editor messages now retain the Regarding value more reliably. This helps merge fields populate correctly and keeps email activity linked to the right record.

120906 - Email IsAuditEnabled not being packaged in solution

Email auditing settings are now included correctly in the solution. This supports better tracking of email activity where auditing is required.

128499 - Initial Fields - Original workflow behaviour not upheld

Initial client behaviour has been aligned more closely with the original workflow. This helps appointment and communication records retain the expected client context.

130186 - Change Tracking - Plugin Assembly WF EmailEditor Merged is changed

The Email Editor merged plugin assembly change has been identified and corrected through change tracking. This helps protect expected email editor behaviour across deployments.

 

Placements, Fees and Financials

53575 - Open Placement from Update Candidate

• What: When accepting an offer, you can now choose to either wait for the Placement to be created and be taken directly to it, or be notified once it is ready. If you choose to wait, a loading screen with the message “Please wait…. the Placement is being created…” is displayed, and you are automatically taken to the Placement in the same tab once it is available. If you choose to be notified, the process closes and you receive an in-app notification when the Placement is created, with a link to open it. Notifications are not sent if you choose to wait. NOTE: The Modified By of the Placement will now be in the context of the service account. Created By however should remain in the context of the user that is running from the page.
• Where: Shortlist record > Update Candidate > Accept Offer.
• Why: This removes the need to manually locate newly created Placements, helping recruiters start work immediately while providing flexibility to either wait or continue working and return via notification.

66276 - Clone Placement to use Custom Page

• What: Update to the UI/UX of Clone Placement to match experience of 'Update Candidate'. The same functionality as before just the look and feel update to be modern and inline with the other pages.
• Where: Placement > Clone Placement.
• Why: matching the experience introduced for Update Candidate. This gives users a more consistent interface for common placement actions.

68551 - Extend Placement to use Custom Page

• What: Update to the UI/UX of Extend Placement to match experience of 'Update Candidate'. The same functionality as before just the look and feel update to be modern and inline with the other pages.
• Where: Placement > Extend Placement.
• Why: Matching the experience introduced for Update Candidate. This gives users a more consistent interface for common placement actions. The user is directed to the newly extended Placement record.

105534 - Address Picker Control within Placement Validation Contact

• What: The new style address picker has been added to the Placement Validation Client Contact form for Work Address.
• Where: Placements --> Mercury Placement Form --> Placement Validation.
• Why: Updated Address control which introduces ability to Search across the address without having to scroll if the Client has a long list of addresses.

 

108549 - Align Currencies on Placement

• What: Four currency synchronisation behaviours have been introduced on the Placement form. Each takes effect immediately when the source currency field is changed, and the dependent fields are set to read-only to prevent manual override.

Source Field Changed	Fields Automatically Updated
Pay Currency	Temp Candidate Pay Currency, Total Estimated Pay Currency, Deduction Currency
Charge Currency	Sales Value Currency
Currency (Transaction Currency)	Margin Value Currency, Gross Profit Currency, True Gross Profit Currency, True Weekly Gross Profit Currency, Weekly Margin Currency
Salary Currency	Permanent Package Value Currency, Permanent Fee Currency

In all cases:

• The dependent currency fields update immediately on change.
• The dependent currency fields are read-only and cannot be set independently of their source field.
• Where: Mercury Placement record form ONLY.
• Why: Recruiters need currency values across a Placement to be consistent and accurate. Previously, changing a primary currency field (such as Pay, Charge, Salary, or Transaction Currency) did not automatically update the associated derived currency fields, creating a risk of mismatched or inaccurate financial data. This change enforces consistency automatically, reducing manual effort and the chance of error.

112641 - Tax on Financial Transactions from Time Sheets Auto Populates and Calculates on Change

• What: Tax fields on Financial Transactions now automatically populate and recalculate without manual intervention.

Pay side:
 

- Tax Code (Pay) is automatically populated from the Candidate Company on the Placement, or falls back to the Tax Code on the Contact's Candidate Company if no Placement-level company is set

- Tax on Payment is calculated automatically as a percentage of Pay (Gross) or Pay (Net) using the rate from the Pay Tax Code lookup

- Pay (Net) always reflects Pay (Gross) minus Tax on Payment

- Pay (Gross) is updated as Pay (Net) + Tax on Payment when values change
 

Charge side:
 

-Tax Code (Charge) is automatically populated from the Client

-Tax on Charge is calculated automatically as a percentage of Charge (Gross) or Charge (Net) using the rate from the Charge Tax Code lookup

-Charge (Net) always reflects Charge (Gross) minus Tax on Charge

-Charge (Gross) is updated as Charge (Net) + Tax on Charge when values change
 

Field editability rules:
 

- Pay (Gross) and Charge (Gross) are always read-only

- Tax on Payment is read-only when a Tax Code (Pay) is present; editable when no Tax Code (Pay) is set

- Tax on Charge is read-only when a Tax Code (Charge) is present; editable when no Tax Code (Charge) is set

- Pay (Net) and Charge (Net) are always editable.
 

• Where: These changes apply to Financial Transactions generated from: Timesheets The form changes on Financial Transactions, will affect Timesheets, Fees, Costs and Expenses.
• Why: Consultants were NOT able to manually remove and re-enter the Tax Code on a Financial Transaction in order to trigger tax calculation. This was a UX issue that could have introduced risk of error and added unnecessary friction to the billing process.

130397 - Tax on Financial Transactions from Fees Auto Populates and Calculates on Change

• What: Tax On Charge Charge Gross fields on Financial Transactions now auto-populate and recalculate automatically when relevant values change, removing the need for manual intervention.

Specifically:
 

- Tax Code (Charge) is automatically populated based on the associated client's tax code (Where available)

- Tax on Charge is calculated from the Charge (Gross) / Charge (Net) value multiplied by the percentage defined on the Charge Tax Code lookup

- Charge (Net) is derived as Charge (Gross) minus Tax on Charge

- Charge (Gross) is kept in sync as Charge (Net) + Tax on Charge.

• Where: This behaviour applies to Financial Transactions that have been created from Fees of type "Fee".

The affected fields on the Financial Transaction form are:
 

- Tax Code (Charge)

- Tax on Charge

- Charge (Net)

- Charge (Gross)

• Why: This change ensures tax values are calculated and kept consistent automatically on change, improving accuracy and saving time for consultants managing fee-based transactions.

 

112692 - Placement > Related Menu Tidy Up

• What: Group all Mercury-related entities into a single section and arrange them in alphabetical order .
• Where: Apply these changes only on the Mercury Placement form .
• Why: To improve form usability, maintain consistency, and make Mercury entities easier to locate and navigate.

112968 - Mercury Ribbon Button Structure – Agreement

• What: Applied the ribbon button structure to Agreement forms, home grids, and subgrids, following the same pattern used across the application.
• Where: Available on Agreement forms, Agreement home grids, and related subgrids.
• Why: To provide a consistent and streamlined command experience for users when working with Agreement records across different areas of the system. This ensures actions are presented in a uniform way, making navigation easier and improving overall usability.

112973 - Mercury Ribbon Button Structure – Fees

• What: Applied the ribbon button structure to Fee forms, home grids, and subgrids, following the same pattern used across the application.
• Where: Available on Fee forms, Fee home grids, and related subgrids.
• Why: To provide a consistent and streamlined command experience for users when working with Fee records across different areas of the system. This ensures actions are presented in a uniform way, making navigation easier and improving overall usability.
   

Bug Fixes

97486 - IDEA-01686 - Timesheet FT Description discrepancies

Financial transaction descriptions from Timesheets are now standardised. This makes finance records easier to understand and reduces the need for manual checks or corrections.

110623 - Placement Validation - State field shown onload for non-US addresses

The State field no longer appears unnecessarily for non-US addresses during Placement Validation. This helps prevent blocked finalisation where a state is not relevant or available.

111699 - Placement - Unlocked Costs - Form OnLoad script error ('Mercury Admin' Model-drive App)

Script errors on the Unlocked Costs form have been addressed. This gives admin and finance users a more reliable experience when reviewing placement cost information.

115303 - Placement Validate - Address fields not showing for Perm or Temp

Placement Validation now shows the expected address fields for permanent and temporary placements. This supports more complete validation and reduces delays when finalising placements.

119102 - Fee not saving once creating

Fee totals now update correctly when a cost is created on a Placement. This helps keep placement cost information accurate without manual recalculation.

120689 - Submit - Fee % is not clearing from Previous selection

The Fee percentage on the Submit page now clears correctly when processing multiple candidates individually. This helps avoid carrying the wrong fee value into the next submission.

120886 - When a fee is cancelled it is still included in calculations - impacting total cost

Cancelled fees are no longer included in placement total cost calculations. This improves financial accuracy and reduces the need to delete records as a workaround.

123874 - Timesheet uploads not always displaying files

Timesheet-uploaded documents are now easier to access through the Documents tab. This reduces confusion when users need to review files linked to a timesheet.

124044 - User unable to Tab through the fields on Submit page

Keyboard tabbing on the Submit page now works more smoothly across fields. This supports faster data entry and a more accessible submission process.

124304 - Finalised By on Placement is inaccurate

Placement finalisation details now capture the correct user more reliably. This improves audit accuracy where multiple processes run around finalisation.

126431 - Request approval not working on Agreement

The Request Approval action on Agreement records now works as expected. This helps users progress agreement approval without manual follow-up or support intervention.

 

Admin, Integrations and Configuration

100339 - IDEA-01720 - User>Consultant ID Field added to Core

• What: The Consultant ID field is now available in the Core solution.
• Where: User record.
• Why: This supports downstream integrations by giving users a consistent consultant identifier without relying on the longer system GUID.

111447 - Third party iframe hosting - Deactivated third party records should prevent users from being able to access the iframe UI

• What: Child records were active if the parent was deactivated.
• Where: Third Party UI Integrations.
• Why: All children are deactivated with parent to prevent unwanted integrations showing.

111526 - Third party iframe hosting - Regularly sync user identifier records

• What: Update cloudflow to create or delete Third Party User Identifier records for all system users.
• Where: On third party integration feature.
• Why: So that support or customer don't have to create or delete a user identifier manually.

120376 - Add 'Currencies' to Mercury Admin

• What: Added Currencies as site map area within Mercury Admin app.
• Where: Mercury Admin app > Support Area.
• Why: Currencies are now available from Mercury Admin. Admin users can access currency records from the sitemap instead of navigating through advanced find.

Bug Fixes

42261 - Can see Audit History without Data Protection Officer role on a contact

Audit History visibility on the Portal Admin Contact form now follows the expected data protection role controls. This helps protect sensitive contact information and supports stronger compliance.

94535 - Mercury Contact - CONTACT_METHOD_RULES configs are not respected on load

Contact method rules are now respected when Mercury Contact loads. This helps configuration behave consistently and supports cleaner contact communication preferences.

115001 - New Security Role for Excel Online - M34761

Excel Online access now has the required security role support. This helps users open Excel Online without permission errors where they have been granted the appropriate access.

120885 - Permissions error when uploading attachment to appointment activities

Users with the correct permissions can now upload attachments to appointment activities more reliably. This helps teams keep supporting documents with the activity record.

125402 - Custom Ribbon Buttons with security roles aren't evaluating user's team security roles

Custom ribbon button visibility now evaluates relevant team security roles correctly. This helps users access actions granted through team membership, not just direct user roles.

128969 - On demand CV parse triggering duplicate in app notifications

On-demand CV parsing now avoids duplicate in-app notifications for the same CV document. This reduces notification noise and helps consultants focus on the correct review action.

129814 - Change Tracking: PluginAssembly core.dll is updated instead of core.merged.dll

Change tracking now targets the correct core merged plugin assembly instead of updating the wrong assembly. This helps keep deployments cleaner and reduces the risk of unintended plugin changes.

 

Advance Notice of Legacy Components Removal

This information is only relevant to Mercury System Admins of organisations who are using Bespoke customisations.

Occasionally it is necessary for legacy components to be removed in order to improve performance across the Mercury platform. Before the decision is made to remove these, we conduct a full investigation to assess the impact. The majority of customers will not see any impact at all in these components being removed, however a small number of customers who have created bespoke customisations that call on one or more of these components may notice a change.

For a list of permitted customisations please refer to this document.

Please raise a support ticket if you have any questions relating to the removal of a particular component.

The list of components below are scheduled for deletion in Release 2026.4 of Mercury, currently scheduled for approximately October/November 2026.

Component Name              Component Guid               Component Type            Deprecation Version (DNU)        Planned Deletion Version (DEL)      Reason for Deprecation       Dependencies

X DNU [v38] DEL [v39] Enable Mercury - HireAra Button Feature Flag		Setting Definition	38	39	Redundant	N/A
X DNU [v38] DEL [v39] Enable Recruiter View Feature Flag		Setting Definition	38	39	Redundant	N/A
X DNU [v38] DEL [v39] Enable Mercury - Progress Candidate Button Feature Flag		Setting Definition	38	39	Redundant	N/A

 

How to identify dependencies on any Legacy X DNU Components in your environment

To identify whether your Mercury environment has dependencies on a particular X DNU component, please follow the steps below:
 
1. Head to your solution

 

 

2. Find the X DNU components

 

3. Select the component you want to check and select Advanced > Show Dependencies

 

4. Review all components listed in any of the 3 tabs. If no results are shown, then there is no further action for you to take on this component.

 
 

As seen in the example above, this X DNU component is being used by the Contact Form. Therefore, in this example your usual development process should be followed to edit the Contact Form to remove references to the legacy Mercury component.