chesterdocs

#Reference

The reference collects the terms Chester uses and what each one means, so any page can be read on its own.

#How the main terms relate

flowchart TD
  Proj[Project] --> Area[Process area] --> Grp[Process group] --> Proc[Process]
  Proc --> Dep[Deployment] --> Inst[Instance]
  Sys[System] --> Ad[Adapter] --> Act[Action]
  Sys --> Env[Environment] --> Cred[Credential]
  Proc -. "service task uses" .-> Act

See also Limits and Validation messages.

#Glossary

Term Meaning
Project The top level of the process hierarchy. See Organise your work.
Process area A topic inside a project that bundles process groups.
Process group Groups related processes within a process area.
Process One business process — master data, diagram, forms and versions. See Process master data.
Executable A process Chester may run. Otherwise the process is documentation only.
Element One shape in the diagram: an event, a task, a gateway. See Process elements.
Expression A small piece of code that computes a value while the process runs. See Expressions.
Form What a person fills in at the start or in a user task. See Forms.
System An external application a process talks to. See Systems and adapters.
Adapter How Chester connects to a system — REST, webhooks, GraphQL or email.
Action One operation an adapter can perform, such as "fetch customer".
Environment One installation of a system — development, test or production — with its own address. See Environments and credentials.
Credential The secret an environment uses to sign in to a system.
Deployment A frozen, runnable version of a process, to development or production. See Deploying a process.
Instance One run of a deployed process. See Monitoring.
Agent An AI model with tasks, tools and knowledge, run as a process. See Agents.
Knowledge vault Notes an agent reads, and may write. See Agent knowledge vaults.
Catalog The list of processes offered to a set of people in the Execution app. See Running processes.