Modeling a Process
The diagram editor is where a business process takes shape. It provides the full BPMN 2.0 element palette and a drag-and-drop canvas for building workflows.
Creating a business process
Open Business Processes and create a new process. The only required field is the process name. You can also set a description, an assignee (the process owner, used for filtering the process list), and employee groups.
The new process starts with no diagram. When you open the Diagram tab for the first time, the editor loads a minimal starter diagram with a single start event.
The element palette
The editor offers the standard BPMN palette — start and end events, gateways (exclusive, parallel, inclusive, event-based), intermediate catch and throw events (timer, message, signal, escalation, compensation), boundary events, sub-processes, call activities, and all task types.
Three task types have a guided side panel built specifically for CityScreen Deals:
| Task type | What the guided panel provides |
|---|---|
User Task |
Dropdowns for assignee and candidate groups, a form picker, and name and description fields. See user tasks and forms. |
Service Task |
A catalog of CityScreen Deals entity services and actions, with auto-filled input and output parameters. See service tasks. |
Script Task |
A code editor with syntax highlighting and a browser-based preview runner. See script tasks. |
Every other element type — gateways, events, sub-processes, boundary events, send tasks, receive tasks, manual tasks, business rule tasks, and more — is configured through the generic properties panel. The generic panel shows the element’s process attributes directly: expressions, listeners, input and output mappings, timer definitions, signal references, and so on. Using these elements effectively requires working knowledge of BPMN 2.0 notation and of these attributes.
Autosave and manual save
While the diagram is open, the editor periodically saves the current state as a draft. The draft is saved with the process and is not deployed to the engine — it has no effect on running instances or on the published version.
You can also save the draft manually at any time.
The editor requires the diagram to contain an executable process. If the process element is not marked as executable, saving is rejected.
Draft and published state
A process can be in one of two states:
-
Draft — the diagram has been edited but not yet published. The draft is visible only in the editor and does not affect the engine.
-
Published — the diagram has been deployed to the engine as a new version.
When you open the editor on a process that has both a draft and a published version, you see the draft. To discard the draft and revert to the last published version, use the rollback action.
See publishing and versions for the full publish, version, and migration workflow.