DependencyDesigns
Offers a visual or structural representation of Vault dependencies for configuration items, useful for system design audits and maintenance assessments.
Columns
| Name | Type | Description |
| ID | String | Unique identifier for the dependency design entry, used to distinguish it from all other records within the system. |
| Dependency_Design_Type | String | Specifies the classification of the dependency design, such as section dependency, question dependency, or checklist dependency, indicating how conditional logic is applied. |
| Name | String | Descriptive name of the dependency design, used to identify the purpose or intent of the dependency configuration. |
| Status | String | Indicates the current state of the dependency design, such as Active, Inactive, or Draft, to help determine its readiness for use. |
| Created_By | String | Username or identifier of the user who initially created this dependency design record. |
| Created_Date | Datetime | Timestamp recording the date and time when this dependency design was first created in the system. |
| Last_Modified_By | String | Username or identifier of the user who last updated the dependency design record. |
| Last_Modified_Date | Datetime | Timestamp reflecting the most recent update made to this dependency design. |
| Behavior | String | Defines how the dependent element behaves based on the controlling element, such as visibility toggling or conditional requirement. |
| Checklist | String | Name or identifier of the checklist that includes this dependency, if the dependency applies to a checklist context. |
| Controlling_Question | String | Identifier or label of the question that determines the condition under which the dependent element is triggered. |
| Dependent_Question | String | Identifier or label of the question that is affected by the controlling question based on the defined behavior. |
| Answer | String | The specific answer value or values from the controlling question that trigger the behavior on the dependent question or section. |
| Dependent_Section | String | The form section that becomes active or hidden depending on the specified answer to the controlling question. |
| Lifecycle | String | Name of the lifecycle associated with this dependency design, linking the logic to a specific document or data process lifecycle. |
| Lifecycle_State | String | Current lifecycle state in which the dependency design is active, such as Draft, Approved, or Retired, helping to scope the logic within defined workflow stages. |