Introduction#
The Exception Management is mainly composed by two objects: a Protocol, which represents a given workflow, amd a Protocol Instance, which is a run-time occurrence of the workflow (modeled as a Protocol) and it can be associated with one or more Materials.
A Protocol translates a state model where you can write changes in each stage of the state model. Similarly to the state model, the Protocol outlines a given workflow, which is composed off different states whose execution can be restricted to those who belong to a specific role. Additionally, the Protocol also offers the possibility of adding several parameters in each state, as well as checklists.
The execution of a Protocol will be done through a Protocol Instance, where the system creates an executable object from its main entity (Protocol). The Protocol is seen as a template from where the instances are being replicated.
Protocol Lifecycle#
The table below summarizes the key states in the Protocol lifecycle, describing their system state and what can be configured in each one of those states:
| State | Description |
|---|---|
| Created | Protocol is created and can be configured to be used. |
| Effective | Protocol is configured and ready to be used. |
| Terminated | Protocol can no longer be used. |
Protocol Instance Lifecycle#
The Protocol Instance system state lifecycle defines the different stages a Protocol Instance goes through from creation to closure.
graph TD
Start -.->|Create|A1[Active]
A1 -->A2[Terminated]
classDef mermaid_start color:#000, fill:#fafafa, stroke:#fafafa, color:#fafafa, stroke-width:0x, font-size:100%, visibility: hidden;
classDef mermaid_state fill:#274b76, stroke-width:0px, color:#fafafa, font-size:100%;
class Start mermaid_start
class A1,A2 mermaid_state
| State | Description |
|---|---|
| Active | Protocol Instance is opened. |
| Terminated | Protocol Instance is closed. |
Info
To continue learning, proceed to Creating a Protocol.