Workflow automation, registers on tasks, and dark mode
Automations now act across registers with record steps, for-each fan-out and approvals; registers show on evidence tasks; Light, Dark and System themes.
AutomationEvidenceRegistersIntegrationsPlatformSecurity
This release makes recurring compliance work something you design once and let run, and it makes evidence tasks show where their proof actually comes from.
Automations
Automations now act on records across the platform, not only on evidence tasks.
- Record steps for every module. A workflow can create or update an evidence task, an information asset, a device, a control exception, an access review, a form request or a training assignment, and chain those steps.
- "For each" fan-out. Run a branch once for every matching record, for example one access review per system owner.
- Waits and approvals. Pause a workflow for a delay, until a date, or until a named approver signs off. Approvals arrive in an inbox.
- Run on existing records. Start a new workflow against records that already exist, with errors written in plain words so the owner knows what to fix.
- Templates for common cases such as quarterly access reviews and new-vendor due diligence.
- Builder usability. A plain-words view of the workflow, a field picker with examples, visible task defaults, a match preview on conditions, a tick note, and a runs list with filters and search.
Every task that a workflow creates is written as a brief: the steps to take, the proof expected and a "done when" condition.
Evidence tasks and registers
- Registers appear on the evidence tasks they prove. Risks, vendors, assets, people, devices and training are opened from the task that depends on them, and the task explains how module-backed evidence satisfies it.
- Forms replaced the generic overview on module-backed tasks.
- Faster task page. The evidence task page makes far fewer requests, so large workspaces load noticeably quicker.
Appearance
- Light, Dark and System themes. Pick one in Appearance settings. New workspaces default to System, and every color in the app has a dark-safe pair.
Integrations
- A setup guide for every integration is available in the in-app documentation, including the permissions each connector requests.
- Tool logos load reliably and asset sources map to their providers.
Security and reliability
- Hardened tenant authorization checks on server actions and connection routes.
- The scheduler retries a missed tick once, so delayed workflow steps resume on their own.
See How pTrackly works for how these pieces fit together, and the roadmap for what is next.
