Clio Operate Release 7.12.0

Nikki Chapman
August 24th, 2026
Was this article helpful?

We are pleased to announce that the next point release of Clio Operate, version 7.12.0, is available from 24th August 2026. 

This release includes approximately 23 new or enhanced features and 108 issue and usability fixes. It also includes 15 changes that carry an upgrade impact, which alter existing behaviour or need action in your environment.

If you are planning an upgrade, start with the Upgrade Impact section. It lists everything that changes behaviour you may be relying on today, so you can assess it before you upgrade rather than after.

Using this page. Click any summary item with an arrow to expand it for the full explanation, including links to the relevant articles. Use the dropdown to filter by product area, or type in the search box to narrow the results further.

🌟 New Features & Enhancements

New features and enhancements in version 7.12.0. 

Click summary items with an arrow } to expand for a full explanation, including links to relevant articles. 

 

Use the dropdown to filter by product area, or type in the search box to narrow results further.

Product Areas Summary of feature/enhancement
Click items with an arrow } to expand for a full explanation  		Zendesk Ref Internal Ref
Finance
Phase 1 of a Goods and Services rework. Goods and Services is renamed to Rate Cards and moved entirely into Admin, with a new list-based interface for creating, managing and cloning rate cards. This is Phase 1 of a two-phase rollout.

 

Until release 7.12, this area was called Goods and Services. Rate cards were created in Modeller, and their prices were added separately in Admin, which was slow and did not scale well for firms with many rate cards. From 7.12 the feature is renamed to Rate Cards and all configuration lives in Admin > Finance > Rate Cards. Phase 2 will follow in a later release and will be covered in a separate article.

What's new or changed

  • Goods and Services is renamed to Rate Cards throughout the product.
  • All rate card configuration now lives in Admin > Finance > Rate Cards. It no longer appears in Modeller.
  • A single list view shows all rate cards, with a default view for each rate card type plus an Inactive view. The list opens on Charge Out Rate.
  • Opening a rate card shows its items on the left and the rate card and item details on the right. Selecting an item shows its current rates, including rates that vary by entity.
  • Currency is now set on the rate card, not per item. All items on a rate card share one currency.
  • Item codes generate automatically for every rate card type, not only hourly rates. You can edit the code until you save.
  • A rate card can be cloned from the burger menu, copying the current rates by default.
  • The previous pricing variation toggles have been removed. Variation by entity is always available.
  • A search panel lists existing rate card items, so you can check what exists before creating a new rate card.
 
 

How to use it

See the Rate cards article for how to find, create, manage, clone and delete rate cards. 

 
 

Setup and prerequisites

  • The Rate Cards - Maintain rate cards and items permission, previously Goods & Services - Items Edit, is required to manage rate cards.
  • Currency is chosen per rate card and locked once the first item exists.
  • The unit of measure is fixed to Hours for Charge Out Rate and Internal Cost Rates.
 
 

Upgrade impact

  • The Goods and Services global feature has been removed.
  • Any existing rate card that used mixed currencies is automatically split into one rate card per currency during the upgrade. Affected firms see an informational message and no action is required.
  • Some underlying data is restructured in this rework. Integrations that read Goods and Services data may need updating. Contact Clio Operate support if you rely on such an integration.
 
 

Related Articles:

   130436
List Views
Configurators can now add data composer fields as columns in a list view. The new columns are resolved at query time using a work type chosen by the configurator, removing the need for a supporting workflow to keep list view data current.

 

Until this release, displaying a data composer value on a list view required workflow that wrote the value into a form field, which the list view then read. The workflow had to run frequently to keep the value up to date, which slowed the system and made the configuration harder to maintain.

Configurators can now bind a data composer field directly to a list view column. The value is resolved at query time for each row, so no supporting workflow is required.

Typical uses include showing a calculated count from child work types, displaying address fields such as a postcode separately, or surfacing any other data held in the data composer rather than in a work type attribute.

paragraph

What’s new or changed

  • A new Data composer fields option is available in the Additional Columns section of the Manage List View blade.
  • Once added, the field can be selected as a column in the Columns blade.
  • Data composer columns support the same formatters as attribute columns.
  • Data composer columns are included when an end-user exports the list to Excel or CSV.
 
 

How to use it

For configuration steps, see the Adding data composer fields as columns section in Configuring List Views.

Setup and prerequisites

  • The list view must use the ShareDo Elastic provider.
  • The configurator needs access to Modeller > Forms and Views > List Views.
  • Sorting and filtering are not supported on data composer field columns in this release but are planned for a future release.
 
 

Related Articles:

 13061, 15278, 15434, 11173 116699
Document Management
New File Extension Whitelist global feature centralises file type control, letting configurators define which file extensions can be uploaded or filed across Clio Operate.

 

Previously, the list of supported file types was hardcoded across different areas of the application and could not be changed without a code change. There was no single, centralised control. Clients who needed to support additional formats, such as DICOM for medical imaging, had no way to add them.

The File Extension Whitelist global feature replaces this with a single configurable allowlist. Once configured, the allowlist is enforced consistently across the Outlook Add-in, document repository uploads, drag-and-drop filing, inbound filing, and Virtual Data Rooms.

The allowlist is pre-seeded with a standard set of extensions, including DICOM formats. Extension matching is case-insensitive. Configuration supports standard import and export, allowing the allowlist to be transferred between environments.

Related articles:

 12289, 14311, 11243, 16341, 14101 120508
Document Management
Clio Operate can now change a file's title in an O365 SharePoint repository, independently of the file name. The new ChangeFileTitles capability surfaces wherever the Repository Explorer is used.

 

SharePoint files have two distinct properties: a file name and a title. Until now, Clio Operate could rename only the file name. The new ChangeFileTitles capability adds title-change support for the O365 SharePoint provider, in every Repository Explorer location: the matter DMS, the document template DMS, and any other widget or blade that hosts the Repository Explorer.

 

Renaming the title does not change the file name. Renaming the file name does not change the title. When both RenameFiles and ChangeFileTitles are enabled on the repository, a single Rename action opens a combined dialogue with both fields, so users can edit either or both in one operation.

What's new or changed

  • A new ChangeFileTitles capability is supported by the O365 SharePoint repository provider.
  • When the capability is enabled on a repository, users see a Change Title action in the Repository Explorer ribbon and burger menu.
  • When the Repository Explorer's Title column is visible, clicking a title cell starts an inline edit, in the same way as inline file-name edits.
  • When both RenameFiles and ChangeFileTitles are enabled on the repository, the existing Rename action opens a combined Rename modal with File name (editable base name, extension preserved) and Title fields.
  • Title and file name are persisted independently. Editing one does not affect the other.
 
 

How to use it

Your administrator enables ChangeFileTitles on the relevant repository. Once enabled, the new actions appear in any Repository Explorer surface. To make the Title column available for inline edits, add it to the DMS widget through Portal designer. See the article Enable title changes for SharePoint documents for full details.
Setup and prerequisites

  • The capability is provider-specific. Only the O365 SharePoint repository provider supports it. Other providers are unaffected.
  • Configurators can hide the Change Title UI in a specific DMS widget by setting showChangeTitle to false in the widget's Advanced configuration. The option defaults to true.
 
 

Upgrade impact

Existing repositories are not changed automatically. The new UI appears only on repositories where your administrator has enabled the ChangeFileTitles capability. Repositories without it retain the existing rename-only behaviour. No data migration is required.

 
 

Related  Articles:

   137829
Documents
New global feature lets configurators control whether Office documents open in the desktop application or in the browser when accessed from SharePoint document repositories.

 

When users opened an Office document from Clio Operate, the product previously defaulted to opening it in the browser (Word Online or the equivalent). Many users prefer the full desktop application for formatting fidelity and a richer editing experience, and were using Open in app manually each time.


The new global feature gives configurators a single switch to set the preferred behaviour for the whole environment. The setting is respected by Related Documents widgets, the document open that follows Prepare Document, and the Edit/Open action on the Document Preview panel and widget.


This applies to SharePoint document repositories. Other DMS providers are not affected.

What's new or changed

  • A new global feature, SharePoint (Advanced) with a toggle Open in application by default, is available in Modeller > Global features.
  • The setting is respected by the Related Documents widgets (DMS, Standard, Flat, and Search variants).
  • The setting is respected by the on-generated open that follows Prepare Document.
  • The setting is respected by the Edit/Open button on the Document Preview panel and widget.
  • When the feature is enabled, Clio Operate now forces repository.matter-documents.type.expandMetadataFields to true on the SharePoint repository. This had to be set manually previously.
 
 

How to use it

Enable the feature in Modeller > Global features. See the Global Features article SharePoint (Advanced) for the full configuration steps.

Setup and prerequisites

  • The feature applies to SharePoint document repositories. Other DMS providers are unaffected.
  • Configurators need access to Modeller > Global features to enable the toggle.
  • Users still see an Open in app option in the UI. The global feature changes only the default action.
 
 

