Release 2026 Q2

2026.2: IMPORTANT changes in User Interface, Text, etc...

All

• [Design system] Inter is now the default interface font
  • You will now see the Inter font across CM applications, providing a more consistent and modern look and feel throughout the platform.
    
    This update standardises typography so screens and UI elements render more consistently across browsers and operating systems.
• [Metadata] Unified metadata mentions across the platform
  • You now get a more consistent, predictable experience when inserting metadata mentions (for example, metadata, connection pickers, and user pickers) across the platform, including document content, automation rules, etc.
• [Repository] Unify Field Modals Appearance
  • Field-selection modals are now aligned across the wider platform (not just Automations), so users get the same look-and-feel when selecting fields in Filters (PM+PP), Documents tables (PM+PP), Metadata mentions inside content, and Automation.
    
    This reduces UX inconsistencies, helps users learn one pattern they can reuse everywhere, and makes future delivery faster by standardising a single reusable modal pattern.
• Standardized UI Copy Changes (Before -> After)
  • Clear Selected -> Deselect All
    
    (Varied / inconsistent empty-search wording) → No results found for '{query}'
    
    (Varied / inconsistent no-data wording) → No values available
    
    (Section naming inconsistent during search) → Search Results

Notes

• Use cases:
  • 1. Open the exact run details instantly: Start a test run and jump straight to the specific run page via a dedicated URL, instead of searching through a list of runs.
  • 2. Track progress without manual refresh: Keep the run page open and see status updates automatically (auto-refresh) while the run is still executing.
  • 3. Use notifications as an entry point: In Policy Management and the Admin Panel, use the “test run started” notification to navigate directly to run details.
  • 4. Role-aware deep linking: Super admins are routed to the Global Automation page for the specific run, while other users are routed to the relevant automation tab/run page within a template/document where the automation is configured (when multiple locations exist, any valid one is used). 
• To Consider:
  • 1. 🔥 Access-dependent redirects: If a user opens a deep link but does not have access to that automation, they are redirected to the main PM (or PP) page and shown: No Access to Automation
• Tips:
  
  • If you share a run link internally (e.g., with a teammate), it should open the same specific run page (subject to access permissions).

Notes

• Use cases:
  • 1. Workflow Alerts: Automatically email document owners in TO, notify stakeholders in CC, and keep compliance teams in BCC when a policy moves to a new stage.
  • 2 Incident Notifications: Send visible alerts to reviewers while quietly copying audit teams in BCC to monitor remedial actions.
  • 3 Publication Updates: Inform end users in TO and keep managers in CC, while adding risk or legal teams in BCC for oversight. 
• To Consider:
  • 1. TO remains required while CC and BCC are optional, so every automated email must still have at least one main recipient configured.
  • 2. Existing automations keep their current behaviour, as recipients are automatically mapped to the new fields to avoid unexpected changes in who sees what.

Notes

• Use cases:
  • 1. Test Before Rollout: Create a new automation rule and test it against a dummy document first. Once you confirm the results are correct, enable the automation for all documents.
  • 2. 🔥 Fix One-Off Issues: If a critical document didn't process correctly due to format issues, manually trigger the automation rule on just that document instead of re-processing everything.
  • 3. Validate Rule Updates: Modify an existing automation rule (like changing approval routing logic) and run it against a sample document to preview the impact before rolling it out to all future documents.
  • 4. 🔥 Emergency Processing: When a document arrives outside normal processing times or in an unexpected format, manually execute the required automation on that specific document without affecting your automated workflow rules.

Notes

• Use cases:
  • 1. Monitor High-Risk Automations: Filter to only see enabled automations with recent failures so you can prioritise investigation and fixes.
  • 2. Review Ownership and Activity: Quickly identify who created or last modified each automation and how often it runs to support internal reviews.
  • 3. Spot Idle or Overused Automations: Use run counts and last run dates to find automations that are rarely used or trigger very frequently.
  • 4. Prepare Governance Reviews: Export or review the global list to understand where automation is used across your policy library before audits or process changes.
  • 5. Troubleshoot failures faster: Filter to failed runs, open a run, and review the step-by-step log to identify which step failed and why.

Notes

• Use cases:
  • 1. Define global automation rules that safely target many documents (for example, all documents in a specific stage or template set) without needing to duplicate similar rules per template or document.
  • 2. Start from a specific document or template and configure local automation scope that only includes items you are responsible for, while still seeing any additional in-scope items added by central teams (which you cannot accidentally remove).
  • 3. Rely on contextual visibility: quickly see simple automations that affect a given document, template, or stage in-place, and use the global automation page to review and manage all rules that span multiple conditions.
