Important Notes
- Features marked with a star (*) have to be activated by ITONICS. For more information, please contact your Account- or Customer Success Manager.
- Please make sure to clear your browser cache once the update was processed, in order to avoid cache conflicts.
Take a look at the product update article to see the release highlights at a glance.
API
API
- NUC-16638 – Rating data and social interaction data (followers and likes) can now be retrieved via dedicated API endpoints. Previously returned as part of every standard element response, this data has been separated out to prevent performance issues on elements with high volumes of ratings or engagement. The new endpoints support filtering and pagination, making them more suitable for integration and reporting use cases.
- NUC-17207 – A new optional RBAC-enforced API mode (opt-in) has been implemented which can be enabled to evaluate the application-level permissions of the requesting user for every API request – contrary to the legacy API permission mode (current default) which is controlled via dedicated API-level permissions.
- NUC-17972 – A new PUT API endpoint for Roadmap data has been introduced, enabling automated external systems (e.g., SAP, PPM tools) to push updates directly into ITONICS roadmaps. The endpoint supports updating existing roadmap records, adding new elements to existing roadmaps, updating milestone data, and creating or removing connections including connection type and direction.
- NUC-19181 – The API now supports the OAuth2 Authorization Code Grant flow as a new authentication option. This enables integrations to authenticate users through their existing identity provider, eliminating the need for separate API credentials for users who access ITONICS via SSO. Existing authentication methods are unaffected.
Campaigns
Permissions
- NUC-13724 - The “Inherit submission-level permission” has been extended to cover export actions, ensuring Campaign Managers can export submission data without requiring a separate, manually configured role permission.
- NUC-18275 – The Campaign permission model for Authors and Campaign Managers has been significantly improved by introducing an option to detach the submission permission of Authors from being tied to the original creator. Campaign Managers with the "Inherit submission-level permissions" option enabled now automatically receive full visibility of all custom submission fields, regardless of phase-specific visibility restrictions for their user role. A new "Sync field visibility with creator" option in the Authors field configuration ensures that Authors can see the same submission fields as the original Creator, including a fallback for external submitter scenarios where no Creator role exists. New submission fields now have all phases enabled in their Phase Visibility settings by default, reducing the likelihood of unintentional field access gaps.
Core
Entity Configuration
- NUC-17083 – Administrators can now apply Entity Configuration permissions at the entity type level, enabling a more decentralized and scalable approach to managing platform configuration. This update is fully backward-compatible — existing setups are unaffected until explicitly reconfigured.
- NUC-17928 – The Segment Field Configuration experience has been redesigned to significantly reduce the time and effort required to set up and manage segment hierarchies (before vs. after). Configuration is now unified in a single location under Entity Configuration > Segment Fields, eliminating the need to navigate between separate menus. Segment options are managed through a new split-panel modal with an interactive tree view on the left and an edit form on the right, supporting bulk actions, drag-and-drop reordering within groups, real-time search, and language tab-based translation management — all without requiring page reloads.
Permissions
- NUC-13723 – Excel and PDF export permissions have been moved from the global permission level to the entity-type level, enabling more granular control over who can export data for each entity type. Roles that currently hold the global export permission will automatically retain the equivalent entity-level permissions for all existing entity types. A global administrative override remains available for roles that require export access across all entity types.
Rating Configuration
- NUC-17929 – The Rating Configuration modal has been redesigned to improve usability and reduce visual complexity. Language fields are now managed through a tab-based selector rather than being displayed simultaneously, significantly reducing scrolling. Individual rating range options are collapsed by default, with an at-a-glance completion indicator showing whether required fields for each range are filled per language. The updated design applies consistently across regular ratings, aggregate ratings, and campaign rating configurations.
Integration
Mintel & Kantar Integrations *
- NUC-18712 – The Integration Module has been extended to support Mintel and Kantar as new third-party data providers. Administrators can now configure connections to these providers alongside existing integrations, enabling automated data ingestion from Mintel and Kantar directly into the ITONICS platform.
Note: ITONICS does not provide a license for these tools — a valid subscription with the respective provider is required to use this integration.
- NUC-18713 - Implemented a new Integration Credential Management page to allow for centralized managing of credentials of third-party integrations activated for your ITONICS system. Permitted administrators can add, update, and test integration credentials directly and independently — for example, replacing an expired API key without raising a support request.
Portfolio
Boards
- NUC-15870 – Number fields, calculated fields, and date calculation fields can now be selected as dynamic card labels on the Board view. This allows users to display quantitative data such as NPV, scores, or calculated durations directly on Board cards, making it easier to assess and compare elements at a glance without opening individual detail pages.
Roadmap
Milestones
- NUC-18261 – Milestones on the roadmap visualization can now be colored based on the value of a configured list field (e.g., Approval Status), following the same logic as existing element bar coloring. Administrators can define a default coloring field per milestone type in the roadmap configuration, and users can adjust the active color dimension during a session directly from the roadmap legend. Changes made in the legend apply only to the current session and revert to the default on the next page load.
- NUC-18265 – A new Milestone Lock Mechanism has been introduced to protect finalized milestones from unintended modification. Administrators can designate any milestone field as a "Controlling Field"; once a value is saved in that field, the milestone becomes locked for users without the new "Lock/Unlock milestone on roadmap" permission. Locked milestones display a visual indicator on the roadmap visualization and in the milestone sidebar, and non-permitted users cannot edit, delete, or move them via drag-and-drop. Permitted users retain full edit rights. Lock and unlock events are recorded in the element timeline. The lock is also enforced for updates via Roadmap Excel import and the Roadmap PUT API endpoint.
Roadmap
- NUC-18255 – A new Presentation Mode has been added to the roadmap toolbar, designed for management reporting and stakeholder communication scenarios where full label visibility is critical. In the standard roadmap view, element labels are constrained to the width of their bars, which can result in truncated titles and a dense layout that is practical for day-to-day planning but less suitable for reporting. Presentation Mode addresses this by expanding all element labels to their full text width and automatically distributing elements into separate swimlanes to ensure every title is fully readable at a glance. Standard editing interactions such as drag-and-drop and resizing are disabled in this mode to maintain performance. PNG exports of the roadmap automatically apply the Presentation Mode layout, ensuring exported images reflect the same uncluttered, fully labelled view.
- NUC-18263 - Element titles on the roadmap visualization are now sticky and responsive to the timeline view. When scrolling or adjusting the timeline filter causes an element's start date to move out of view, the title automatically repositions itself to remain anchored to the left edge of the visible portion of the element bar. This eliminates the need to scroll back to identify elements that extend beyond the current view. The behavior applies consistently across the roadmap visualization and Roadmap Snapshots.
SSO/SAML
SAML
- NUC-18697 – The SAML field option mapping configuration has been enhanced with support for flexible, configurable value mapping between source and target option values. Administrators can now define exact, partial, and pattern-based (regex/wildcard) mapping rules, with a clear evaluation priority applied in that order. New target option values can be automatically created when a mapping target does not yet exist, if enabled. All mapping logic is externally configurable without requiring code changes, and existing behavior is fully preserved when no new configuration is provided.
Workflow
Notifications
- NUC-18080 – Workflow element notifications now support new tokens to reference the target element directly within notification message templates, allowing for more contextual and actionable notification content especially when an element is converted from one type to another.
Workflow Triggers
- NUC-15711 – Mandatory field validation for Enrichment workflow triggers is now applied consistently across all trigger combinations. When an Enrichment trigger is combined with other triggers such as Value Change, Notification, or Rating, the workflow step now presents two save options: "Save", which requires all mandatory fields to be completed and fires all associated triggers, and "Save current changes", which allows partial progress to be saved without executing secondary triggers. This prevents workflow actions — such as status changes or notifications — from being fired before the required data has been provided.
