Product updates

Autonomy used to be a single setting on a worker: everything it could do sat at the same level. That forced a choice nobody wanted to make, because drafting a summary and closing a case are not the same risk.

Each action now carries its own level. Set filing to Act, drafting to Act with approval, and closing to Suggest, on the same worker.

Existing workers were migrated with every action set to the worker's previous level, so nothing changed behaviour on upgrade. Cases already in flight keep the level they started with.

See Choosing an autonomy level.

Deadline triggers used to fire on the day a deadline passed, which made every notification a reprimand rather than help.

Steps can now be triggered a set number of working days before a stage deadline. The obvious use is a warning to the case owner two days out.

Existing steps triggered on Deadline passed are unchanged. See Deadlines and working days.

Open any digital worker entry on a case timeline and you will find a Sources panel listing exactly which fields, documents and correspondence it used.

This is the fastest way to diagnose a wrong suggestion: a worker drawing on the right sources and reaching a poor conclusion is a guidance problem, one drawing on the wrong sources is a case data problem, and the fixes are entirely different.

Applies to actions taken from this release onward. Historical entries do not have it.

See What digital workers can see.

Approval gates have a new option: a second person, meaning anyone except whoever prepared the action.

Previously a Supervisor with approval rights over their own team could approve work they had prepared themselves. Where a policy required four-eyes, that was expected rather than enforced.

Existing gates are unchanged. See Approval gates.

Saved views were personal. A Supervisor can now share one with their team, where it appears in everybody's sidebar.

The most useful shared view on most teams turns out not to be "all open cases" but "cases with no activity in five days" — the ones quietly going wrong rather than the ones visibly busy.

See Searching and filtering cases.

A connector that failed after its retries recorded the failure in the integration log and nowhere else. On a case whose workflow depended on that call, the effect was that nothing happened and nothing said so.

Failures are now timeline entries on the affected case, naming the connector and the error.

Connectors still do not block a case when they fail. See Troubleshooting a connector.

Imported cases took their stage-entry date from the import timestamp, so every deadline was counted from the day you migrated. On a team importing cases already close to a statutory deadline, that was actively misleading.

The import mapping now accepts a stage-entry date column, and deadlines are counted from it.

Imports run before this release are not retrospectively corrected. If you imported open cases and the deadlines look wrong, contact support and we will work through them with you.

See Importing existing cases.

The audit log was readable on screen and nowhere else, which made preparing for an inspection a copying exercise.

Any filtered view now exports to CSV with the filters applied exactly as displayed.

Worth doing before the meeting rather than during it — reading the export beforehand means you find the awkward entry before somebody else does.

See Reading the audit log.