Removal of Legacy Components
The following 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 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 of these components may notice a change.
For a list of permitted customisations please refer to this document.
Going forwards we will give you notice of at least 1 release of any components that are slated for removal, and we encourage you to raise a support ticket if you have any questions relating to the removal of the particular component.
The component listed below is scheduled for deletion in Release v36 of Mercury, currently scheduled for January 2026.
Click here for instructions on how to identify any X DNU dependencies in your environment.
| Component Name | Component Type |
| X DNU [v34] DEL [v36] recruit_/integration/broadbean_v2/scripts/form.js | Web Resource |
How to identify dependencies on Legacy X DNU Components
To identify whether your Mercury environment has dependencies on a particular X DNU component, 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.