Ruleguard Update 4.109.0

We're pleased to announce that Ruleguard version 4.109.0 is now live!

This update contains the following changes:

Compliance Monitoring and Audit

• Manage Tests directly from a Plan. A Plan can now surface its Tests in one place, grouped under the Activity each belongs to, with add, remove and delete available inline and a choice of which Activity a new Test belongs to. Test detail loads when you expand it rather than all at once. 
• A new "Create sub-items" transition action. On transition, creates child items and adds them to a configured field. The number created can come from a field, or from a multiple-selection Data Library field on the parent - creating one child per selected value, each carrying its corresponding single value. 
• Compliance Monitoring items now appear in the Inbox. (Plans, Assessments, Findings, Recommendations and Tests under Assurance, following the same rules as today, and open from there as they do from their grids).
• Item counts on the Plan summary. A Plan now shows counts of everything it contains - Activities, Tests, Actions, Findings and Recommendations - resolved through the full hierarchy.
• Relationship configuration. An item type pair can be configured as either a parent-child relationship or a linked-item relationship. The two are mutually exclusive, which keeps the relationship unambiguous and keeps MI results consistent.

Improvements

• New "Period" field type. Capture a month range or a quarter range as a single value each with a start, and an end.

  • Period fields are available on Issue types, which covers Issues, Solutions, Business Services, Plans, Tests, Findings, Requests, Actions and Forms.

  • In MI, a Period behaves as a date dimension: you can group by it, use Month or Quarter calendars, and apply date filters, with the data table showing the full range.

• A Date field can now default to 'Today' or 'Tomorrow' rather than needing to be a fixed date.

• Auto naming - generate an item's name from another field. A new "Based on another field" Name format builds the name as optional prefix + a chosen field's value + optional suffix - for example Complaint - Acme Ltd (2026) - so names follow a consistent convention.
  • You can hide the Name box entirely and let it be set automatically.
  • The field you choose as the source is made mandatory automatically, so a name can always be produced, and the name is kept in step with that field (if the source field's value changes later, the name updates to match). 
• Rename a standard field. A standard field such as Name can be given a different label on an item type - Monitoring Title, for instance.
• Parent and Child types (Staged Workflows nested). Where an item type is configured with a child type and you click to add (the child) as a linked item Field type it is linked as a child and created inline without having to leave the parent.
  • Parent must be saved first
  • A new Field type will allow you to create this child from the parent.
  • You can remove / detach these items (which is separate to deleting these items which can also be achieved with requisite permissions).
  • Where an item type is configured as a child of one or more parent types, its grid now shows a Parent column by default. 
• A new way of viewing a Grid is offered that displays a smaller subset of columns that can be expanded (filtering, querying an all regular functionality continue to operate as normal) for a more compact and pleasing aesthetic. 
  • Provided for Issues and Staged Workflow Types.

• Radio-button lists are presented more clearly when the horizontal layout setting is switched on.

Fixes

• A user who uploads a file to a workflow event can now delete that file. Previously Users holding View events received a permissions error when attempting to delete a file.
• Creating an item using a Linked Item field that targets a Task List no longer throws an error. Selecting an individual Task within the list is again possible.

In a Rush?