Process-Centric Design

The application is built around process models (workflows) as the primary driver. Users interact mainly through tasks generated by processes.

Characteristics:

1. Workflow‑driven: The process model dictates the sequence of steps.
2. Task‑oriented UI: Users see and act on tasks in their task list.
3. State tracking: The process instance holds the state of the work.
4. Data storage: Often stored in process variables or related DB tables.
5. Access: Users typically access data via process reports or task forms.

Pros:

1. Good for strictly sequential workflows.
2. Easy to enforce business rules and approvals.
3. Clear audit trail in process history.

Cons:

1. Less flexible for ad‑hoc actions.
2. Harder to change mid‑process without restarting or migrating instances.
3. Can become process‑heavy and harder to maintain at scale.

Record-Centric Design

The application is built around Records as the primary object. Processes are supporting actions (Related Actions) triggered from the record.

Characteristics:

1. Data‑driven: The record is the single source of truth.
2. Action‑oriented UI: Users interact with records and trigger actions as needed.
3. State tracking: The record’s fields reflect the current status.
4. Data storage: Centralized in a database or Appian Data Store.
5. Access: Users can view, search, and filter records easily.

Pros:

1. Flexible — supports ad‑hoc and non‑linear workflows.
2. Easier to maintain and extend.
3. Better for case management and self‑service scenarios.
4. Records remain accessible even if no active process is running.

Cons:

1. Requires careful design to ensure data integrity.
2. Less prescriptive — may need more governance to ensure process compliance.
3. Complex workflows may require multiple related actions and process coordination.