Skip to main content

​
Activating a Use Case

Activating copies a use case into your organization as an ordinary draft: a workflow, an agent, or an agent together with the workflow it runs. Nothing is compiled and nothing is published. You get exactly what was built and reviewed for the catalogue, bound to your documents, your approvers and your choice of how it starts. Open a use case and click Activate. Four steps follow.
1

Connect

The step lists only what this use case reaches for. Each toolkit is either connected, or offers Connect (an administrator connects it once, and every use case that needs it can then use it), or says We arrange it where your deployment cannot offer the toolkit yet. Each of your own systems is marked With us: that connection is set up together with us during activation.You can continue without connecting anything. The draft will not run until the toolkit is connected, and the last step reminds you.
2

Documents

For every document set the use case reads, choose one of your knowledge bases or Create one named after it. A knowledge base with the same title is preselected. New knowledge bases are created empty: add the documents after activation, as indexing takes minutes. A use case that works on the files handed to it at run time needs no knowledge base.
3

How it runs

  • How it starts — the use case proposes it. A workflow starts when someone starts it (from the workspace or through the API) or on a schedule; an agent works in a conversation. A schedule shows its next runs as you edit it, and is created switched off.
  • Who approves — for every approval in the use case, an administrator can pick the groups whose members decide, or leave it for later. Until someone is chosen, only administrators can decide that step.
  • Who can use it — only you for now, everyone in your organization, or specific groups (administrators only).
4

Build

The step runs on its own: it creates the knowledge bases you asked for, then the draft. You land on Your draft is ready with a summary, the list of things to do before you publish, and Open the draft.If something fails, the step shows why and offers Try again, which repeats only what failed. A knowledge base created by an earlier attempt is found by its title and reused.

​
What a draft is

The draft is a normal item in Agents or Workflows. Nothing can run it until you publish it: a schedule on it starts no run, an agent cannot reach it as a tool, and a conversation cannot address it. Run it on two or three real cases with the people who own the process, then publish it from the designer or the studio, the same way you publish anything else. Activating a use case twice creates a second draft; the use case page offers Open once one exists.