Abstract – Code Removals Dependency check 

As part of Cúram’s ongoing built-in quality and platform health program, we plan to remove a set of long deprecated and unused Artefacts in the Cúram Q4 2026 release. To ensure customer upgrades remain smooth and risk-free, we ask all customers to run the Artefact Dependencies Search Tool (ADST) V1.0.4 using the Cúram Q4 2026 input file and return the resulting report to Product Development for analysis. This quick, self-service scan identifies any custom dependencies on items planned for removal. This process has been used successfully across previous Cúram V8 release cycles. 

Why we are doing this

Removing deprecated features helps maintain a lean, maintainable, high-quality product. Deprecated Artefacts increase technical debt and complexity and are no longer maintained or enhanced. As with earlier cycles (e.g., 8.0 and 8.1), the ADSTbased customer feedback process enables Cúram to:

• Confirm whether any custom code depends on deprecated Artefacts 

• Avoid customer impact during upgrades

• Finalise safe, validated removal lists for a major release 

In scope for Cúram Q4 2026 

The following long deprecated functional areas are planned for removal in Cúram Q4 2026  

1. Cúram Case & Participant Index (CPI)
   Removal of components and dependencies associated with the Cúram Case and Participant Index (CPI).

2. Cúram Client Access
   Deprecation and removal of legacy components related to Cúram Client Access.

3. Deprecated Platform Client Components
   Removal of deprecated platform-level client components (UIM, VIM, and Properties) from older Cúram releases, including version 6.x.

4. Deprecated Cúram Enterprise Modules Components
   Removal of deprecated client components content (UIM, VIM, and Properties) associated with Cúram Enterprise Modules from older versions, including 6.x.

5. Deprecated Cúram HCR, CFSS and CWC Client Components
   Removal of deprecated client components (UIM, VIM, and Properties) from older Cúram releases, including version 6.x

All related Artefacts for these areas have been included in the Cúram Q4 2026 ADST input file. Running the tool will allow customers to easily identify whether their implementation references any of the deprecated components. 

Download the ADST package

The Artefact Dependencies Search Tool package includes: 

• The ADST executable

• The Cúram Q4 2026 input file listing planned removal Artefacts

• A detailed ReadMe with setup and execution instructions

Customers can download the package from the following location: Cúram downloads on Sdrive  

How to run the tool 

1. Download and extract the tool package. Follow the readme instructions.

2. Ensure that Node.js is installed on the machine executing the scan.

3. Update the properties.env file to point to the codebase you wish to scan.

4. Run the tool from the command line using: Npm run scan "Because this release contains a large number of deprecated artefacts in the input_artefacts file and depending on the size of any custom components being scanned, the code removal tool may take some time to complete. A progress bar is provided to show the status of the scan. Please allow the tool to run to completion so that the full report can be generated".

5. Retrieve the generated report from the results folder.

6. Email the report to Cúram Product Manager Angela at: <[email protected]>

What happens next 

Once your ADST report is received:

• Cúram Product Development will analyse any flagged dependencies.

• You will receive guidance on any required changes or follow-up discussions.

• The final removal scope for Cúram Q4 2026 will be confirmed considering customer input.

This validation step is essential to ensure that code removals do not negatively impact your implementation.

Background reference

For historical context on previous removal cycles, customers may review earlier version code removal documentation (e.g., Cúram 8.1 Removals). These references are provided for background only and do not affect the Cúram Q4 2026 removal scope.

Legal disclaimer

Cúram’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at Cúram’s sole discretion. 
Information regarding potential future features is intended to outline general product direction and should not be relied upon when making purchasing decisions. 
This document does not constitute a commitment or legal obligation to deliver any specific material, code, or functionality. Future features and their timing remain at Cúram’s sole discretion.