> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/pim3/reference/product-model-setup/workflows/workflow-states/workflow-transitions.md).

# Workflow transitions

Workflow transitions define how a workflow state can change.

You can add or update workflow transitions through [Product model setup](/pim3/reference/product-model-setup.md) > [Workflows](/pim3/reference/product-model-setup/workflows.md) > [Workflow states](/pim3/reference/product-model-setup/workflows/workflow-states.md) > [Workflow transitions](/pim3/reference/product-model-setup/workflows/workflow-states/workflow-transitions.md).

### Add a new workflow transition

1. Click the "Plus"-icon
2. Set Transition to state and Label along with additional [details](/pim3/reference/product-model-setup/workflows/workflow-states/workflow-transitions/workflow-transition-details.md)
3. Click "Confirm"
4. Click "Confirm"
5. Click "Update Workflow"

### Edit workflow transition

1. Click "Edit"-icon
2. Modify the workflow transition [details](/pim3/reference/product-model-setup/workflows/workflow-states/workflow-transitions/workflow-transition-details.md)
3. Click "Confirm"
4. Click "Confirm"
5. Click "Update Workflow"

### Delete workflow transition

1. Click the "Delete"-icon
2. Click "Confirm"
3. Click "Update Workflow"


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.struct.com/pim3/reference/product-model-setup/workflows/workflow-states/workflow-transitions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.