top of page


Dev Blog Update – Q1 2021

It’s been a busy few months for the growing ShareDo product team with release 6.27 bringing us a raft of new features.


  1. Developer IDE – as part of modeller there is now an integrated IDE for the development of custom portal widgets and other extensions.

  2. Data Composer – data composer continues to be enhanced with additional data scopes and extensibility improvements including connections, easier support for time zones, property details, incident details, multi-currency and support for data composer in title generators.

Core Case

  1. Enhanced time zone support enabling better management of geographically distributed teams and SLA timings.

  2. ODS Information Walls enabling groups of people, orgs or teams to be placed in “walls”; users are then restricted in their searches of these walls.

Document Assembly

  1. Simplification of the document template configuration model


  1. Introduction of more configurable time list views

  2. As part of the Finance 2.0 programme a new highly configurable budget framework has been released

  3. Enhanced support for units of measure and unit of measure types


  1. We have depreciated our Land Registry integration in favour of a more generic InfoTrack integration

These features are described briefly in the following sections. As always for more details please see the relevant help materials or contact customer success.

Modeller – Developer IDE

The developer IDE aims to bridge the gap between ShareDo “no code” configurability and true extensibility. Available to both SaaS and on-premise clients we will over time be depreciating the custom plugin model completely.

Instead of custom plugins you can now use the Developer IDE to implement extensions are fully integrated into the ShareDo modeller environment.

sharedo modeller environment

Just like VisualStudio you can create a number of different customisations. These customisations are supported by scaffolding


For the initial release the IDE is focused on extensions for

  1. Portal Widgets – if Sharedo doesn’t have the relevant widget you can now create your own widget in javascript

  2. Blades – with the ability to override blade behaviour or look and feel

The IDE will be gradually expanded with different customisation options over time to assist in the migration away from custom plugins. To assist with this process

  1. Custom plugins are now side-loaded into the main application and hence do not have to be part of your CI process

  2. All customisations implemented using the ShareDo IDE form part of the your solution packages and are imported and exported

  3. You can view the “old” style custom extension points from the “Custom Extension Points” global feature; these can then be replaced with “no code” extensions overtime

Custom Extension Points

[Modeller] Support of data composer in title generators

Tile generators

When configuring a title or reference generator for a work type you can now choose to load data composer fields. This will allow you to browse the dictionary for a work item and select the required fields or expressions that you require for your titles. The fields that are selected are then made available in the generation mask help.

[Globalisation] Time zones

ShareDo is increasingly being used by global organisations who perform functions across one or more time zones. Even organisations limited to a single country may face the challenges associated with multiple time zones.

To assist with these processing scenarios we have introduced

  1. A new global feature that enables you to turn on time zone support – if you are operating in only a single time zone then leaving this disabled will not add any additional functionality to your solution.

time zone support
  1. Once enabled you will then have additional time zone capture available for user profiles

Time zone
  1. The intended “working time zone” is then captured against work items; a common example being the capture of appointments

  1. Support for viewing these dates in both the work item and a user’s time zone is then provided via Public APIs, Data Composer, Forms, Document Assembly, chronology and calendar sync

[Security] ODS Walls

Within the ODS Area of ShareDo we maintain a master list of users, people, organisations and teams.

These master lists can be subdivided in a number of ways including the

  1. Configuration of different searches

  2. ODS Types

However there are various circumstances where we wish to create specific sets of ODS Entities to restrict the available entities that are available for different users. We describe these restrictions as ODS Information Walls

Examples of the use of walls include

  1. Restricting the list of users such that a client user can only see the users who are working on their account

  2. Restricting the list of organisations such that a client user can only see the organisations that they have as counter parties

  3. Restricting the list of users available for task allocation to only those that are in your business unit. For example the real estate team would only see real estate users

Like the majority of ShareDo feature enhancements ODS Walls are optional and are controlled by the feature framework via the “ODS Information Walls” feature.

ODS Information Walls

Within this feature you specify 2 elements

  1. The default wall that will be applied to all ODS Entities that are created; access to this wall will typically be given to system administrators

  2. The work types that should be used to default “walls” for specific processing scenarios; this is typically statements of work.

Once enabled with the Admin area you will then be able to maintain walls.

Maintain walls

With a wall contains a variety of different ODS entities with permissions to read or update these entities being granted to security teams.

Walls can be assigned in several ways

  1. Users can ODS Entities manually; either singularly or as a bulk action

  2. When a new ODS Entity is created it can be assigned a Wall by virtue of

  3. The default system walls – these are defined in the global feature

  4. By any default walls that are defined in the work item hierarchy

Information Walls restrict users actions in the following ways

  1. When a user searches ODS Entities the list of results returned is restricted by the users membership of Walls and the Read permission

  2. When a user attempts to update an ODS Entity their ability is restricted by the users membership of Walls and the Update permission.

[Document Assembly] Simplification of the template configuration model

The first step on our Document 2.0 programme of enhancements is the introduction of a number of new document assembly related features

  1. Documents are now administered via their own dedicated Admin portal; this can be accessed via the global launch pad

  2. When a template is created a variety of its settings are now based on the template type in order to make the experience of authoring templates considerably easier. Templates types are configured under the document assembly global feature

Templates types

When configuring a document template we now separate the “data context” from the display context enabling you to write about an appointment from a case

Edit doc
  1. The display of templates can also be further refined using matching rules

  2. In addition as part of the migration to the new document admin portal there have been a significant number of additional usability enhancements including

  3. Better management of pack contents

  4. Simplification of DMS Output settings

  5. Simplification of Display Rules

  6. UX Enhancements to document actions

