Release 260 (10.06.2025)

Release 260 introduces MCP (Machine Communication Protocol) integration for ROPA, enabling external tools to create and edit records via a secure token-based API, and extends tag management to organisational units.

New Release

Version: 260
Release Date: 10.06.2025 19:00 CET


Overview

This release adds a new API integration layer that allows authorised external tools to create and manage ROPA records programmatically using IAM tokens. Tag management has been extended to cover organisational units, and several refinements have been made to how responsible persons and last-editor fields are handled during automated interactions.

Contents

  • What's new
  • Improvements
  • Known issues

What's new

External API access for ROPA (MCP integration) [NG-4094]

Authorised external applications can now create and edit ROPA (Record of Processing Activities) entries through a dedicated, token-secured API. This makes it possible to connect third-party tools or internal workflows directly to the DPMS without manual data entry. Access is controlled by IAM tokens, ensuring that only properly credentialled integrations are permitted.

Tag management for organisational units [NG-4348]

Tags can now be assigned to and managed for organisational units, bringing them in line with other object types in the system. This allows compliance teams to classify and filter organisational units using the same tag-based approach already available elsewhere in the platform.

Organisational unit attributes route [NG-4409]

Organisational units now expose a dedicated API route for their attributes, supporting more consistent data retrieval for compliance reporting and integrations.

Improvements

  • ROPA – automated record creation: When a ROPA record is created via an external integration, the responsible person and last-editor fields are now set automatically and correctly, preventing empty or incorrect attribution.
  • IAM token screen: The token edit screen now reflects additional metadata, giving administrators better visibility of token details when reviewing or rotating credentials.
  • Tags – valid-tag filtering: The platform now validates tags before applying them, preventing invalid or deprecated tags from being attached to records created through external tools.

Known issues

No known issues.

Feedback and Support

We value your feedback. If you encounter any issues or have suggestions, please contact our support team:

  • Schedule a Meeting: Via the Help Widget
  • Give Feedback with Screenshots: Via the Feedback Button in the Help Widget
  • Schedule a Support Call: Here
  • Schedule a Technical Support Call: Here

Was this article helpful?