> For the complete documentation index, see [llms.txt](https://ieg4.gitbook.io/onevu-digital-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ieg4.gitbook.io/onevu-digital-platform/openprocess-cases-and-workflow/openprocess-flex/worked-example-simple.md).
# Worked Example - Simple
Let's say you have a linear process like this for 'Report a Pothole':
The process as it stands means that irrespective of the size of the pothole or its priority the issue will always be passed to the same team and have the same SLA. But what if, having reviewed the details provided you could decide whether an inspection was required and thus treat small potholes differently from big ones. If we click on the plus symbol below 'Reviewing the details' step we can add a branch:
When you do this you will see your first condition. We need to give this a name and also add a condition. Before we can do this we need to create the options for the condition. We do this using the 'Fields' tab:
Let's say we want three conditions around High, Medium, Low priority we can see the choices for these below:
When you first add a branch it appears like this.
Clicking the purple 'branch' icon a further two times means we end up with three placeholders for our conditions:
Now we need to add the condition for each. The condition for each based upon what we learned about conditions earlier will be:
Fields\["PRIORITY"] == "Low"
Fields\["PRIORITY"] == "Medium"
Fields\["PRIORITY"] == "High"
E.g. the low one named and the condition added as follows:
Now, before we add steps to the 'branches' in the process we need to make it so the user needs to set a choice as a part of completing the first step. We do this by clicking the edit icon on the 'Reviewing the details' step, clicking on the 'Fields' tab and selecting the Priority choice as being mandatory to complete the step:
Doing this ensures that the priority is always known and it thus knows which branch of the process to go down. It should look like this when added:
Now when a user completes this step they will see this:
All that is left to do now is set the steps you want within each branch:
As we can see there are four steps and, in this case, all are specific to the branches they are linked to. These have their own SLAs, assigned to their own users and emails sent to the customer.
{% hint style="info" %}
**Note**
If there is a common step that will exist below all branches then you would add it at the bottom below the branch rather than adding it three times i.e. once in each branch. In the above scenario, a different end step is relevant for each branch.
{% endhint %}
---
# 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://ieg4.gitbook.io/onevu-digital-platform/openprocess-cases-and-workflow/openprocess-flex/worked-example-simple.md?ask=&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.