Explain the differences between Process-Centric Design and Record-Centric Design.
Answer
Aspect | Process-Centric Design | Record-Centric Design |
|---|---|---|
Primary focus | Process/workflow | Business data/entity |
Main object | Process Model | Record Type |
Data approach | Data moves through process variables and activities | Data is stored and accessed through records |
User interaction | Users interact mainly through tasks/forms | Users interact through record views, actions, and related data |
Best for | Workflow automation and approvals | Data-driven applications and managing business entities |
Example | Employee submits request → Manager approves → HR processes | Employee record containing profile, department, requests, and history |
Process dependency | Application is driven by the workflow | Application is driven by the business data |
Appian approach | “What needs to happen?” | “What data do we need to manage?” |
Process-Centric Design
The application is built around process models (workflows) as the primary driver. Users interact mainly through tasks generated by processes.
Characteristics:
- Workflow‑driven: The process model dictates the sequence of steps.
- Task‑oriented UI: Users see and act on tasks in their task list.
- State tracking: The process instance holds the state of the work.
- Data storage: Often stored in process variables or related DB tables.
- Access: Users typically access data via process reports or task forms.
Pros:
- Good for strictly sequential workflows.
- Easy to enforce business rules and approvals.
- Clear audit trail in process history.
Cons:
- Less flexible for ad‑hoc actions.
- Harder to change mid‑process without restarting or migrating instances.
- 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:
- Data‑driven: The record is the single source of truth.
- Action‑oriented UI: Users interact with records and trigger actions as needed.
- State tracking: The record’s fields reflect the current status.
- Data storage: Centralized in a database or Appian Data Store.
- Access: Users can view, search, and filter records easily.
Pros:
- Flexible — supports ad‑hoc and non‑linear workflows.
- Easier to maintain and extend.
- Better for case management and self‑service scenarios.
- Records remain accessible even if no active process is running.
Cons:
- Requires careful design to ensure data integrity.
- Less prescriptive — may need more governance to ensure process compliance.
- Complex workflows may require multiple related actions and process coordination.