Workflows: run an AI workflow and read what it did

Steps

1. 1

   Open Workflows

   In the left menu, in the group Agent Mode, select Workflows. Four figures head the page: Active, for runs in progress, Completed, Failed, and AI Credits used across all runs. Under Active Workflows the list says No workflows yet.

   • Select Workflows
2. 2

   Select New Workflow

   Select New Workflow at the top right. The form explains that a workflow runs in the background and that its steps appear when it is complete. It has three fields.

   • Select New Workflow
3. 3

   Choose the workflow type

   Open Workflow Type and choose Regulatory Impact Analysis. A line under the field says what it does: it analyses a new regulatory alert and maps its impact across the entity's obligations. The type is the only required field.

   • Select Workflow Type *
   • Choose Regulatory Impact Analysis
4. 4

   Type the trigger event

   Trigger Event is a short label for what set this run off. It is shown in the list, so use it to tell runs apart. Type training example. If you leave it empty, the run is labelled manual.

   • Type Trigger Event: training example
5. 5

   Type the inputs

   Inputs is what the workflow works on, written as JSON: each name and each value in double quotes, pairs separated by commas, all inside curly brackets. For this workflow give the title of the regulatory update, its source, its jurisdiction, a summary and a relevance score from 0 to 1. The text typed here says clearly that it is a training example and not a real publication.

   • Type Inputs (optional JSON): {"title":"Training example: excise returns to list each product regist…
6. 6

   Select Run Workflow

   Select Run Workflow. The form closes with the message Workflow started, it will run in the background. The run appears in the list at once, and Active at the top counts it while it is in progress. You can leave the page: the run carries on.

   • Select Run Workflow

   

7. 7

   Wait for the run to finish

   The list refreshes by itself every few seconds. After a short while the status changes to Completed. Reading across the row: the workflow type, the trigger label you typed, the status, the number of steps it took, the AI credits it used, and when it started.

8. 8

   Open the run

   Select the row. A window opens with the trace of the run. At the top are its status, the AI credits used and the time it completed. Under Trigger Inputs is the text you typed, together with a line the app added itself: the list of tools this run was allowed to use.

9. 9

   Read the steps

   Below the inputs is Steps. Each numbered step names the tool the workflow used, its status and how long it took, and shows what came back under Output. The first step here read the entity's regulatory alerts. The steps are the evidence of what the workflow really looked at.

10. 10

    Read the result

    Scroll to the end, to Result. It lists any errors, here none, then the actions the run took: in this example one calendar entry and one risk insight, and no notification. Then comes the outcome, the workflow's own summary, the tools it used and the number of steps. A run in which a step failed is shown as Completed with errors. Treat it as a draft: compare it with the steps above, and check any action it reports in the place where that action would appear.

11. 11

    Close the window and check the figures

    Close the window. At the top of the page Active is back to 0 and Completed reads 1. Every run stays in this list with its trace, so a colleague or an auditor can see later what was run, on what inputs, and what it did.

    • Select Close