> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/6.11/development/flow-studio/connectors/communication/rest-service/rest-project-tool/enumerations.md).

# Enumerations

Enumerations can be used in models to limit the possible values a workflow designer can assign to a member of a model.

Consider for instance an API for 'orders' in a 'store'. We got the operations 'Add new order', 'Update order' and 'Delete order'. Let's look at the 'Order' model: 

![](/files/-M77Ztq08nEPAOBIANO5)

'status' is of type 'Enum': 

![](/files/-M77ZwtG1YYci5HenoOG)

And if we look at that enum you can see what possible values that member can have: 

![](/files/-M77_-mgyV4XLJBzlQQa)

Members of the enum can be added and deleted as needed (circled area above). Let's look at an operation using the 'Order' model, 'Update order' 

![](/files/-M77_4GP-MrYSrO4QzH7)

![](/files/-M77_7UrhyNN3g3RKTB_)

It uses 'PATCH' to only update certain members, accepting a body of model 'Order'. Let's look how this will look in Flow Studio:

![](/files/-M77_G8fIfNa4xXaVTBi)

When using 'Constant' as mapping to 'status' only the members of the enum are available. You can still mess it up by selecting 'Variable' as mapping and providing an invalid value in the passed variable. But with the usage of enums you can at least guide the person using the connector in Flow Studio in what kind of values are expected.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.novacuraflow.com/6.11/development/flow-studio/connectors/communication/rest-service/rest-project-tool/enumerations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.