Additional information for Mercury System Admins
Removal of legacy components
The following information is only relevant to Mercury System Admins of organisations who are using bespoke customisations.
As part of our work to improve and extend the quality, functionality and performance of our products, it is necessary for legacy components to be removed from our solution from time to time. This process involves thorough testing by our development teams to ensure end users continue to receive a high-quality experience.
While the majority of customers are unaffected by this process, environments that have had particular kinds of bespoke customisation may be required to take action as a result. Specifically, where customisations have been made that depend on components marked as legacy, those customers will need to take action to remove those dependencies themselves.
Mercury maintains guidance for customers that choose to customise their system. Customers that follow these guidelines will typically have lower exposure to the impact of legacy components. For a list of permitted customisations please refer to this document.
NOTE: customisations completed by Mercury’s Consultancy team will adhere to these guidelines and are unlikely to be affected.
Going forwards we will give you notice of at least 2 release cycles of any components that are slated for removal. If you have any questions relating to the removal of the particular component, please log into you Customer Support Portal and raise a request case. Legacy components have their name prefixed with “X DNU” (X - Do Not Use) along with information on when this declaration was made and when the component is scheduled for removal.
Beginning in Mercury v32, the following component is planned for deletion in the Mercury v34 release (currently scheduled for June 2025).
| Component name | Component type |
| X DNU [v32] DEL [v34] Encrypt Password (Contact) | Process (Workflow) |
How to identify dependencies on legacy components (X DNU components)
To identify whether your customised Mercury environment has dependencies on a particular legacy component:
1) Head to your solution:
2) Find legacy components by searching for “X DNU” in the top right corner:
3) Select the component you want to check and select Advanced -> Show Dependencies
4) Check all components listed in any of the 3 tabs:
As seen in the example above this legacy component is a web resource. It is being used by the Contact Form. Consequently, the customer will need to assess the impact of removing references to this component and carry out the work necessary to remove the dependency.
Customers are reminded of the need to undertake customisations responsibly, using recommended best practice including the deployment of managed solutions (not unmanaged) that originate in sandbox environments.