⚠️ Upgrade Impact

After upgrading, the global feature is off by default, so existing open-in-browser behaviour is preserved. Once enabled, Clio Operate overrides the visible value of the expand-metadata-fields setting on SharePoint repositories and treats it as true. The change is silent. No configurator action is required.

 
 

Related  Articles:

 13834, 14056, 12126, 16415  121069
Email / SMS Templates
Email document templates now support role-based recipient restrictions on the CC field, and SMS document templates now support role-based recipient restrictions on the To field. Both behave in the same way as the existing role restriction on Email To.

 

Previously, only the To field on Email document templates supported role-based recipient restrictions configured at the template level. CC on Emails and the recipient field on SMS templates accepted only free typed entry, with no way for implementers to constrain who could be addressed. Now you can configure role restrictions on Email CC and on the SMS recipient field. This brings recipient configuration in line across all three Email and SMS recipient fields, while keeping BCC unrestricted on a per-message basis.

What's new and changed

  • New role-based recipient restriction on the Email CC field at the template level. Configure one or more roles in the Question Sets section of an email template to restrict CC to participants holding those roles.
  • New role-based recipient restriction on the SMS To field at the template level. Configure one or more roles in the Question Sets section of an SMS template to restrict the recipient.
  • Where no roles are configured for a field, the field accepts free typed entry. This applies to Email To, Email CC, and SMS To.
  • BCC on Email is unchanged. BCC always accepts free typed entry and cannot be restricted by role.
  • Behaviour at email or SMS creation: where a single participant matches the configured role, the field populates automatically. Where multiple participants match, the participant picker opens filtered to the configured roles.
  • Role sourcing on the work type takes precedence over the role chosen in the template.
 
 

How to use it

From the menu, select Open Document Admin. In the left-hand panel, select Document Templates > Email Templates or Document Templates > SMS Templates. Open the template you want to configure, navigate to the Question Sets section, and configure roles for the To, CC (Email), or To (SMS) field.
For the full configuration walkthrough, see Preparing a new email template and Preparing a new SMS template.

 
 

⚠️ Upgrade Impact

Existing Email and SMS templates continue to behave as before. Templates with no CC or SMS To role restrictions configured will continue to accept free typed entry on those fields. No action is required to preserve existing behaviour. To use the new restrictions, edit the template's Question Sets and configure the relevant roles.

 
 

Related Articles:

 13556 103933
ODS
Organisational Hierarchy Roles in Participant Roles have been deprecated. These have been replaced with a new Job Roles feature. 

 

Job Roles do everything the old roles did — and quite a bit more.

The biggest improvement is that users now have a role history. Rather than a single “current role” on their profile, you can record each role a user has held and when it started. This matters particularly for time recording and fees: the system can now look up what role a user held at the time a time entry was created, not just what role they hold today.

Job Roles are organised into Job Families (for example, Legal, HR, Exec), which makes them easier to browse and manage, especially in larger environments.

What's New

Job Roles admin page

There’s a new dedicated page for managing Job Roles, found here: Admin > Users > Job Roles. 

From here you can:

  • Create, edit, and disable Job Roles
  • Organise roles into Job Families
  • Delete roles (subject to usage checks)

The page uses Clio Operate’s standard list view, so you can filter by active status and configure the view as needed.

Job Families are groupings of related roles. When assigning a role to a user, the dropdown is structured by Family, making it much easier to find the right role in environments with a large number of roles.

 
 

Role assignment and history for users

Each user now has a job role history rather than a single current role. When you assign a new role to a user, the previous role is automatically given an end date. The full history is visible on the user’s profile.

You can also edit the most recent role assignment to correct mistakes, though a role cannot be changed if it has already been used in a time to fees calculation.

 
 

User type settings

You can now configure whether a Job Role is required for users of a given user type. This is set on the user type configuration, in a new “Job Roles” section above Team Membership.

By default, this is set to on for new user types. The upgrade migration handles existing user types automatically.

 
 

User Advisor

The user profile advisory panel has been updated and renamed the User Advisor. It now flags users who don’t have a Job Role assigned where one is required. Advisories are grouped by type, so permission issues and job role issues are displayed separately.

 
 

Import and export

Job Roles and Job Families can be exported and imported between environments in the standard way. Allocation Rules, Business Rules, and other items that reference a Job Role will include that Job Role as a dependency on export.

 
 
 
 

What's been Deprecated

Organisational Hierarchy setting has been removed from Participant Roles. Because organisational roles have been removed, there is no other usage of participant role other than to be used on a Worktype and therefore the Sharedo Role setting has also been removed.

 
 

Where Job Roles Are Used

Job Roles feed into several other parts of the system. Here’s a summary of what’s changed in each area.

Area What’s changed
Time to Fees The hourly rate lookup now uses the role the user held at the time the timer started, not their current role. This means time recordings that span a role change are calculated correctly.
Rate Cards / Internal Costs Rate cards and internal costs are now configured against Job Roles. Any that were previously linked to Organisational Hierarchy Roles are automatically migrated.
Fee Templates Fee templates can now specify a Job Role. Existing fee templates that referenced Organisational Hierarchy Roles are updated on upgrade.
Allocation Rules Round Robin and Least Busy Team allocation rule types now use Job Roles. The dropdown has been updated accordingly.
Goods & Services Role selection in Goods & Services items now uses the Job Role list.
Business Rules User match cards can now be configured against a Job Role. The system checks whether the user’s current role matches.
Security Barriers Security barriers can be configured against Job Roles, controlling whether a user can be placed into a participant role.
Data Composer The User context in Data Composer has been extended with Job Role and Job Role Assignments (as an array). The old primary team role tag has been removed.
SCIM A default Job Role can be configured for users added via SCIM. Users provisioned through SCIM will be assigned this role automatically.
Public API New endpoints are available for managing Job Roles and Job Families. The User API has been updated to support Job Role assignment. See the API documentation for details.
Reporting The DIM_Person, DIM_PersonTeam, and DIM_TimeEntry reporting tables now display the user’s Job Role system name.
 
 

Set Up Job Roles

For full details and instructions on how to setup and configure the job roles feature see Everything you need to know about Job Roles, the instructions are on the Configure Job Roles tab.

 

 
 

⚠️ Upgrade Impact

If you are upgrading an existing environment, read this section carefully. The migration is automatic, but there are a few things worth being aware of. If you have not used Organisation Hierarchy Roles, the upgrade will have not impact - the new Job Roles feature will just be available.

 

What the migration does

The upgrade migration handles the transition from Organisational Hierarchy Roles to Job Roles automatically via a SQL migration. Here’s what it does:

  • Existing Organisational Hierarchy Roles are converted to Job Roles.
  • Where roles were organised into categories, equivalent Job Families are created.
  • Users are assigned a Job Role based on their existing role data. The migration uses the role set for a user’s primary team, or if no primary team role exists the role from the team with the most members.
  • Email signature global feature config is updated from ods.user.primaryTeam.role.name to ods.user.activeRole.roleType.name
  • Rate cards and internal costs that referenced Organisational Hierarchy Roles are updated to point to the equivalent Job Role.
  • Fee templates, allocation rules, and business rules are updated in the same way.
  • All references to Organisational Hierarchy Roles are removed from the application UI.
 
 

Users with no role after migration

Some users may not have a role assigned after migration, for example, if their existing data was ambiguous or incomplete. These users will be flagged by the User Advisor on the admin Users page, making them easy to identify and fix.

 
 

Data Composer and calculated fields

The old primary team role tags have been removed from Data Composer and calculated fields. If your environment uses these tags in Data Composer queries or document templates, a Modeller Upgrade Assistant is available to help identify and update affected items. Check the Modeller Assistant after upgrading.

 
 

Allocation Rules and Business Rules

If you have allocation rules or business rules that reference roles, check that they’re pointing to the correct Job Role after the upgrade. The system migrates these automatically, but it’s worth verifying.

 
 

Data loading

The primaryRoleSystemName field has been removed from the data loading schema. Any data loading configurations that reference this field will need to be updated.

 
 

Participant Types

References to Organisational Hierarchy Roles have been removed from Participant Types. If your configuration previously used these references, they will no longer appear. Review your participant type configurations after upgrading.

 
 
 
 

Related articles:

 9469 126630
ODS / Participants
Banking detail permissions have been updated. The single read permission has been replaced with two granular permissions: readFull and readPartial.  This provides more precise control over who can view sensitive banking information.

 

The banking details feature allows banking information to be stored and managed against ODS entities: individuals, organisations and teams. This update introduces permission-based access control for banking details. Administrators can now grant users either full or partial access, ensuring that sensitive financial data is only visible to those who need it, and only to the level of detail they require.

 

For example, a finance administrator may be granted full access to view account numbers and sort codes in full, while a team leader is granted partial access and sees those fields masked.

