#Process master data

A process's master data says who owns it, what it is for and whether Chester may run it, independently of the diagram itself.

#What a process page holds

A process opens on four tabs:

Comments on the process open in a side panel, next to all four tabs.

#Decide whether a process is executable

The Executable switch is the most important piece of master data. It decides whether the process is only documented or can also run.

flowchart TD
  P[Process] --> Q{Executable?}
  Q -- "no" --> Doc["Documentation only"]
  Q -- "yes" --> Exec["Executable"]
  Doc --> D1["Diagram with documentation fields only"]
  Doc --> D2["No validation, no forms"]
  Doc --> D3["Can be deployed as a version"]
  Doc --> D4["Cannot be started"]
  Exec --> E1["Full configuration: systems, forms, conditions"]
  Exec --> E2["Validated while you model"]
  Exec --> E3["Deploys only when valid"]
  Exec --> E4["Can be started once deployed to production"]

A documentation-only process is for describing how work is done without automating it — as a reference, for training, or as a first step before automation:

• The diagram shows only the documentation properties of each element. System, form and condition settings are hidden, because nothing would ever use them.
• It is never validated, and always counts as valid.
• The Forms tab stays empty and asks you to mark the process as executable first.
• You can still deploy it. The deployment records the process as it stands as a version, just as for an executable one.
• It is never offered to anyone to start.

An executable process shows every setting, is validated while you model, and can only be deployed when the validation passes. To be started from the Execution app it also needs a production deployment and a plain start event.

You can switch a process between the two at any time on its Details tab.

#Set the owner and tags

Every process has exactly one owner. Tags are shared with systems, so the same tag can mark a process and the system it depends on.

#Keep track of versions

The Versions tab lists every deployment, grouped by production and development. Each save is also kept as a version in the background, but the process page cannot show or restore those yet. See Keep track of versions and deployments.

#Edit without overwriting each other

Only one person edits a process at a time. Whoever clicks Edit first holds the process; everyone else sees who that is and can only read until they are done. See Edit without overwriting each other.

#Discuss a process

Comments open in a side panel next to every tab. Mention a colleague with @ to notify them. See Comment on a process.