# Camunda properties in BPMN

The Camunda Platform properties provider ships with this editor, which means the execution-level fields are editable here rather than in a separate modelling tool.

If your process will be deployed to a Camunda engine, this is where the parts that make it executable live.

---

## What this is for

* Processes destined for a Camunda engine.
* Configuring user task forms and assignment.
* Setting up listeners, mappings and job configuration.

---

## How it works

| **Action**                | **How**                                        |
| ------------------------- | ---------------------------------------------- |
| Forms                     | User task form definitions and fields.         |
| Listeners                 | Execution and task listeners.                  |
| Input and output mappings | Variable mappings into and out of an activity. |
| Job configuration         | Retry and async settings.                      |
| Extension properties      | Arbitrary key-value pairs the engine can read. |

---

## A few things that catch people out

* These fields are ignored by anything that is not a Camunda engine. They are harmless but pointless elsewhere.
* Setting execution properties does not make a process executable on its own; it still has to be deployed.
* If you are only documenting a process, leave all of this alone.

---

## Related

[BPMN token simulationPlay the process before anyone runs it.](https://help.gocapable.com/diagrams/bpmn-token-simulation.html)

[Colour BPMN elementsHighlighting without breaking the notation.](https://help.gocapable.com/diagrams/colour-bpmn-elements.html)

[BPMN editorBack to the editor overview.](https://help.gocapable.com/diagrams/bpmn-editor.html)

---

_Simulate it before you publish it._