What's new or changed

  • The single bankdetails.read permission has been replaced with two new permissions: readFull and readPartial.
    • readFull grants access to view banking details with no masking or redaction.
    • readPartial grants access to view banking details with sensitive fields (sort code, account number, BIC/SWIFT) partially masked.
  • Users with no read permission can no longer see the banking details section. The button and navigation bar are hidden for those users.
  • Viewing fully unencrypted banking details (readFull) now generates an audit event on the associated entity’s audit log. This applies to persons, organisations and teams.
  • API integrations that previously accessed banking details using the DataComposer overridePermissions bypass must now hold an explicit readFull or readPartial permission.
 
 

⚠️ Upgrade Impact

Action required for all upgrades.

  • The bankdetails.read permission no longer exists. Users who previously had the read permission, will be migrated to the new readPartial permission. If they require the full read permission readFull, then it will need to be explicitly granted by an admin. 
  • Users with no banking detail permission will no longer see the banking details section after upgrading, even if the navigation was previously enabled for them.
  • API integrations using the DataComposer overridePermissions bypass will no longer receive banking detail data after upgrading unless they are explicitly granted readFull or readPartial. Sensitive fields will return null rather than a 403 error when no permission is held. API integrations must be updated to include the appropriate permission before the upgrade is applied.
  • Review all existing integrations that consume banking detail data and assign the appropriate permission before the upgrade goes live.
 
 

Related Articles:

   137003
Outlook Addin

 

The Outlook Add-in now automatically detects when an email has already been filed and shows you who filed it and when, preventing the same email from being filed multiple times by different people.

In legal practices, emails are often sent to multiple people. When this happens, different fee earners can independently attempt to file the same email against a matter using the Outlook Add-in. This results in duplicate entries on the work item, chronology problems, and potential workflow issues.

 

Clio Operate now addresses this by checking the filing status of each email in real time. If an email has already been filed, the add-in tells you immediately, before you take any action.

 

When you select an email in the Outlook Add-in, the add-in checks whether it has already been filed against a work item.

  • If it has already been filed, an information bar appears at the top of the add-in panel. It shows the date and time of filing, and the name of the person who filed it (if that person is not you).
  • If more than one user attempts to file the same email at the same time, the add-in may initially show it as unfiled. When you try to file it, the add-in checks the current status. If it has since been filed, the information bar displays and the filing is stopped. This prevents duplicates even when two people act at the same time.

The information bar is advisory. You can still file the email again if you need to. Select the work item and proceed as normal. Use this option with care, as re-filing creates a second copy of the email on the work item. 

 

   131709
Participants
Improvements made to Modeller > Participant Roles.

What's changed

  • Participant Roles is now a list view rather than a client paging control.
  • You can no longer edit Sharedo Ownership from Participant Roles - the option has been removed from the Actions menu and the Nav bar. Instead this is now only managed via the work type. You must configure a work type participant role on the parent work type, you cannot do it on inherited participant roles. Modeller > Work Types > Edit work type > Participant Roles > Click the arrow at the end of the row or Actions > Configure
  • Due to the new Job Roles feature, the Organisational Hierarchy setting has been removed. Because organisational roles have been removed, there is no other usage of participant role other than to be used on a Worktype and therefore the Sharedo Role setting has also been removed.
  • The details within the ODS Settings Aspect have been moved onto the main Participant Roles blade. Previously when creating a participant role you had to create the participant then reopen the blade to set the ODS types, which meant they were easily missed.
  • In Modeller > Work Types > Edit work type > Participant Roles list view on the Actions menu there is an option to set inactive/set active the role on that work type. This can be done for all participant roles on a work type including inherited ones, making it a quick way to deactivate roles that are no longer needed on that work type.
 
 

Example Edit Participant Blade

 
 

⚠️ Upgrade Impact

This change removes one route to Participant role configuration in Work Types. Alert your configurators to this. An alternative route already exists, but they may be used to the old path. KB articles have been updated to reflect this.

You can no longer edit Sharedo Ownership from Participant Roles - the option has been removed from the Actions menu and the Nav bar. Instead this is now only managed via the work type. You must configure a work type participant role on the parent work type, you cannot do it on inherited participant roles. Modeller > Work Types > Edit work type > Participant

 
 

Related Articles:

  

108471

126493

108471
Participants The Key Contacts aspect has been deprecated and was causing errors.  It can no longer be added to a Participant Type on the ODS Aspects blade.   129925

Time Recording

 
Maximum narrative length added to Time Recording Global Features settings.

 

The Maximum narrative length field is used to set a character limit on the narrative field in time recording. Leave it blank to apply no limit.

Where to find it: Modeller > Global Features > Case > Time Recording 

  • When a value is set, users cannot submit a narrative that exceeds the limit. If a user enters more characters than the maximum allows, the narrative field displays how many characters are over the limit.
  • Auto-generated narratives that exceed the limit are capped automatically.
  • If the field is left blank, no maximum applies.

The maximum must be greater than the minimum narrative length. If the minimum is not set, it is treated as 0, so any value greater than 0 is valid.

The message displayed in the narrative field depends on how minimum and maximum lengths are configured.

Configuration Message displayed
Minimum only

Must be at least X characters long 

This message disappears once the user has entered enough characters to meet the minimum, consistent with existing behaviour.
Minimum and maximum Must be between X and Y characters long
Maximum only No message; over-limit count shown if exceeded
Neither set No message

Related Articles:

 11308, 13449 128740

Time Recording

 
New Extended Narrative time recording blade layout.

 

A new time recording blade layout has been introduced to support firms where lawyers frequently need to write lengthy, detailed time narratives - such as those used in statute bills or detailed cost exports.

Previously, the standard time recording blade offered limited space for narrative text, requiring users to scroll to read or edit longer entries. The new Extended Narrative blade presents a wider, document-style layout with independent scroll bars on each side of the blade, making it easier to write, read, and review multi-paragraph narratives without excessive scrolling.

Configure the blade layout

Where to find it: Modeller > Global Features > Time Recording > Time Recording Blade Layout

This is a dropdown with two options:

  • Standard - the existing time recording blade (default)
  • Extended Narrative - the new document-style blade

The default value is Standard. This setting can be changed at any time to apply the selected layout across all time recording entries.

 
 

Extended Narrative blade behaviour

When the Extended Narrative layout is selected, when a user opens a manual time entry via the clock icon ribbon button the Extended Narrative blade displays in place of the standard blade. The narrative box is free text and auto-expands to accommodate the content as the user types.

Example Standard blade layout

Example Extended Narrative blade layout

 

 
 

Related Articles:

   129739
Workflow
Workflows now route across five dedicated processing streams based on priority, reducing queue contention and improving processing speed for interactive, user-facing workflows.

 

Previously, all workflow triggers and execution events shared a single processing queue. Under load, interactive workflows, such as those triggered directly from a menu by a user, could wait behind slow background or scheduled tasks, causing unpredictable delays.

 

Workflow prioritisation and stream selection replaces the single queue with five dedicated processing streams, each configured for its workload type. The system automatically assigns each workflow to the appropriate stream based on its trigger type and how it is used. Configurators can review and override these assignments where needed.

What's New or Changed

  • Five priority streams are now available.
  • Workflows are automatically assigned to a stream based on how they are triggered. The system evaluates factors such as whether the workflow is called from a menu, a bulk action, a data table upload, or a maintenance plan.
Priority Name Description
1 Interactive processing workflows Workflows that generate tasks and which users interact with in a single process flow on a single case.
2 High priority workflows Workflows where users may be interacting with several activities on a single case.
3 Normal priority workflows Default queue for all existing workflows and new workflows where no rule matches.
4 Low priority workflows Workflows with no direct user involvement, such as those waiting on the next stage in a case or task.
5 Scheduled processing Workflows where large numbers of events are collected but no immediate processing is required.
  • Default priorities are set in the Execution Engine global feature.
  • Configurators can manually override the assigned priority on any workflow via the visual workflow configuration screen on the Plan tab. 
  • Workflow priority is now available as a column in the workflow list view. The column supports sorting and filtering.
  • On upgrade, the five streams are created automatically. The existing single queue migrates to Priority 3 and retains its current node and role configuration. All other streams receive two roles.
 
 

How to Use it

  • In most cases no action is needed. Priorities are assigned automatically on upgrade and recalculated whenever a workflow or its trigger is changed.
  • To override a workflow's priority, you need access to workflow configuration. Visual workflow editor > properties > plan tab. 


    Priority overrides are set per workflow and apply to all instances of that workflow. 
  • To review priorities across all workflows, the Priority column is available in the workflow list view. 

⇢ See Workflow prioritisation and stream selection for full guidance.

 
 

⚠️ Upgrade Impact

On upgrade, five new streams are created:

  • {environment}-execution-engine-processing-1
  • {environment}-execution-engine-processing-2
  • {environment}-execution-engine-processing-3
  • {environment}-execution-engine-processing-4
  • {environment}-execution-engine-processing-5

