🎓Policy Glossary
Next, we discuss the terms that need to be understood to create Policies within the Guardian framework:
Term | Definition | Example |
---|---|---|
Block | Either a Policy Workflow or a Policy Action | MRVDataVerification (Policy Workflow) |
| Defines a list of Blocks that are grouped into a Policy Workflow | List of Blocks |
| Determines if Policy Workflow or a Policy Action can be executed |
|
| Security Policy associated with a specific role |
|
| Specifies the type of Policy Workflow or Policy Action |
|
| Specifies the data of the policy workflow and/or Policy Action to be displayed |
|
| Specifies the ID of a policy action which can be referenced in other blocks as a dependency |
|
| Defines the data schema for a block |
|
| Specifies the Type of data used in the Block |
|
| Specifies which blocks | See |
| Available roles from which the user can choose. |
|
| Go back one step to enable the creation of the previous object. |
|
| End processing here, don't pass control to the next block. |
|
| Gives the document a label in the DB. Needed for filtering. |
|
| Adds new Document |
|
| List of attributes, which is added to the VC when it is being persistent. Can be used for more flexible filtration. | "name": "status" "value": "Minted", |
| Type of Document | VC/VP/DID |
| Specifies Topic Name | topic |
| Specifies a person, who will be next Owner | Owner/Policy Owner |
| Specifies a person, who will be Signer | owner / Policy Owner |
| Specifies whether a block applies to only those documents owned by the role specified in |
|
| Specifies documents in the Grid with status timeline |
|
| Specifies if the error has occurred in the Block | Retry/Go to step/Go to tag |
| Specifies which VC should be assigned to the user |
|
Last updated