# 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. You can add or delete memberse using the buttons in the circled area. 

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

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: 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:

```
GET https://help.novacuraflow.com/connectors/areas/communication/rest-service/rest-project-tool/enumerations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.