• To Consider:
  • 1. Global scope configuration is only available to Superadmins and Document Managers with Manage Automations authority; Other users with Manage Automation authority can only configure local scope on documents or templates they have explicit access to.
  • 2. Local automation scopes are intentionally simplified: you can include only documents you can access and cannot add extra filters (such as additional stages or metadata), even if they are used in global rules.
  • 3. 🔥 Automation visibility depends on complexity:
    
    • Visibility: Local: simple single-filter rules (by document, template, or stage) appear in context (like inside document or template) and on global automation page.
    
    • Visibility Global: rules with multiple filters or complex logic are only visible and editable from the global automation page.

Notes

• Use cases:
  • 1. Project Pack: Track a fixed set of key project documents in one collection using the Document picker, without relying on complex filters.
  • 2. Modification Inbox: Route only modification documents into a dedicated review workflow using the Modification Type field in automation conditions.
  • 3. Title-Synced Templates: Automatically pull the document Title into the title page or header inside content, so authors do not need to retype it.
  • 4. Targeted Alerts: Send different notifications for originals and modifications by combining the Document picker and Modification Type in automation rules. 
• To Consider:
  • 1. 🔥 The Title field behaves as a single-line text field and its editability follows your metadata screen configuration (including Document settings, Top Navigation, and Move to stage), so review those rules before relying on it inside content.
  • 2. The Document field is a document picker designed for explicitly selecting specific documents rather than replacing your existing metadata-based filters, so use it when you need a fixed, hand-picked list.
  • 3 The Modification Type field is intended for targeting original documents vs modifications in automations and reporting; templates and snippets use the “None” value and will not be treated as originals or modifications.
  • 4 Smart fields inside text fields (like Email Body) such as Document and Portal Document continue to behave as before, still showing links and icons to the latest versions, so you do not need to update existing configurations that rely on them.

Notes

• Use cases:
  • 1. Route by Department: Automatically move documents to the next workflow stage when the Document Owner’s department matches the triggering user’s department.
  • 2. Approval-Based Progression: Advance a document to the next review stage as soon as a specific approval (for example, Global Compliance) is granted, without relying on hidden tracking fields.
  • 3. Metadata-Driven Routing: Apply different actions (like updating fields) based on live document metadata such as region or policy type instead of maintaining separate rules per segment.
  • 4. Role-Specific Actions: Trigger follow-up notifications only for documents where Policy Owner Department is equal to some value.
• To Consider:
  • 1. Dynamic values are resolved at runtime, so rule outcomes depend on the latest document metadata, workflow state, trigger data, and prior action outputs available at the moment the automation runs.
  • 2. Type-safe validation is enforced: you cannot compare incompatible data types (for example, date with user picker)

Notes

• Use cases:
  • 1. Trigger reminder emails when Stage Deadline is approaching and automatically insert the exact deadline and Stage Name into the email subject and body (for example, “Legal Review due on 28/03/2026”).
  • 2. Send escalation emails when Stage Age exceeds a threshold, including how many days the document has been in the current stage so managers can quickly identify bottlenecks.
  • 3. Build automation rules that behave differently based on Stage (e.g., different email templates or recipients for “Drafting”, “Compliance Review”, and “Final Approval”), with Stage Name used as a smart field in the email content.
  • 4. Combine Stage, Stage Age, and Stage Deadline in conditions to drive time-bound alerts and actions, such as assigning tasks or notifying owners when stages are overdue or close to their cut-off date
• To Consider:
  • 1. 🔥 Stage-related fields are not shown on the Portal, so end users will continue to see only the information they need when browsing published documents 

Notes

• Use cases:
  • 1. Automatically align document-level metadata with the nested values of the User or Connection picker. For example, copy Region and Department values from the User Picker, such as Policy Owner, to reduce manual re-entry on the document level.
  • 2. Keep metadata in sync between parent and child documents by copying values from a parent document via Connection Picker fields, helping Document Owners maintain consistent information across a document hierarchy.
  • 3. Support repeatable metadata operations (such as enforcing ownership, region routing, or departmental responsibility) at scale so that Approvers and end users always see accurate, consistent metadata on published documents in the Portal.
• To Consider:
  • 1. Dynamic values are available only from compatible metadata types. For example, for date fields, you can use only other date fields' values, not values from other types. Text fields can use information from any field type.
  • 2. 🔥 When using nested fields, for example, from a User or Connection Pickers, only the first user or document is used to check its nested field value. If there are multiple values in the field, the others are ignored.
    • 2.1. If the selected nested field from a User Picker or Connection Picker is empty at runtime, the Update Metadata action is skipped, and the automation run is marked with an error indicating that the source field value is empty.

