ADAM Manager 6.6: discover what’s new in version 2026.2

Version 2026.2 of ADAM Manager (Manager 6.6) introduces several new features relating to media management, document validation and integration with external applications.

It also enhances certain existing features, notably saved searches, data views and applicability management.

New features

1. Support for S1000D 4.0.1 and S1000D 6.0

ADAM Manager is expanding its support for the S1000D standard with the integration of versions 4.0.1 and 6.0, subject to a specific licence.

Two new default configurations are available:

  • S1000D 4.0.1 : CONF_S1000D_401
  • S1000D 6.0 : CONF_S1000D_60

These new configurations enable ADAM Manager to be used with documentation projects based on these versions of the standard.

2. A new approach to managing media with ‘deleted’ status

Version 2026.2 introduces more comprehensive management of the ‘deleted’ status for media items.

It is now possible to manually set an illustration to ‘deleted’ status from within ADAM Manager.

A new import processor, ‘media-last-issue’, also allows this status to be automatically assigned to previous versions of a media item based on its issue number. A dedicated migration is planned to apply this mechanism to older versions of media items present in existing domains.

The ‘Issue type’ field allows you, amongst other things, to assign the ‘Deleted’ status to a media item.

Additional checks

This change is accompanied by new validation checks:

  • Req_Media_LastReleasedReferenced checks that the referenced media file is indeed the latest released version;
  • Req_Media_ExpectedIssueType checks that the referenced media has a valid issue type.

A new configuration filter also allows you to exclude media that have been deleted during a bundle export. Finally, new web services (media-issuetype-deleted) enable you to carry out migration operations with different scopes and track their progress.

3. Accessing external actions from ADAM Manager

ADAM Manager includes a new framework component, external-actions-component,

which allows an external application to be called directly from the DM/PM view.

The application’s URI is defined at system level, and the call takes into account the current domain as well as the selected documents.

The available actions are grouped in a ‘Custom Actions’ context menu, which is automatically disabled when no documents are selected.

The ‘Custom Actions’ menu allows you to trigger an external action from the documents selected in ADAM Manager.

4. Outsource validation to the ADAM Datachecker Standalone Server

Version 2026.2 now allows document validation to be delegated to an external ADAM Datachecker Standalone server.

The validation plan is determined based on the capabilities provided by the Datachecker server. Remote validation can be enabled for the master validation, authoring, import and export bundle components, either as pre- or post-validation.

ACT, CCT and PCT applicability documents can also be sent to the server for validation.

ADAM Manager delegates validation operations to a dedicated instance of ADAM Datachecker Server, and then retrieves the validation results.

In particular, this architecture helps to reduce the processing load on ADAM Manager and to scale validation capabilities to accommodate large CSDBs. The dedicated server handles the validation scheme, including XML Schema/XSD/DTD, BREX, Schematron and XQuery checks.

Improvements to existing features

5. Saved searches and data views

Saved searches from Data Modules (DM) can now be used from the Publication Modules (PM) and export bundle pages.

Data views have also been updated with the addition of the ‘Saved searches’ and ‘Query Filter’ facets in the DM Data views user configuration.

These updates make it easier to reuse configured search criteria in different contexts within ADAM Manager.

6. Developments in applicability management

There have also been several developments relating to applicability models.

New migration web services enable applicability models to be analysed and regenerated according to different scopes: all domains, a specific domain, a control number or a particular configuration.

The behaviour of empty attributes has also changed. When a product or condition attribute is empty in the applicability model, any value for that attribute may be used in a DM, which will then be considered valid.

Similarly, the applicability filter will not take this attribute into account: all its values will be considered applicable.

7. Other functional developments

Version 2026.2 also includes a number of operational adjustments.

TheinWork value in Issue Info is now limited to two digits, i.e. a maximum of 99. If importing an applicability model causes the inWork value of an ACT, PCT or CCT to increase to 100, the import is blocked and an error message is displayed.

Furthermore, it is once again possible to add a company to the _COMMON project.

8. Changes to the Maintainer API

Finally, the Maintainer API has been enhanced with new capabilities relating to:

  • the regeneration of applicability models;
  • the reprocessing of CIR fragments;
  • the migration of media with the ‘deleted’ status;
  • the unlocking of bundles.

Key points

With version 2026.2 (Manager 6.6), ADAM Manager continues to enhance the management of the document lifecycle and S1000D data.

Support for S1000D 4.0.1 and 6.0, the new management of media with ‘deleted’ status, Custom Actions and, above all, the ability to offload validations to the ADAM Datachecker Standalone Server are the main new features of this version.

If you have any questions regarding the availability, configuration or use of these features in your environment, please contact your 4D CONCEPT Project Manager.