The existing {environment}-execution-engine-processing role is renamed to -3. Priority 3 retains its current node and role count. Streams 1, 2, 4, and 5 each receive two roles. No manual migration steps are required. Be aware that if there is an existing stream, as this change creates new streams, any events sat on the old stream will remain and be processed there. That stream and the role will be deleted by the Clio Operate team once all processing is complete.

 

The prefix for the execution priority streams and the default priorities are set in the Execution Engine global feature. 

 
 

Related Articles:

 

   132222
Document Management
New File Naming Rules global feature lets configurators control how file names are generated across Clio Operate, with configurable rules for invalid characters, whitespace, collision-avoidance suffixes and length, plus a global compliance policy that acts as a safety net.

 

File naming is now a first-class, configurable concept. A central rules engine replaces the previous mix of hardcoded tags and ad-hoc methods, and every file-save scenario uses it: document generation, email and post PDF conversion and bundling, document split and document bundling, inbound and outbound email archiving, legal form uploads and electronic signature uploads.

Rules can be selected directly or surfaced as tags in a file name template, and constraints are resolved per destination repository, so each backend DMS's reserved characters are honoured.

What's new or changed

  • A new File Naming feature is available in Modeller > Global features, under Document Management.
  • Four rules are seeded by default: _title, _titleAsFilename, _titleAsFilenameWithoutTimestamp and _sanitised. _titleAsFilename is the default.
  • Each rule controls whitespace, invalid characters, collision suffixes and length, and is aware of the target repository’s constraints.
  • A compliance policy acts as a final safety net on the fully composed file name.
  • Rules are available as tags in document templates (Output Title, Output File Name, PDF File Name), legal forms, electronic signature and inbound email attachments.
  • A File Naming Rule dropdown has been added to the Document Bundling feature and the email archive channel configuration.
  • A Test Configuration debug blade lets you preview how a rule transforms a name, and rule deletion is usage-checked.
 
 

How to use it

See the File naming rules article for how to configure rules, the compliance policy, and how each area uses them. 

 
 

Setup and prerequisites

  • The feature is in Modeller > Global features > File Naming.
  • You need the core.adminAccess or core.modeller permission to change the configuration.
  • Set a default rule; consumers fall back to it when no specific rule is selected.
 
 

Upgrade impact

  • Legacy tokens are migrated automatically, with no manual configuration changes required: [OriginalName] becomes [_title] and [OriginalNameWithTimestamp] becomes [_titleAsFilename] on electronic signature configurations; [attachmentFileName] becomes [_title] on inbound email attachments.
  • Email archive channels without a rule are seeded with _sanitised; document bundling without a rule is seeded with _titleAsFilename, preserving prior behaviour.
  • Compliance and repository-aware constraints are now enforced where they were not before, so some generated file names may differ, for example invalid characters removed or length enforced. Review any custom file name templates after upgrading.
  • The migration is idempotent and safe to re-run.
 
 

Related Articles:

   135530
Document Management
Document bundle navigation improvements. Table of Contents links and the PDF outline now go to the correct document and scroll it into a readable position, and the navigable index and PDF outline are enabled by default.

 

Clicking a Table of Contents entry or a sidebar bookmark in a generated bundle now scrolls the destination so the document's header sits just below the top of the viewport, instead of landing mid-page. Destinations also resolve correctly when the Table of Contents itself spans more than one page.

The Enable Outline and Enable Navigable Index options now default to On for new configurations (existing saved settings are preserved), and the "Experimental features" banner has been removed from the Document Bundling configuration.

 14329 92599
Document Management
Bundle separator templates now use Data Composer. Bundle separator templates now draw their data from Data Composer, and a Modeller Assistant job migrates existing templates. This modernises how bundle title pages, section headers and document separators are populated.

 

Bundle separator templates (title pages, section headers and document separators) now read their data from Data Composer rather than the legacy tag libraries, and resolve against the correct work item context. Bundle details such as name, sections and documents can also be used in business rules and phase guards, bundle fields are available in the Word Add-in tag browser, and bundles containing empty sections now generate without error.

A Modeller Assistant job scans existing bundle templates for legacy tag names and context workarounds and offers one-click migration. See the Upgrade Impact tab.

Until release 7.12, bundle separator templates used a legacy bundling tag library, and in some cases read data from the bundle task rather than the matter, which required workaround tags. From 7.12 separator templates use Data Composer and resolve matter data directly.

What's new or changed

  • Bundle separator templates read their data from Data Composer.
  • Matter details resolve from the matter itself, so workaround navigation paths are no longer needed.
  • Bundle fields (bundle name, current section name, previous and next document name, page range and page count) are available in the tag browser and in the Word Add-in.
  • Bundle details are available in Data Composer on the bundle work item, for use in business rules and phase guards.
  • A bundle with an empty section now generates without error.
 
 

How to use it

See the Document Bundling Global Feature article for how to author separator templates with Data Composer fields. 

 
 

Setup and prerequisites

  • Separator templates are authored in Bundle Templates, in Documents Admin, and in the Word Add-in.
  • No new permission is required.
 
 

Upgrade impact

  • Legacy bundling tags are retired. Run the Bundle Template Migration job in Modeller Assistant to update existing separator templates. Until a template is migrated, its affected tags will not populate.
  • Old workaround navigation paths that read matter data through the bundle task now return a blank value. Replace them with the direct Data Composer fields, which the migration job can do for you.
  • The legacy document-bundling tag loaders are removed as part of the upgrade.
 
 

Related Articles:

   95928
Search
Quick search now keeps your search text when you change search type, rather than clearing it.

 

When you switch the quick search scope, the text you have already typed is kept and the search box is re-focused, so you no longer have to retype. Results from the previous scope are cleared and the search re-runs as you continue typing.

   111998
List Views
List view type filters now include a search box for finding work types quickly.

 

The work-type column filter dropdown on list views now has a search box at the top. Typing filters the type tree to matching branches (case-insensitive), with keyboard navigation, a "no matches" message, and the search text preserved when you reopen the dropdown.

   123884
List Views
List views now show a filter chip that makes it obvious when filters are applied and lets you clear them in one click.

 

When one or more filters are active, the list view toolbar shows a filter chip with a live count of active filters. Click the chip to open or close the filter panel (or the edit-filters blade on older list views), and click the × to clear all filters in a single action. The plain funnel icon returns when no filters are applied.

   140239
Emails
The "sending outside your organisation" warning on the outbound email blade is now more compact.

 

The external-recipient warning on the outbound email blade has been condensed, with a smaller font and reduced padding, so it takes up less space in focus mode. The warning is switched on through the Outbound Email global feature.

   137309
Data Loading
The user data loader now supports Job Role assignment.

 

The user data loader can now assign a Job Role when loading users. Two columns, jobRoleSystemName and jobRoleStartDate, have been added to the users staging table (source schema version 1.0.8), with validation that the job role exists and that the start date is not in the future. If no start date is supplied, the current date is used; if no job role is supplied, the date is ignored.

   140039
Vincent
New icons added to core for use with the Vincent plugin.

 

Three additional icons (keyboard-brightness, and the solid and regular variants of file-magnifying-glass) are now available in core and can be referenced in any icon field, for example in the Portal Editor. They are provided primarily for use with the Vincent plugin.

   139157
 
 

✅ Issues Resolved

Issues resolved in version 7.12.0. Items raised via Zendesk include the ticket reference number.

Use the dropdown to filter by product area, or type in the search box to narrow results further.

Product Area ❌ Issue ✅ Resolution Zendesk Ref Internal Ref
API
PUT /api/v2/public/people/externalReference/{externalRef} endpoint returns error and successful status incorrectly

 
Fixed an issue where the PUT /api/v2/public/people/externalReference/{externalRef} endpoint returned 500 Internal Server Error when more than one person shared the same external reference, and a misleading 200 OK when no person matched the external reference at all. The endpoint now returns 404 Not Found when no person matches, and a 400 response with a clear message including the duplicate count when multiple people share the same external reference. The same behaviour now applies to the v1 version of the endpoint.
   136517
API
Unable to add user participant when creating workItem

 
Fixed an issue where adding a user participant to a work item through the public API failed with a 500 Internal Server Error when the role was configured for users only, because the user was incorrectly treated as a person. Users can now be added to user-only roles through the public API, and mismatched participant types are rejected with an appropriate error message.
   140052
Aspects Editor
Save actually Saves AND Closes. Need dedicated Save and Close button.

 
Fixed the Aspects Editor so that the Save button no longer automatically closes the blade. A dedicated Save & Close button has been added, allowing configurators to save their changes and continue editing without having to reopen the editor each time.
   136493
Audit
Uploading Documents to a Work Item does not create an Audit Record

 
Fixed an issue where uploading a document to a Work Item did not generate an audit record. Document uploads are now captured in the audit log, so administrators can see who uploaded a document and when.
   117132
