Object state types enable Admins to identify specific states across object lifecycles, or even across all object lifecycles in a Vault, that should have common behaviors.
Note: This article explains how to create custom object state types. For help associating object state types to object lifecycle states, see Configuring Object Lifecycles.
About Object State Types
By default, each object lifecycle initially has two state types associated with it: Initial and Complete. You can create custom object state types in object lifecycle configuration.
For example, an organization might create the custom object state type “Approved”, defined by the Admin with a scope of Available to all lifecycles. This means that the “Approved” state type is available to add to any object lifecycle in the Vault. An Admin is then able to create a state type to lifecycle state association for “Approved” with any object lifecycle.
Other Vault functionality, such as distribution of data and reporting, can then leverage the “Approved” object state type, and would therefore apply to every object record in an associated state across multiple object lifecycles. Furthermore, the state types are leveraged by many cross-Vault connections. In QMS-Regulatory, for example, state types are used as a trigger to indicate when data should be transferred between Vaults without requiring extensive re-configuration of the existing lifecycles.
Within an object lifecycle, a state could be associated with multiple state types. For example, the “Approved” state in the “Deviation Approval Lifecycle” could be associated with both the “Steady State” state type, as well as the more specific “Deviation-Approved” state type. However, within an object lifecycle, only one state could be associated with a specific state type, for example, only one state could be associated to the state type “Complete”.
To create a new object state type:
- Navigate to Admin > Configuration > Object State Types.
- Click Create.
- Enter a Label and Name.
- Select a Scope. Selecting Applies to all lifecycles ensures this state type appears in every object lifecycle, including pre-existing object lifecycles. Select Available to all lifecycles to make this state type appear as an option when creating a new state type association. Select Specific lifecycle if this state type only applies to a single object lifecycle.
- Choose whether the state type is required or not. A required state type must have an associated state in all lifecycles in which it appears. By default, Vault associates the Initial state with the required state type.
- Optional: Enter a Description. This value only appears in the lifecycle configuration pages.
- Select a Status from the drop-down.
- Optional: If you selected the Specific lifecycle scope, you must select an existing object lifecycle from the Lifecycle drop-down.
- Click Save.
About Active and Inactive Object State Types
Object state types have a status flag to indicate Active or Inactive. Only Active state types are available for making a lifecycle state and state type association.
You must have the following permissions to configure object state types:
Admin: Object Lifecycles
To create and modify object state types, you must have a security profile which grants Create and Edit permissions for Object Lifecycles.