Tagsecurityrule
Class: metadata
Internal Vault developers use Tag Security Rules to control access to records. External developers cannot create custom Tag Security Rules, but they can create Tagsecurityruleassignment subcomponents to map Tagsecurityrules to Objects. This allows assignments to be moved between Vaults using migration packages (VPKs).
| Attribute | Metadata | Description |
|---|---|---|
label | Type: String Max length: 60 | UI-friendly string in the Vault’s base language. |
active | Type: Boolean | Indicates whether the component is active. |
allow_custom_objects | Type: Boolean Required | If true, the rule can be applied to custom objects. |
description | Type: String Max length: 255 | A general description of the rule. |
help_content | Type: String Max length: 255 | UI-friendly help string. |
Tagsecurityruleassignment
Section link for Tagsecurityruleassignment| Attribute | Metadata | Description |
|---|---|---|
label | Type: String Max length: 60 | UI-friendly string in the Vault’s base language. |
active | Type: Boolean | Indicates whether the component is active. |
object | Type: Component Required | Reference to the Object component. An object can only be included in one Tagsecurityrule. |
Supported Operations
Section link for Supported Operations| Operation | Support |
|---|---|
| Create | |
| Recreate | |
| Alter | |
| Drop | |
| Rename | |
| Describe | |
| Generate Recreate | |
| Queryable |
Notes:
- Recreate, Alter: MDL Operation is supported only to create or alter custom subcomponents.