Data Composer
'a field has already been defined' error occurs intermittently and requires app restart reload to fix

 
Fixed an intermittent issue in Data Composer where, under heavy concurrent activity at start-up, users would see errors such as 'a field has already been defined' that previously only cleared after an application restart. Data Composer now recovers from these conditions on its own, so users no longer need to wait for a restart to resolve the issue.
 15211, 14511, 15895 120651
Data Composer
Calculated fields is not displayed in browser

 
Fixed an issue where calculated fields defined against nested work item paths, for example, workitem.invoiceDetails, did not appear in the Data Composer browser. Calculated fields at every level now display and resolve correctly when queried.
 
⚠️ Upgrade Impact: this fix changes how Chronology POI work type references behave in Data Composer; previously the fully materialised related work item was available for selection, whereas now only basic work item information is exposed and a specific work type must be picked to access aspects, roles or calculated fields, so any clients using these fields will need to update their configuration.
 12465 133185
Data Loading
FormAspects dataloader is associating aspect data to the participant role ID instead of the participant ID so this data is not loaded.

 
Fixed an issue where participant form data loaded via ETL was stored against the wrong participant record, so the values did not appear on the form in the user interface. Participant form data now loads against the correct participant and is visible on the relevant forms once the load completes.
   139827
Data Loading
Control characters cause Nancy model binding to fail

 
Fixed an issue where data loads failed when reference values or other text fields in the source data contained stray non-printable characters. Data loads now tolerate these characters and complete successfully.
   137167
Data Loading
Proceeding keydates do not have correct sharedo relationships

 
Fixed an issue in data loading where key dates added to a proceeding were not linked back to the parent matter, statement of work or contract because the proceeding was not being recorded as a child of its matter. Proceedings now sit correctly under their parent matter on load, so key dates added to a proceeding resolve through to the matter and related work items as expected.
 
⚠️ Upgrade Impact: data load packages no longer need an explicit Sharedo relationship entry for matter to proceeding, bringing the Proceedings load into line with Offers, Invoices and Payment Requests.
   140073
Documents
Tags do not hydrate - suspected issue with identifying the correct Context

 
Fixed an issue with document bundling where tags applied through the Context or the bundle's parent work item failed to populate when the bundle was generated. Tags from both sources now resolve correctly during bundle generation.
   111477
Documents
Error when changing data context on document template configuration

 
Fixed an issue on the Add and Edit Document Template blade where, after a template had a To participant with a role restriction, changing the data context caused the blade to error. The data context can now be changed cleanly on templates with role-restricted participants.
   125526
Documents
About field displays Missing Sharedo! error when work item does not have a title

 
Fixed the Prepare Document About field, which previously displayed 'Missing Sharedo!' when the context work item had no reference and no title, for example work items created via the public API with a null title. The field now shows a clear message stating that a reference or title could not be resolved for the matched work item.
 10651 129584
Emails
Error when viewing Attachments on Outbound Email blade

 
Fixed an issue where attachments on a filed outbound email could not be previewed or opened, displaying a broken link error instead. Attachments on filed outbound emails now preview and open correctly from the email blade, including emails filed through the Outlook addin.
   136062
Emails
Other users unable to view email details if email signature is present

 
Fixed an issue where users other than the email creator were unable to view outbound email details when the email contained a signature. Other users can now open and view the full email details regardless of whether a signature is present.
 14749, 15402, 13960, 15517, 15976 138205
Finance
Chart of Accounts - Restrict Code Combinations config is still being validated against when turned off

 
Fixed an issue where the Restrict Code Combinations setting in Chart of Accounts configuration continued to flag valid codes as invalid on linked transactions even after the setting had been disabled. Turning the setting off now removes the restriction immediately. Note: a full page reload may be required on the matter screen after the global feature toggle is changed and the configuration cache is reset.
   102110
Finance
Budgets- Update the logic around editability of budget phase plan to match the warning message

 
Fixed an issue on the Configure Budget Structure blade where the Budget Phase Plan dropdown could still be changed on a budget that was already in use, despite a warning message stating that it was locked. The field is now read-only once transactions have been recorded against the budget structure, and remains editable on budget structures that are not yet in use.
   104575
Finance
Finance Portal Widgets are available for the workbench designer but are not valid in that context

 
Removed the Finance Portal Widgets from the workbench portal designer, where they were selectable but produced no meaningful output because they require a work item context. The Budget Analytics, Budgets Navigation and Payment Plans portal widgets are no longer offered when designing global portals, but remain available within work item portals where they continue to work as expected.
   113797
Finance
Tax Rates Global Feature - Sales/Purchase account config does not import correctly to new environment (Address Time -> Internal Costs config at the same time).

 
Fixed an issue where Sales and Purchase account configuration on the Tax Rates and Time Internal Costs global features did not import correctly into other environments, because the configuration was tied to identifiers that differed between environments. Both features now store the code combinations in a form that is consistent across environments, so export and import behave reliably.
 
⚠️ Upgrade Impact: a Modeller Assistant migration job has been provided for each of these features and must be run after the upgrade, otherwise Tax Rates and Time Internal Costs will show as invalid and cannot be used until the job has completed.
 13274, 12001 127484
Finance
Tax Rates global feature breaks if account codes are disabled

 
Fixed an issue where the Tax Rates global feature failed to load if a referenced Chart of Accounts code had been deactivated or deleted, preventing administrators from repointing the feature to a different code. The Tax Rates feature now shows a warning when the stored codes are missing or no longer match the system, and allows the codes to be re-selected from the configuration blade.
   126190
Finance
UoM on Default Internal Cost Rates should be locked to Hour

 
Fixed an issue where the Unit of Measure on Default Internal Cost Rates in the Time Internal Costs global feature could be set to any time-related unit, when it should always be Hour to match the equivalent restriction on Goods and Services Internal Cost Rate Items and Rate Card Items. The Unit of Measure on these rate currency defaults is now fixed to Hour.
   133413
Finance
Budget Status widget doesn't update calculated positions correctly

 
Fixed an issue where the Budget Status widget did not reflect calculated position values correctly when the underlying input values changed, even though the budget itself calculated them correctly. Calculated positions now match the budget across all configured scenarios, and the widget also respects the Show When Zero Value setting in cases where a transaction has been rejected and reverted to zero.
   133595
Finance
Can't add Header/Footer aspects to Budgets

 
Fixed an issue on the Budget Display configuration blade where the plus button for adding aspects to the Header and Footer sections of a budget was unresponsive. Header and Footer aspects can now be added as expected and display correctly in the budget UI.
   134130
Finance
Account Codes and Account Categories filters dont work. 

 
Fixed an issue in Chart of Accounts configuration where filtering Account Codes or Account Categories by the parent column returned no results when searching by the code prefix, because only the parent name was being matched. The parent filter now matches against the full parent display name, including both the code prefix and the name, so searches return the expected results.
   134694
Finance
Payment Request vatAmount UI control is resetting to zero for existing payment requests with a vatAmount

 
Fixed an issue on the Payment Request blade where a manually entered VAT amount was overwritten with a value calculated from the tax rate when the request was reopened, even on transaction line types where the tax rate field was not shown on the form. The VAT amount is now preserved as entered, and the disabled tax setting now correctly shows the control as read-only rather than hiding it. The Create Payment Request workflow toolbox item has also been updated to populate the VAT amount correctly when creating payment requests through workflow.
 13430 135471
Finance
CodePath resolving should filter to only active segment codes in toolbox items

 
Fixed an issue where the Create Invoice, Create Payment Request and Create Invoice Interest workflow toolbox items could pick an inactive Chart of Accounts segment code when both an active and an inactive version of the same code existed. These toolbox items now match against active segment codes only. A new Modeller Assistant monitor job has also been added that highlights inactive segment codes that are no longer referenced anywhere in the system and can be safely deleted; running it is optional and is intended to help administrators tidy up unused configuration.
   138191
iManage
ID based retrieval of a document should respect the UseLatestPublicVersion setting

 
Fixed an issue where iManage documents opened from a task or email blade ignored the repository.matter-documents.type.versioning.useLatestPublic setting, so users continued to see the original version of a document even after a newer public version had been uploaded. The setting is now respected when documents are opened from task and email blades, so users see the latest public version in line with the configured behaviour.
 14199, 15650, 16296 128602
iManage
null reference on document upload to repository

 
Fixed an issue where uploading documents to an iManage repository could fail under certain conditions when the response from iManage did not include the expected file details. Documents now upload successfully in these cases.
 13118 135468
Import/Export
Key Date "Create" Permissions not set in target environment following import

 
Fixed an issue where Create permissions on a key date work type were not carried across when exporting and importing the work type between environments, leaving the target environment with no users or teams able to create that key date. Work type Create permission assignments are now included in the export package and applied on import, removing the need to recreate them manually.
 14624 135139
