Docatomicsecurity
Class: metadata
Atomic security for documents provides more granular control, based on lifecycle state and role, over who can perform specific lifecycle user actions like changing document state and starting a workflow. For example, the Editor role may be able to start the Review workflow, but not the Expedited Approval workflow.
Learn more about Atomic Security for Documents in Vault Help.
| Attribute | Metadata | Description |
|---|---|---|
label | Type: String Max length: 60 | UI-friendly string in the Vault's base language. |
active | Type: Boolean | Indicates whether the field is active. |
document_lifecycle | Type: Component Required | Indicates the lifecycle that atomic security applies to. |
state | Type: String Required Max length: 1500 | Indicates the lifecycle state that atomic security applies to. |
Docworkflowactionsecurity
Section link for DocworkflowactionsecurityAtomic security for documents provides more granular control, based on lifecycle state and role, over who can perform specific lifecycle user actions like changing document state and starting a workflow. For example, the Editor role may be able to start the Review workflow, but not the Expedited Approval workflow.
| Attribute | Metadata | Description |
|---|---|---|
label | Type: String Max length: 60 | UI-friendly string in the Vault's base language. |
active | Type: Boolean | Indicates whether the field is active. |
role | Type: String Required Max length: 1500 | Indicates the role override that the permission applies to. |
type | Type: Enum Required Allowed values:
| Indicates the permission type. |
workflow_actions | Type: Enum Multi-value Allowed values:
| Indicates the active workflow action that the permission applies to. |
workflow_task_actions | Type: Enum Multi-value Allowed values:
| Indicates the active workflow task action that the permission applies to. |
Docactionsecurity
Section link for DocactionsecurityAtomic security for documents provides more granular control, based on lifecycle state and role, over who can perform specific lifecycle user actions like changing document state and starting a workflow. For example, the Editor role may be able to start the Review workflow, but not the Expedited Approval workflow.
| Attribute | Metadata | Description |
|---|---|---|
label | Type: String Max length: 60 | UI-friendly string in the Vault's base language. |
active | Type: Boolean | Indicates whether the field is active. |
role | Type: String Required Max length: 1500 | Indicates the role override that the permission applies to. |
type | Type: Enum Required Allowed values:
| Indicates the permission type. |
lifecycle_actions | Type: String Max length: 1500 Multi-value | Indicates the user action that the permission applies to. |
Supported Operations
Section link for Supported Operations| Operation | Support |
|---|---|
| Create | |
| Recreate | |
| Alter | |
| Drop | |
| Rename | |
| Describe | |
| Generate Recreate | |
| Queryable |
Notes:
- Alter: MDL Operation may not be supported for some multi-value attributes.