New features delivered in 25.09

The following features and enhancements were included as part of Data Bridge 25.09.

New Purge and Archive process

This release introduces new CRM data management capabilities to the Data Bridge platform (DATABRIDGE-1632). The new Purge and Archive process is designed to help organizations manage CRM data lifecycle with precision, compliance, and scalability. You can now configure and execute processes for automated or ad hoc purging and archival of both the operational and audit CRM data. This feature supports key use cases such as:

• Regulatory Compliance: Automatically remove and optionally archive CRM data based on configurable criteria.

• Database Growth Management: Reduce CRM database size by purging historical audit logs.

For example, your company policy may be that all activities older than seven years should be archived and removed from your CRM. You can use Data Bridge to generate snapshots of activity records, move them to a secondary storage (archive), and then physically remove (purge) the activities from your CRM database. This functionality can be executed by a batch process that is scheduled to run nightly.

The Purge and Archive feature introduces a new dedicated tab in the Data Processes workspace. Users can use the new Purge and Archive tab to configure, preview, and execute automated data purge and archival workflows.

Creating a new Purge and Archive process

When creating a new Purge and Archive process, you specify the following information.

• You must select Purge Criteria to define filter conditions for identifying purge candidates. Specify whether or not previously soft-deleted records should be included.

• You can optionally add Data Preview Fields to better visualize the data selected by the purge criteria. However, these fields do not affect the purge process.

• The Cascade Associations section allows you to view associated objects or fields affected by the purge process.

Data archiving is optional and disabled by default. You can enable it for the process by selecting the Enable archival of data before purging option on the Archive tab. If archiving is enabled, data is only purged if it was successfully archived. Specify the following information if archiving is enabled:

• Select the Archive Publishing Target to specify how the snapshot of the archived data should be saved.

• Specify the Archive Fields to include as part of the archiving snapshot or apply a Transformation.

• The Archive Preview can be used to better visualize the data that will be archived and purged.

Support for additional subject areas

New subject area configurations were added for the following CRM system audit logs (DATABRIDGE-2032). The following new subject areas have been added:

• Audit Log

• Attribute Audit Log

• Authentication Audit Log

• Integration Log

You can now build CRM Publishing processes and Purge and Archive processes using these subject areas.

Support for relative dates in filters

You can now use relative date values when specifying filtering criteria (DATABRIDGE-2031). For example, you can identify tasks that were created in the past two months. To do this, you can add the Create Date field as a filter. You can then set the operator as greater than, select the month interval, and then set its value as -2. Whenever this process is run, the filter will identify all tasks created within the prior two months of the run date.

Automatic retrieval of the CRM metadata

In order to be able to configure and execute data publishing and data management processes with Data Bridge it is necessary to import the up-to-date CRM metadata (class model) into the product configuration. Previously, this task was accomplished by first exporting the relevant metadata as .json files with the help of the Data Bridge Adapter for CRM, and then importing them into the Data Bridge Server’s configuration. For more information about this process, see the “Exporting NexJ CRM metadata as JSON” and “Creating new subject areas and extending default subject areas” topics in Data Bridge documentation.

In this release, the process was enhanced to automatically retrieve the necessary CRM metaclass information using an API endpoint (DATABRIDGE-2041). While exporting and loading the CRM metadata using .json files is still supported, it is no longer necessary. Data Bridge automatically determines the list of CRM metaclasses for which it requires details. It queries the CRM server using an API at startup. It can also query the server using an API on an ad hoc basis.

For an ad hoc retrieval of CRM metadata, a user with Administrator privileges must navigate to the Global Settings workspace and the Subject Area Configuration tab, and click the Load Metadata button.

To enable this functionality, the following setting in the NexJ Data Bridge System Admin Console must be set appropriately. On the Statistics page, navigate to nexj.bridge > Administration > DataEngine > Model and ensure that the Load CRM Metadata via APIs attribute is set to Y. This is the default value. If this attribute is not set to Y, then Data Bridge will continue to look for the .json metadata files when attempting to load metadata.

Security, integration, and automation upgrades

The NexJ Framework used for Data Bridge 25.09 includes the following upgrades (DATABRIDGE-2079, DATABRIDGE-2062):

• Apache Tomcat has been upgraded to version 9.0.107 (released by the Apache Software Foundation on July 4, 2025) (CRM-4129).

• OpenJDK has been upgraded to version 11.0.27+6 (released April 15, 2025) (CRM-3948).

• Selenium has been upgraded to version 4.33 (released by the Software Freedom Conservancy on May 25, 2025) (CRM-3909).

• The Avro library was upgraded to version 1.11.4+ (released by the Apache Software Foundation on September 22, 2024) (CRM-3861).

• The googlei18n/libphonenumber library has been upgraded to 9.0.5 (released May 07, 2025) (CRM-3853).

• The date.olson.db.js module has been upgraded to version 2025b (released March 22, 2025) (CRM-3486).