Key Dates
Can't add a key date after removing due to transition error

 
Fixed an issue where a key date could not be re-added after it had been removed, with the system reporting that no valid transition existed from milestone-removed to milestone-planned. A previously removed key date can now be restored without error.
 15326, 14766 139483
Key Dates
Workflow created Key Date failing after initial success

 
Fixed an issue where a workflow that created a key date would error on subsequent runs after the original key date had been deleted, because the workflow tried to update the removed key date instead of creating a new one. The create-delete-recreate cycle now works as expected for both manual and workflow-driven key dates, including cases where the key date is restored directly into a Done or Missed state.
 15718, 16240, 15516, 15919, 14766, 15996, 16136 140395
List View
A 'given key not present in the dictionary' error occurs when trying to add certain finance list views as a new list view

 
Fixed an issue where opening certain finance list views from Modeller > Forms & Views > List Views to create a new list view produced a 'given key was not present in the dictionary' error. The Fee Templates list view can now be created without error, restoring administrators' ability to follow the Modeller Assistant guidance for re-creating affected list views.
   136412
List View
When totalling monetary values across multiple list view pages behaviour is confusing

 
Fixed a confusing display on list views with monetary totals where, on lists paginated across multiple pages, the totals bar showed the sum of every row across all pages but the row count next to it referred only to the rows on the current page. The totals bar row count now explicitly reflects the total number of rows being summed, making the total easier to interpret.
 13845 137343
ODS
Cannot delete an Org Hierarchy Role once it has been used

 
Fixed an issue where Organisational Hierarchy Roles could not be deleted once they had been used, even after all current usages had been cleared. This has been resolved as part of the Job Roles feature, which now correctly checks for genuine references and allows roles with no remaining usages to be removed cleanly.
   138714
ODS
People search by phone number not working with spaces

 
Fixed an issue where searching for a person or organisation by phone number returned no results when the search term included spaces, because the stored numbers are held without spaces. Phone number searches now return results regardless of whether the user enters spaces.
 
⚠️ Upgrade Impact: the Elastic indexes for people and organisations must be rebuilt after the upgrade for this fix to take effect.
 13495 136076
Offers
Role ordering incorrect when offer blade is reopened

 
Fixed an issue on the Offer Details blade where participant roles such as Offer From Party and Lodged By were displayed in the wrong order after the offer was saved and reopened. The Offer Details blade now respects the display order defined in the offer roles configuration both when saving and when reloading the offer.
   139408
Option Sets
Changing the name of a new Option Set before the blade has been closed leads to the creation of a new Option Set on subsequent saving.

 
Fixed an issue when creating a new option set where changing the name after the first save, but before closing the blade, caused a second option set to be created with the new name rather than renaming the existing one. The blade now updates the existing option set when the name is changed after the initial save, so only one option set is produced.
   126016
Participants
Sharedo ownership is not set to inactive when a participant role is set to removed (cosmetic only)

 
Fixed a cosmetic issue where setting a participant role to Removed in the Participant Role Modeller did not flag the role as inactive on the work types it was associated with. The work type Participant Roles list now shows the role as Disabled when the underlying participant role has been deactivated, and the Edit Sharedo Type Role blade displays a warning so configurators can see that the role is no longer in use.
   100776
Participants
ODS Settings for People and Users are exclusive but should be inclusive

 
Fixed an issue where the Person and User settings on a participant role behaved exclusively rather than inclusively, so a role configured for Person did not return people who were also users. Roles configured for Participant Type Person now return all active people, including those who are also users, while roles configured for User continue to return only people flagged as users.
   97124
Participants
Redundant Participant roles appearing in the list of Roles available for assignment to a matter

 
Fixed an issue where redundant participant roles that had been removed or made inactive still appeared as options in the role dropdown when editing an existing participant on a matter, even though they were correctly excluded from the Assign Participants and Manage Participants screens. Inactive or disabled participant roles are now consistently excluded from every list of selectable roles across the participant UI.
   99102
Participants
Misleading title for the disable functionality

 
Fixed a misleading label in the participant roles burger menu, where the Remove option did not actually remove the role but only marked it as inactive. The option is now labelled Set Inactive, and changes to Set Active when the role has already been deactivated, so the action matches what the system does.
   99104
Participants
The title of blade does not match that of its nav bar

 
Fixed an inconsistency on the Edit Participant Role blade where the blade title read 'sharedo settings' but the navigation bar referred to the same area as Sharedo Ownership. As part of the Job Roles changes, the separate Sharedo Ownership blade has been removed and the ODS settings have been merged into the main participant role blade, with participant roles now assigned to work types through the work type modeller.
   101493
Participants
Opening 'Team' role causes infinite spinner and error in console

 
Fixed an issue where opening a participant role named Team caused the role blade to hang on an infinite loading spinner. The blade now loads correctly for participant roles of any name, including Team, Person, Organisation, Title and Vehicle.
   135174
Participants
Deleting a 'Team' role causes an error

 
Fixed an issue where deleting a Team participant role failed with an error, leaving the role in place. Team roles, and other participant roles with related ODS type role configuration, can now be deleted cleanly.
   135185
Participants
ODS Entity Picker aspect does not respect role sourcing configuration for 'Query the ODS'

 
Fixed an issue with the ODS Entity Picker aspect where users could still search the wider ODS for People, Organisations and Teams even when the role had been configured to source only from a parent work item with Query the ODS disabled. The picker now respects the role sourcing configuration, so only the configured parent sources are available when assigning the role.
   136179
Repository Explorer
'Auto Open Docked Preview' no longer works

 
Fixed the Auto Open Docked Preview toggle on the Repository Explorer widget, which had stopped opening the document preview automatically when a user navigated to the matter DMS. The preview panel now opens automatically when the toggle is enabled, and any manual open or close action by the user overrides the configured default for subsequent visits.
 13334 135480
Repository Explorer
Unable to change cursor position when renaming file title

 
Fixed an issue in the Repository Explorer where, when renaming a document title, the cursor could not be moved within the textbox because the text remained fully selected after the initial click. Users can now click inside the rename textbox to position the cursor freely while editing the title.
   140191
Repository Explorer
Renaming a file will update the title in related documents

 
Fixed an issue in the Repository Explorer where renaming a document from the DMS page also overwrote the title on related work items, such as the originating Prepare Document blade. The document title and the work item title are now kept independent, so renaming the file no longer changes the work item title.
   140389
Repository Explorer
Flat DMS is only showing the "Open in Browser" option

 
Fixed an issue where Flat DMS only offered an Open in Browser option on the document burger menu, even though the standard DMS view offered both Open in App and Open in Browser. Both options are now available consistently in Flat DMS and in document search results.
   140391
Security Barriers
Security barriers not applying rules to allow/deny role allocation

 
Fixed an issue where Security Barriers rules did not prevent allocation of a denied role to a team, because the team restriction check only considered rules that targeted a person or user. Deny rules now correctly block role allocation to both users and teams as defined in the rule.
   139375
Tasks
Error is thrown on creating a Task without a Title

 
Fixed an issue where creating a task without a title produced an error, even when Title is Mandatory had been set to False on the task aspect configuration. Tasks can now be saved without a title when the configuration allows it, and the mandatory check continues to apply correctly when Title is Mandatory is True.
   137342
Time Recording
When Time Category Restrictions = False, previously configured Applicable Categories persist

 
Fixed an issue in Time Recording where, after turning off Restrict Available Time Categories for a work type, any previously configured Applicable Categories were still being enforced. The selected categories are now cleared when the restriction is disabled, so all time categories are available again when creating a time entry on that work type.
   132961
Time Recording
Gap in UI on time recording blade when no work item is selected

 
Fixed a layout issue on the manual time entry blade where, when opened from a global portal context with no work item selected, a gap appeared between the right-hand edge of the form and the edge of the blade. The time entry form now fills the full width of the blade in both global and work item contexts.
   137896
Transcription
Speechmatics plugin overwrites global Content-Security-Policy

 
Fixed an issue where enabling the Speechmatics transcription plugin caused the application's global Content-Security-Policy to be replaced with a minimal policy containing only the Speechmatics WebSocket source, leading to script and resource loading failures and conflicts with other plugins such as Vincent. The Speechmatics and Azure transcription plugins now add their required WebSocket source to the existing policy rather than replacing it, so the full policy is preserved.
   139284
Users
No warning

 
Fixed an issue where deleting a user from Admin > Users took effect immediately with no warning. Administrators are now prompted to confirm before the user is deleted, with a Cancel option that closes the warning without taking any action.
   113094
Widget
Object not set error when retrieving property viewmodel

 
Fixed an error on the Plot Sales property titles widget that occurred when a non-creator user opened a matter where the property location could not be read due to permissions. The widget now handles a missing location gracefully, so users without read access to the location can still open the matter without seeing an error.
   118204
Documents
Documents active filter showed "Favourites" instead of the Active/Inactive checkboxes

 
Fixed the Favourite filter in the Document Templates list view provider, so the Active/Inactive filter displays correctly.
 13725 128325
