Business Processes
CityScreen Deals includes a built-in BPMN 2.0 process engine. A business process is a workflow that the organization models once and the engine executes every time — assigning tasks to people, sending emails, creating documents, updating records, and moving deals through stages without manual coordination.
The process automation module must be enabled for the organization by CityScreen staff before it becomes visible. Once enabled, the Business Processes and Tasks sections appear in the main navigation.
What the engine covers
The engine is a full BPMN 2.0 runtime. The entire standard BPMN palette is available in the diagram editor — gateways, timer events, signal events, sub-processes, boundary events, and more.
Three element types have a guided interface that presents CityScreen Deals concepts directly:
-
User Task — assign work to an employee, pick candidate groups, attach a form.
-
Service Task — call a CityScreen Deals entity service (create a document, update a customer) or send documents by email.
-
Script Task — write and preview a script.
Everything else on the palette is configured in the generic properties panel, where the designer edits the element’s BPMN attributes directly. Using these elements effectively requires familiarity with BPMN notation.
Core concepts
| Concept | Meaning in CityScreen Deals |
|---|---|
Process |
A reusable workflow definition — a BPMN diagram with its tasks, gateways, and events. Each process belongs to one organization and can be activated or deactivated independently. |
Version |
Every time a process is published, a new version is created. Running instances are not affected by a new version — they finish on the version they started on. |
Process instance |
A single run of a process definition. The top-level navigation calls these "Instances"; the per-process tab calls them "Executions" — both labels refer to the same thing. See terminology for the full disambiguation. |
Task |
A unit of human work created by the engine when a process reaches a user-task step. The engine assigns the task to an employee or offers it to an employee group. Tasks appear on the Tasks page and are completed through forms. |
Incident |
An error recorded when a process step fails at runtime — for example, a script error or a failed email delivery. To recover from an incident, migrate or delete the affected instance. |
Form |
A set of fields presented to the employee when they open a task. Forms are defined separately, deployed to the engine, and referenced from user tasks in the diagram. |
Section overview
| Page | What it covers |
|---|---|
The diagram editor, autosave, and the difference between guided and generic elements. |
|
Assigning work to employees and groups, attaching forms, and how candidate groups resolve to employee groups. |
|
Calling CityScreen Deals entity services and sending documents by email from a process. |
|
Writing and previewing scripts, and the difference between the browser preview and the production engine. |
|
Draft, publish, version history, and migrating running instances to a new version. |
|
Manual start, automatic start on entity events, and controlling who can launch a process. |
|
The task list, opening a task, filling the form, and completing it. |
|
Viewing running instances, reading incident details, and recovering from failures. |