πŸ’»User Guide

1. Step By Step Process

  1. Click β€˜Discontinue’ button for the policy in policies list

  1. Policy can be marked β€˜discontinued’ immediately (chose β€˜Immediate’ option) or automatically at a later date (β€˜Deferred’ option)

  1. In the UI policies, which were set to discontinue immediately are displayed with the red color in the status block and policies which are set to deferred discontinue are displayed with the gold warning color in the status block.

  1. Discontinue actions in the UI triggers the issuance of the [deferred-]discontinue-policy messages in the corresponding policy topic

  1. Discontinued policy is displayed with a red bar in the UI. For these policies the creation of new documents for users/sensors is not disabled. Policies which are set to discontinue later (β€˜deferred’) are displayed with a yellow warning bar

  1. When a policy has been discontinued users can migrate data to another (currently active) policy

Migration steps order:

  1. Policies: Select the source and the destination policy.

  2. VP Documents : Select VPs which are to be migrated from the source policy.

  3. VC Documents : Select VCs which are to be migrated from the source policy.

  4. Schemas : Map the source policy schemas with the destination policy schemas.

  5. Roles : Map source policy roles with the destination policy roles.

  6. Groups : Map the source policy groups with the destination policy groups.

  7. Tokens: Map the token templates

  8. Blocks : Block mapping (while state migrating is enabled)

  9. Clicking OK you will start an asynchronous migration task

  1. When the task completes, a success or warning (in case of issues) notification is displayed.

2. Demo Video

Youtube

Last updated