Skip to main content
This is a documentation pilot. Confirm final interface labels, permissions, and release behaviour against the production build before publication.
This tutorial creates a workflow for a recurring report. It begins when the required data is ready, drafts a report from the admitted evidence, and requires a human decision before publication.

​
Before you begin

You need:
  • A workspace where you can author the workflow.
  • A selected data source and a report purpose.
  • The required enrichment definitions for the report.
  • An agent definition that can draft the report.
  • A named reviewer, publication destination, security classification, billing owner, and budget.

​
1. Define the report

Create a new workflow and record the report’s purpose, source, scope, and reporting period. Choose the workspace artefact library as the publication destination for this first workflow. Keep the workflow specific to one report outcome; a reusable template can be created once the journey is validated.

​
2. Add the data stages

Add and connect the stages that prepare the report input:
  1. Start with the ingestion trigger.
  2. Add the data collection or job stage.
  3. Add the dataset produced by that work.
  4. Add the required enrichment stages.
Configure the condition so the workflow starts only when the ingestion succeeds and the required enrichment results are available. A partial ingestion or a required enrichment failure should stop automatic reporting.

​
3. Add the drafting stage

Connect the prepared evidence to the agent that will draft the report. The draft should identify its evidence, distinguish observations from inference, and surface uncertainty. Set the agent’s report purpose and any inputs it needs before enabling the workflow.

​
4. Require human review

Add a human review stage after the agent draft. The reviewer must see the exact report version, its sources, limitations, and earlier decisions. Configure the review outcome so that:
  • Approve allows publication of that version.
  • Request changes creates another report version for review.
  • Reject stops the run.

​
5. Add publication

Connect the approved report to the workspace artefact library. Publication must apply only to the version that the reviewer approved. If approval becomes stale because the report changes, require a new approval before publishing.

​
6. Test and activate

Run the workflow with a known input and verify each stage:
  • The ingestion manifest identifies the admitted source data.
  • Required enrichments reach a terminal outcome.
  • The start condition explains why the run was created.
  • The report shows evidence and limitations.
  • The review decision is recorded against one report version.
  • The published artefact has a publication receipt.
Activate the workflow only after the test run meets those checks.

​
Next steps