Documents
Duplicate version history was created and the oldest version returned a 406 Not Acceptable error

 
Fixed an issue affecting document version history so that all versions of a document now preview correctly.
   137376
Documents
Attaching a file to a Task caused infinite loading

 
Fixed an issue where attaching a file to a Task could load indefinitely. File preview and attachment errors are now handled gracefully.
   141731
Documents
Buttons shown on hover on the Related Document blade were unresponsive and displayed incorrectly

 
Fixed the hover buttons on the Related Document blade, which were unresponsive and had a broken display. File preview and related errors are now handled gracefully.
   141732
Documents
"Clone Template and Pack Documents" did not clone the Question Sets

 
Fixed an issue where using Clone Template and Pack Documents on a document template did not copy the associated Question Sets to the cloned template.
   123368
Documents
Document bundling threw an error when the same document was added more than once

 
Fixed a bug that occurred when a bundle contained more than one copy of the same document.
 16029 137361
Documents
No warning was shown when previewing an unsupported file type

 
Document preview is now enabled only for file types supported by Prizm, so unsupported files can no longer be previewed.
   137607
Documents
Document Split could only be created from within the DMS

 
Document splits can now be created and processed from any entry point, not just the DMS. When a filing repository is not supplied at creation, the processor resolves one from the sharedo's linked repositories and saves it back to the split.
 14859 140864
Documents
Unable to share a document from the DMS to the post room

 
Fixed an error during PDF conversion when using the Post task as a share target in the DMS widget, so documents can be shared from the DMS to the post room.
 12117, 15142 135479
Repository Explorer
The Office 365 repository search API returned a leading slash for root files

 
Fixed an issue where the Office 365 provider's repository search API returned a leading slash for files in the repository root.
   139371
Repository Explorer
Downloaded files with a comma in the filename had an incorrect name

 
Fixed an issue where files with a comma in the filename downloaded with the wrong name; they now keep the correct name.
   139390
Repository Explorer
A console error was reported over a missing icon in the templates explorer

 
Fixed the console errors reported when viewing the Templates Explorer.
   129953
iManage
iManage approved default security values were not configurable for latest-version resolution

 
When serving an iManage document, Clio Operate resolves to the latest approved version. Previously "approved" always meant the security value "public". The security values treated as approved are now configurable per iManage repository, and Clio Operate can refuse to serve a document that does not meet them.
   141805
iManage
Preview and Download were no longer available in iManage-backed repositories

 
Fixed an issue where Preview and Download were unavailable in iManage-backed repositories. File preview errors are now handled gracefully.
   141539
Emails
Outbound emails used the work item title as the email subject instead of the subject

 
Fixed an issue where the value entered in the Subject field on the email blade was ignored and the work item Title was used as the outbound email subject. Sent emails now use the Subject from the email blade, and fall back to the work item Title only when no subject has been entered.
   122188
Emails
Email questionnaires did not show in email focus mode

 
Fixed an issue where email questionnaires were hidden by email focus mode; they now display.
 15049, 14664 139180
Emails
The Email Details more-options menu could show CC and BCC as enabled even when hidden

 
Fixed the CC and BCC handling on the email aspect. CC and BCC links now appear next to the To field and expand the fields when clicked.
   136423
Workflow
Workflow Trigger did not remember its trigger configuration

 
Fixed the workflow trigger editor for approval events, where reopening a saved trigger showed a blank approval model dropdown even though a value had been saved. The saved configuration is now retained.
 12813 134329
Workflow
A document-generated event did not appear in the chronology when generated via a workflow

 
Fixed an issue where a document-generated event was not logged in the chronology when triggered from a workflow.
   135194
Workflow
Incorrect icons and buttons appeared on the ribbon for Edit Variable in the Visual Workflow Modeller

 
Improved the ribbon on the Add/Edit Variable blade in the Visual Workflow Modeller, correcting the icons and buttons.
   135148
Workflow
Finance toolkit items did not render an icon on the workflow canvas

 
Fixed an issue where the Create Invoice Interest Transaction workflow toolbox item did not show its icon on the canvas.
   105378
Workflow
A search-criteria validation error remained on the Find Work Item block after selecting "Search by phase"

 
Fixed the search-criteria validation on the Find Work Item block in Visual Workflow, so the blade can be saved when Search by phase is selected.
   116436
Business Rules
The rules engine could error when a rule was applied to a person aspect

 
Fixed an issue where the rules engine errored when an empty or null ODS identifier was passed through for evaluation.
 15116 125418
Business Rules
When testing business rules, a changed custom parameter value was not reinitialised

 
Fixed an issue where testing business rules in the evaluation panel overwrote custom parameter values with previously cached test-run values, which could mask a user's edits. Edited values are now preserved.
   130243
Data Composer
Saving a calculated field on a work type with no derived types showed an unnecessary cascade prompt

 
Fixed an incorrect cascade prompt when saving a calculated field on a work type with no derived types. The cascade option now appears only when the selected entity type has derived types.
   137512
Work Types
After deleting a child work item on a type relationship that does not allow multiple children, the option to create another was missing from the parent ribbon

 
Fixed an issue where, for a type relationship configured to not allow multiple children, deleting the child did not restore the create-child option on the parent blade ribbon. It now reappears once the existing child is removed.
   134216
Participants
The wrong field was focused when multiple participant blades were open

 
Fixed an issue so the correct roles field is focused when multiple participant blades are open.
   119387
ODS
Merge Organisations showed a Party Types tickbox with no label when the field was blank

 
Fixed an issue where a merge line was shown for Party Types when both sides had no configured labels; the empty, unlabelled row is no longer displayed.
   136224
ODS
The ODS search blade intermittently threw a "Value cannot be null. Parameter name: key" error

 
Fixed an intermittent "Value cannot be null" error in the ODS search blade when searching for people or users, for example to impersonate a user or reassign a matter, even with valid search terms.
   133663
ODS
The Job Roles migration did not copy team members that had no team member history

 
Fixed an issue in the Job Roles migration where team members without team member history were not copied over.
   140207
Key Dates
Participant role key dates were overwritten and did not save correctly

 
Fixed an issue where participant role key dates were overwritten and did not save correctly.
   141106
List View
Grouping showed a broken row count in the activities list view

 
Fixed an issue where issue grouping produced a broken row count in the activities list view.
   141747
List View
ListViewWidget threw an "Incorrect syntax near ')'" error when the contact-preference global feature had no "On Form" preferences

 
Fixed an issue where the list view widget threw an "Incorrect syntax near )" error when the contact-preference global feature had no On Form preferences configured.
   138210
Reporting
In Report Builder, an empty data source view did not fall back to Default

 
Fixed Report Builder so the data source now always reverts to Default when left empty.
   139404
Reporting
Embedding a paginated report on a Power BI dataset was not supported

 
Added the ability to use paginated reports on top of a Power BI dataset in Operate.
   141432
Finance
The Financial Summary Radar widget displayed zero-value segments

 
Fixed an issue where the Financial Summary Radar widget showed zero-value segments; these are now filtered out of the plot.
   139345
Finance
The Rate Cards edit-rates navigation incorrectly flagged valid codes as invalid

 
Fixed the rate card edit-rates navigation so a new rate card item with a default price of 0.00 can be created without the previous workaround.
   142700
Finance
The Budgets navigation widget did not open its panel when used on a matter

 
Fixed an issue where the Budgets navigation widget did not open its panel when used directly on a matter.
   118966
Finance
The Budget Status widget did not enforce validation

 
Added validation enforcement to the Budget Status widget.
   122057
Finance
Deleting a Budget Structure Segment Value with attachments threw an exception

 
Fixed an error when deleting a budget structure segment value that had document attachments. Such values are now deactivated rather than deleted, consistent with values referenced by transactions, and no longer reappear in the configuration grid.
   124734
Finance
The Budget Analytics graph showed the same plot when multiple instances were on one portal

 
Fixed an issue where the budget analytics graph did not display correctly when multiple instances of the widget were on the same portal.
 10652 126296
Finance
The Description/Details field disappeared after saving on the Payment Request blade

 
Fixed an issue where the Description/Details field disappeared after saving on the Payment Request blade; it is now retained.
 11593 128484
Finance
The Create Invoice toolbox item threw a script error when a Payment Due Date was set but Payment Due After Days was empty

 
Fixed an issue where the Create Invoice toolbox item errored when no Payment Due After Days value was set, even when a valid Payment Due Date was configured. See the Upgrade Impact tab.
 13525 135500
Finance
Migration error when deploying the Rate Card feature if a rate card type had previously been deleted

 
Fixed an issue where deploying the Rate Card / Goods and Services migration could fail on a foreign key constraint if a rate card type had been deleted while it still had items associated with it. Orphaned rate card items are now assigned to an "Unknown" rate card type during migration; these appear under the inactive view on Admin > Goods and Services Rate Cards and cannot be re-activated through the UI. See the Upgrade Impact tab.
   143193
