Skip to content
PRESHaiPRESHaiPRESHos Platform

Workflows

Workflows and Statuses manages workflows, statuses, and unified status mappings. Two tabs split the surface: Workflows and Unified Statuses. The workflow table lists each workflow with its status count, used-by, transition rules, creator, and dates. The visible rows include Agent Plans (9 statuses), Agents Tasks (9), Approval (4), Change Request (5), Client Status (2), Collaboration (3, used by Agent Ops Sessions, Comments, Notes), Company Lead Status (5), and Company Lifecycle Stage (8). Most rows shown are system-created with transition rules off. New Workflow creates; search filters the 36 rows across two pages.

Change a workflow only when the owning process changed. Status counts and used-by tell you what a change would touch.

  • Workflows tab lists each workflow with status count and used-by. Unified Statuses tab maps statuses across workflows.
  • Transition rules off means the workflow does not enforce transitions; used-by shows which surfaces consume it.
  • Collaboration is the one shown wired to Agent Ops Sessions, Comments, and Notes.
Settings Workflows and Statuses table with Agent Plans, Agents Tasks, Approval, and Change Request rows plus status counts

Workflows and work items

Section titled “Workflows and work items”

Every work item row holds exactly one status, and that status belongs to the workflow governing its type. The workflow is what makes a deliverable’s “In Review” mean the same thing on every row: the status set is shared, so views, filters, and rollups read every row the same way.

Work-item workflow: statuses behind project, deliverable, and task rows
  • A row moves status only when the work actually moved. Status theater — advancing rows to look busy — corrupts due-date views and the overdue grouping in My Tasks.
  • Transition rules off means the workflow does not enforce its transitions; teams that need a real gate (draft to review to approved with no skips) need the rules on for the governing workflow.
  • The Approval workflow governs work-item approvals in the Approvals queue: allow, deny, and redirect decisions move through its states, recorded on the audit trail.
  • Work-item shape around the statuses — which types exist, which fields each carries, what new rows start with — lives under Work Item Types. Change either side only when the owning process changed, since sessions in flight reference both.

What next

Section titled “What next”

  • Work items: the hub — hierarchy, lists, customization, workflows, approvals, sessions.

  • Work Item Types: the types these workflows govern.

  • Objects: the object groups behind the lists.