Overview
This guide explains how State Categories and States work in your application, how workflows are managed across record types, and how business processes can be modeled through these structures.
Each record type (e.g., Document, Nonconformity) has its own State Category, and multiple States can be defined under each category. This structure allows organizations to model their processes flexibly and traceably.
State Management Structure
What is a State Category?
A State Category is a predefined classification for the States of a specific record type (e.g., Document, Nonconformity).
- Each record type can have multiple State Categories.
- State Categories are defined by the system and cannot be changed by users.
- Under each category, users can define as many States as they need.
Key Points:
- State Categories group and classify States for the same record type.
- They are not used to separate States of different record types but to organize potential States within a single record type.
Examples:
- Document State Categories: Draft, Opinion, Control, Approval, Published, Cancelled
- Nonconformity State Categories: Draft, OpenApproval, ProgressReport, RootCauseActionPlan, CloseProgressReport, CloseApproval, Closed
What is a State?
A State represents a specific state in the lifecycle of a record (e.g., "Operational", "Completed").
- Each State belongs to a State Category.
- Users can define new States under an existing category.
- Each State can be configured with additional properties such as allowed transitions, whether notifications or task assignments are triggered, etc.
Sample State Categories and State Chart
⚠️ Warning:
The following examples may not exactly match the definitions in the application. They may vary depending on your organization’s processes.