Skip to main content
A workflow describes a user behavior and the expected result. It is neither a Playwright script nor proof that anyone has tested it.

​
Author the saved-view workflow

Under Example Desk → Views, create: Write observable expectations. If filter order does not matter, avoid wording that accidentally requires it. Keep credentials and customer data out of prerequisites and steps.

​
Understand the three identities

Editing expectations appends history; it does not rewrite earlier definitions. Identical content retains identifiers. The workflow’s edit-lock version is distinct from the saved definition sequence. Moving a workflow to another area in the same product preserves its identity, history and direct link; moving across products is not supported.

​
Read history before judging old evidence

Open the workflow’s saved history to inspect the exact text used earlier. A later expectation change does not retroactively validate an earlier result. Runs should pin the workflow/definition pair; retrieving an unavailable pair must not silently substitute the latest text. Reference videos are optional illustrations of saved expectations. Replacing or detaching a clip preserves the earlier saved association. See reference videos for what a clip does and does not demonstrate.

​
Give an agent bounded context

Use list_product_workflows to search, then get_product_workflow for full current expectations. For batch retrieval, resolve_current_workflows accepts 1–50 stable IDs within a product and returns summaries; resolve_workflow_definitions accepts 1–5 exact pairs and returns saved expectations. Archived, invalid and unavailable references are explicit states. They are not permission to invent substitute expectations. See the running MCP contract for schemas and supported tools.