Release 258 (01.06.2025)

Release 258 brings a new Request for Change workflow for shared objects, automatic translation indicators across the platform, and improvements to the login experience and risk settings.

New Release

Version: 258
Release Date: 01.06.2025 19:00 CET


Overview

This release introduces a Request for Change feature that allows users to propose and track modifications to shared records directly within the platform. Alongside this, a new automatic translation indicator system gives users clear visual feedback on the translation status of individual fields across all major modules. Several smaller improvements round out the release, including a pre-filled email field on the login screen and refined risk priority level display.

Contents

  • What's new
  • Improvements
  • Fixes
  • Known issues

What's new

Request for Change (Sharing)

Users working with shared objects can now submit, review, and track Requests for Change without leaving the platform. A dedicated pending-changes panel and a change-history view are available in the sharing area, making it easier to coordinate modifications across organisations.

Translation Status Indicators [NG-4281] [NG-3671] [NG-3670]

Fields that support automatic translation now display a visual indicator showing whether the content is up to date, pending translation, or already translated. This applies to text inputs and rich-text areas throughout ROPA, Risk, Assessments, Vendors, Assets, Documents, TOMs, and other modules. A new translation button makes it straightforward to trigger or review translations field by field.

Automatic Translation for Additional Modules [NG-3859] [NG-3743] [NG-3745]

Automatic translation support has been extended to:

  • Shared objects (sharing workflows)
  • Risk models — asset risk, process risk, and related damage/likelihood scales
  • Assessment templates — questions, options, sections, and result screens
  • International standards — risk priority levels now reflect the selected standard

Change Indicator in Sharing [NG-4254]

A new visual change indicator in the sharing view highlights when linked or shared records have been updated, so recipients can immediately see what has changed.

Improvements

  • Login screen — The email address entered during login is now saved and pre-filled the next time the login page is opened, reducing repetitive data entry.
  • Risk settings — process risk — Damage and likelihood scale tables have been updated with improved layout and editing controls.
  • Asset / Asset Group creation — General creation forms have been refreshed to align with the platform's current design standards.
  • Policies & Documents list — The index view has been updated for better clarity.
  • Company display name — When a company's name is changed, the updated name is now propagated automatically to all consulted/linked objects that reference it.
  • Rich-text editor (Lexical) — Toolbar styling and placeholder behaviour have been refined for a cleaner editing experience.
  • Assessment template builder — The results screen table, variable display, and intermediary-result conditions have received usability improvements.
  • Sharing list — Selection state is now correctly preserved in the sharing list, preventing unexpected resets during editing.

Fixes

  • [NG-3968] Linked elements were not updated correctly when accepting a downloaded change — this has been resolved.
  • [NG-4339] An unnecessary automatic-translation attribute was being added in certain contexts; this has been removed to prevent incorrect behaviour.
  • [NG-4335] The sort order was not reset properly after uploading a file; the step counter is now updated correctly.
  • [NG-4316] Company name changes were not reflected in consulted objects — a migration and runtime fix have been applied.
  • [NG-4359] An empty-field validation error in assessment options caused an unhandled iteration; this is now handled gracefully.
  • Risk settings — An incorrect enum value was causing display issues in risk configuration screens; corrected.
  • Consultation process — Linked consultation-process references were incorrectly included in change-detection logic; they are now excluded.
  • Request By user — When the user who submitted a request was later deleted, the field was left in an inconsistent state; it now falls back gracefully.

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?