Audit
The audit feature could cause poor performance at high volume

 
Improved the audit cleanup maintenance plan to delete in batches, with configurable batch size, command timeout and maximum running time.
 10735, 15044 123423
Aspects
Longitudes over 85 could not be entered into the Map aspect

 
Fixed a bug that prevented a Map aspect with a longitude over 85 from saving correctly.
 14434, 15320, 16343 138445
Permissions
Buttons on the Global Permissions blade were unresponsive if the user made changes more than once

 
Fixed the Global Permissions blade, where the Save/Discard buttons could be left in an invalid state after repeated changes. Change detection has been added and the team's permissions-changed event now includes the team ID so it fires only for the loaded team.
   133531
Permissions
Permissions were not deleted despite the endpoint returning a successful status

 
Fixed an issue in the identity client admin where permissions were not deleted even though the endpoint returned success.
   134405
Chronology
Chronology Time Focus reloads applied auto-populated date boundaries incorrectly

 
Fixed an issue where the chronology Time Focus reloaded and applied auto-populated date boundaries to the search incorrectly.
 12214 140601
Modeller
The sub-feature expand button was hard to see

 
Fixed an issue where the Modeller sub-feature expand button was not visible against some theme colours; it is now visible regardless of theme colour.
   139764
Modeller
The Service Portfolio Modeller allowed descriptions longer than the database limit

 
Added a validator and error label to the Description and Title fields, limiting them to 250 characters to match the database column limits.
 14577 140143
Themes
The brand logo did not change when previewing a Theme

 
Fixed an issue where the logo did not update when previewing theme and iconography changes; it now changes temporarily during preview.
   140943
Finance
Payments summary widget chart rounded values to the wrong number of decimal places

 
Fixed an issue where the Payments summary widget chart did not round to the currency's minor unit correctly, so an amount such as 67.35 could be shown as 67.40. The chart now uses the correct decimal precision for the currency.
   80838
 
 

⚠️ Upgrade Impact

If you are upgrading an existing environment, read this section carefully before you begin. It covers breaking changes, configuration updates, and anything else that could cause issues if not addressed. Skipping this section could result in unexpected behaviour or data issues. Each item listed may require action.

Use the dropdown to filter by product area, or type in the search box to narrow results further. 

Product Area Upgrade Impact
Data Composer

Calculated fields is not displayed in browser - Previously, the fully materialised related work item was available for selection (e.g. all fields of a Prepare Document POI); now only basic work item data (title, phase, reference) is available. This was necessary to prevent infinite loops during schema introspection caused by the addition of ChronologyRecordGraphType, which was causing calculated fields to be missed.

This fix changes how Chronology POI work type references are resolved in Data Composer.

 

⇢For full details see the Issues Resolved tab and enter 133185 into the search field.
Data Loading

Data load packages no longer need an explicit Sharedo relationship entry for matter to proceeding, bringing the Proceedings load into line with Offers, Invoices and Payment Requests.

 

⇢For full details see the Issues Resolved tab and enter 140073 into the search field.
Document Management

The Blacklisted attachment types setting has been removed from Admin > Channels > Email.

If your implementation was using this setting to restrict file types on inbound emails, those restrictions are no longer active after upgrading to 7.12. Configure the File Extension Whitelist global feature to restore the intended behaviour.

⇢For full details see the New Features & Enhancements tab and enter 120508 into the search field.
Finance

Tax Rates. A modeller assistant job has been created for each feature to migrate existing segment code Id config to CodePath config. A Modeller Assistant migration job has been provided for each of these features and must be run after deployment - until it is, the Tax and Internal Costs features will show as invalid config and cannot be used. 

 

⇢For full details see the Issues Resolved tab and enter 127484 into the search field.
ODS

Organisational Hierarchy Roles in Participant Roles have been deprecated. These have been replaced with a new Job Roles feature.

The migration is automatic, but there are a few things worth being aware of. If you have not used Organisation Hierarchy Roles, the upgrade will have no impact - the new Job Roles feature will just be available. 

If your email signatures use the deprecated ods.user.primaryTeam.role.name tag, either directly in the Email Signature global feature configuration or through a profile override, update them to the Job Roles equivalent. Email signatures were not covered by the usage-flagging jobs, so a signature still referencing the old tag will send with the tag unresolved.

 

⇢For full details see the New Features & Enhancements tab and enter 126630 into the search field.
ODS
People and organisation search by phone number has been fixed to correctly handle numbers containing spaces. Phone numbers are now normalised before indexing and searching. 
 
The Elasticsearch index for people and organisations must be rebuilt after this update is deployed for the fix to take effect.
 
⇢For full details see the Issues Resolved tab and enter 136076 into the search field.
ODS / Participants

Banking detail permissions have been updated. The single read permission has been replaced with two granular permissions: readFull and readPartial.

Action required for all upgrades.

  • The bankdetails.read permission no longer exists.  Users who previously had the read permission, will be migrated to the new readPartial permission. If they require the full read permission readFull, then it will need to be explicitly granted by an admin. 
  • Users with no banking detail permission will no longer see the banking details section after upgrading, even if the navigation was previously enabled for them.
  • API integrations using the DataComposer overridePermissions bypass will no longer receive banking detail data after upgrading unless they are explicitly granted readFull or readPartial. Sensitive fields will return null rather than a 403 error when no permission is held. API integrations must be updated to include the appropriate permission before the upgrade is applied.
  • Review all existing integrations that consume banking detail data and assign the appropriate permission before the upgrade goes live.

⇢For full details see the New Features & Enhancements tab and enter 137003 into the search field.
Participants

You can no longer edit Sharedo Ownership from Participant Roles - the option has been removed from the Actions menu and the Nav bar. Instead this is now only managed via the work type. 

This change removes one route to Participant role configuration in Work Types. Alert your configurators to this. An alternative route already exists, but they may be used to the old path.

 

⇢For full details see the New Features & Enhancements tab and enter 126493 into the search field.
Repository Explorer
Fixed the 'Auto Open Docked Preview' toggle for the Repository Explorer widget, which had stopped working. 
 
If the toggle does not appear to take effect, clearing browser storage (F12 > Application > Clear site data) may be required, as manually toggling the preview panel stores a user preference in the browser that overrides the configured default.
 
⇢For full details see the Issues Resolved tab and enter 135480 into the search field.
Workflow

Workflows now route across five dedicated processing streams based on priority. On upgrade, five new streams are created.

The existing {environment}-execution-engine-processing role is renamed to -3. Priority 3 retains its current node and role count. Streams 1, 2, 4, and 5 each receive two roles. No manual migration steps are required.  Be aware that if there is an existing stream, as this change creates new streams, any events sat on the old stream will remain and be processed there. That stream and the role will be deleted by the Clio Operate team once all processing is complete.

 

The prefix for the execution priority streams and the default priorities are set in the Execution Engine global feature. 

 

⇢For full details see the New Features & Enhancements tab and enter 132222 into the search field.
Document Management

Legacy file name tokens ([OriginalName], [OriginalNameWithTimestamp] and [attachmentFileName]) are automatically migrated to the canonical [_title] / [_titleAsFilename] tokens by a seed migration, so no manual configuration changes are required.

New fileNamingRule config keys are added to the email archive channel and document bundling configs, seeded with backwards-compatible defaults.

⇢ For full details see the New Features & Enhancements tab and enter 135530 into the search field.
Document Management

Legacy document-bundling tag libraries are being retired. Existing bundle separator templates must be migrated: run the Bundle Template Migration job in Modeller Assistant, which scans templates for legacy tag names and context workarounds and can apply the changes automatically. Until templates are migrated, affected bundle tags will no longer populate.

The four legacy document-bundling tagLibraryLoaders entries are removed by a SQL migration.

⇢ For full details see the New Features & Enhancements tab and enter 95928 into the search field.
Finance

If you previously deleted a rate card type while it still had rate card items associated with it, the Rate Card / Goods and Services migration will now assign those orphaned items to an "Unknown" rate card type rather than failing. Review these items after upgrading, as they will sit under the Unknown type and cannot be reactivated through the UI.

⇢ For full details see the Issues Resolved tab and enter 143193 into the search field.
Finance

The Create Invoice toolbox fix applies to a workflow only once it is next saved or published. Any pre-existing workflows that use the Create Invoice toolbox item must be saved or published after upgrading before the fix takes effect for that workflow.

⇢ For full details see the Issues Resolved tab and enter 135500 into the search field.
ODS

The Job Roles migration now also copies team members that have no team member history, which were previously missed. The migration is automatic and no manual steps are required.

⇢ For full details see the Issues Resolved tab and enter 140207 into the search field.
 
 

 

new features 7.12 release notes 7.12 upgrade impact 7.12 issues resolved 7.12 fixes 712

Was this article helpful?

Give feedback about this article

Related Articles

Related articles in the knowledge base