The introduction of this feature has required a number of structural changes to the way templates are managed to assist with the migration of your templates within the new document admin portal there is a V7 Template Upgrade page

Doc admin

Within this page you can

  1. Initiate an upgrade of your templates; your templates will be upgraded to the new model in a matter of seconds

  2. Review the results of the upgrade; since we have introduced different data and display contexts to documents the upgrade process will attempt to assign these correctly, however where this is ambiguous warnings will be issued

[Finance] Time Recording Enhancements

Time recording list views have now been moved to the standard list view framework which in turn enables you to configure more flexible time views. Within modeller you will find a new list view provider for Time Entries which provides you with additional configuration options that are relevant to time management.


These include the ability to

  1. Filter time by users or teams in the list view definition

  2. Filter time by state e.g. submitted or unsubmitted

  3. Filter time be period

In addition on the time list views there are now additional actions for bulk reversing or submitting time.

[Finance] Enhanced budget configuration

As part of the Finance 2.0 programme of work we have introduced enhanced configurability into budgets. From the feature framework you can now access a budgets configurator.


From within this modeller you can then define your budget structures

Cost budget


  1. The segment of the chart of accounts that they are based upon

  2. What account codes are included

  3. What columns are displayed

The new budget functionality is also supported by a configurable set of widgets including

  1. Budget Transaction log

  2. Budget Radars

[Finance] Units of Measure

In this release we have introduced a configurable set of units of measures and types. Units of measure are then referenced in

  1. Goods and Services items

  2. Form definitions

Units of Measure are designed to enable you to invoice (sell) or purchase (buy) specific quantities of items; with the typical example being time.

Units of measure types are defined within the Global Feature and then specific codes maintained within the Admin portal

Units of measure

Relevant units of measure are then specified in Goods and Service definitions

Goods and services

[Integrations] InfoTrack – Property Search Integration

In this release we have now depreciated our land registry integration in favour of infotrack integration which provides not only land registry searches but significantly more.


Within the feature framework you can turn on Info Track integration specifying your connection settings, processing style and availability for work types.

Major Bug Fixes and minor enhancements

  1. 89935 – Ability for users to initiate a refresh of a Power BI report manually and have information on when the report was last refreshed

  2. 90392 – Enhancement of MoJ integration to support better injury and participant mapping

  3. 92225 – [Admin] Data load – Trying to create a new active run or opening an existing one throws a ‘404 content not found’ error

  4. 91281 – [Participants] Advanced ODS search – Searched for a postcode but the search results did not contain the postcode

  5. 91682 – [Participants] Advanced ODS Search (Add user to a team) – Refine search by team membership and a specific postcode returns unexpected results

  6. 92682 – [Modeller] Title Generator – Data Composer – Fails if a an ’empty’ field is included

  7. 82402 – [Case Management] Bulk Approval – Team Approvals – issue with approving own items in new bulk approval handler

  8. 92601 – [Document Templates] Document Template List View – system name should be visible

  9. 86402 – [Audit] Missing entries for participant removal

  10. 89091 – [Case Management] – Notifications list view not showing dismissed date

  11. 92283 – [Case Management] [Action Plans] – Emails accessed through action plan do not filter participants

  12. 90319 – [Modeller] [Option Sets] Duplicate names should be allowed

  13. 91949 – [Integrations] [iManage] Cannot save a matter title with a & in

  14. 89562 – [Case Management] [Striping] Option Set Striping: Court Type list on Proceedings does not honour jurisdiction matching rules for striping

  15. 91638 – [Modeller] Work Type Execution Engine Triggers doesn’t show triggers that are applicable via a path

  16. 89287 – [Modeller] Liability Feature: Not respecting role inheritance and forcing user to enter in role configuration at every level

  17. 91769 – [Document Assembly] Document Generation: issue with openXml generation with business rules in repeating tables

  18. 91768 – [Document Assembly] Address Formatter – AUS address format not working

  19. 90484 – [Document Assembly] – [Document Templates] – Fixed issue on document tags refresh not refreshing all tags in document templates

  20. 90642 – [Finance] – [Fee Templates] – Move VAT tax references to config

  21. 91577 – [Modeller] – [Global Feature: Litigation] – Matter Type Configuration throws an error

  22. 88449 – [Modeller] – [Global Feature: Liability]: Feature does not honour role inheritance

  23. 87552 – [Document Assembly] – [Multiparty Email]: Multiple Email Deliveries on MultiParty Documents not able to Complete task

  24. 91572 – [Case Management] – [Duplicate Search]: Dispute Matters(New instruction / matter spawn) – The duplicate search errors

  25. 91683 – [Modeller] [Finance: Goods and services] – A non-stop progress wheel is thrown when trying to open/edit an item

  26. 90366 – [Modeller] – [Aspects] – Duplicate aspects appearing in Add new aspect

  27. 90793 – [Case Management] [Search] Search for participants should not be case sensitive

  28. 91021 – Matching rules – new matching rule to ensure documents associated with work item at phase transition

  29. 90999 – Case Management – [Comments Widget] – Regarding link should be clickable

  30. 90999 – Case Management – [Comments Widget] – User interface update

  31. 91005 – Case Management – [Wiki Widget] – Support Default Config and Tables

  32. 91006 – Case Management -[Info Message Widget] – Support rich text and

  33. 91154 – Case Management – [List View Aspect] – Widget configurability

  34. 91177 – Case Management – [Phase Guards] – e-signature phase guard should support rich text

  35. 91549 – [Documents] Related Documents Widget UX Enhancements

  36. 91264 – [Finance] [Offers] Rationale should be a rich text component

  37. 92709 – Ability to conflict check on the intersection of two roles

  38. 92805 – [Autoclose Descendants] Move to feature framework


bottom of page