Notes

• Use Cases 1. Resize an image more reliably using a dedicated pixel-size input with clearer constraints, so accidental oversized values are prevented. 2. Preview and inspect an image quickly via explicit Image Preview and Image Details options, reducing guesswork about what an image contains. CONSIDER 1. 

Notes

• Use cases:
  • 1. Open approvals directly from email or in‑app notifications and review all changes in a focused mode without learning comparison tools.
  • 2. Use the “Changes” and “Clean” views to switch between a markup view of edits and a clean reading view while keeping approval actions in the same place.
  • 3. Navigate change by change using “Review first change” and next/previous controls to ensure no updates are missed before approving.
  • 4. Check the current workflow stage and due date at the top of the document to prioritise which approvals to complete first. 
• To Consider:
  
  • 1. Who sees the Changes view by default: Reviewers are automatically shown the Changes (diff) view when opening a document for approval. All other roles, including Owners and Editors, see the Clean view by default and can switch to Changes if needed.
  • 2. Approval bar availability: The new bottom approval bar is shown for all document approval scenarios across all roles that have at least one document approval, but it is not shown for paragraph-level approvers.
  • 3. Stage indicator colour: The progress indicator for the active approval stage displays in green when the stage deadline has not been reached, and in red if the stage is overdue.
  • 4. 🔥 Top bar changes for approvers: When approvers open a document, the compare versions button and other non‑essential controls are removed from the top toolbar, replaced with a stage tag that shows the current stage name and due date.
  • 5. View preference is saved per document: Once an approver selects Changes or Clean view, their preference is stored for that specific document. Reloading the page will restore the previously selected view.

Notes

• Use cases:
  • 1. Normalize selected paragraphs to a single font family and size in one action, so long sections match your organization’s formatting rules.
  • 2. Clear inconsistent inline styles from multiple paragraphs at once to clean up imported or legacy content.
  • 3. Apply bulk formatting while automatically skipping locked paragraphs, keeping protected content unchanged.
  • 4. Undo or redo a bulk formatting change in one step if you want to quickly revert or reapply updates across all selected paragraphs.
• To Consider:
  • 1. 🔥 Some formatting options may apply only to part of your selected paragraphs. Check tooltips and selections before applying changes.
  • 2. 🔥 Applying a new font family or size will clear conflicting inline styles in selected paragraphs, which may remove ad‑hoc overrides you previously applied.
  • 3. 🔥 Bulk text style updates will reset conflicting inline formatting (font family, size, bold, italic, underline, colour) to match the defined text style for that paragraph type, similar to how such Paragraph styles (not Character styles) work in Word.
  • 4. 🔥 Re-applying the same text style to already-styled paragraphs will remove inline overrides and revert them back to the canonical style definition for that style.
  • 5. All bulk operations are recorded as single undo/redo steps, so use undo to revert changes across all affected paragraphs at once.
  • 6. 🔥🔥🔥 Bulk formatting (Text Styles, Font Family, Font Size, Clear Formatting) is disabled when more than 100 paragraphs are selected due to performance constraints.
  • 7. 🔥 Some bulk operations still behave in line with earlier editor limitations: Toggle Numbering remains non‑atomic in undo/redo, and lock/unlock in templates cannot be undone or redone.

Notes

• Use cases:
  • 1. While scrolling through a long document, quickly see which section you’re currently reading because the TOC highlights the active heading automatically.
  • 2. After using Find / in-document search and jumping to a match, immediately see the corresponding section highlighted in the TOC for better orientation.
  • 3. After navigating via diff-related flows (where applicable), keep the TOC in sync with your new position so you don’t lose context.
• To Consider:
  • 1. 🔥 The “active heading” is determined based on the primary section currently in view, so the highlighted TOC item may change as soon as you scroll into the next section boundary
• Tips:
  • This is especially useful when you move around the document using shortcuts/search rather than scrolling linearly.

Notes

• Use cases:
  • 1. Collapse sections you’re not working on to keep the TOC short and focused when navigating large documents.
    2. Keep your preferred TOC expansion state while you work, since collapse state is remembered for the session (and shared between PM/PP).
    3. Jump to a section by clicking a heading and immediately orient yourself—your current section is highlighted, and (in editing mode) the cursor is placed at the target heading. 
• To Consider:
  • 1. The “active heading” highlight is designed to follow navigation interactions (e.g., clicking a paragraph/heading).
    
    Depending on context, it may not continuously update just from scrolling alone.