Policy Workflow Step 8

Next, we want to add another step to our policy action. To do this we again go back to the Policy Action itself by clicking on the โ€œinit_installer_stepsโ€ Policy Action icon on the left.

At this point, we need to create a sub Policy Action process as a dependent workflow. We can always do this by adding a container block by clicking on the โ€œContainerโ€ button in the top navigation bar.

We now configure this new container block through the โ€œTagโ€, Permissions, setting the Default Active (since this step must be initiated), and selecting the UI type (TABS in our case since we will have to fill in different types of information in different sections).

Programmatically this workflow step looks like this:

   // Create an InterfaceContainerBlock to group all pages accessible after registration is completed.
      "blockType": "InterfaceContainerBlock",
      "tag": "installer_header",
      "defaultActive": true,
      "permissions": [
      "uiMetaData": {
        // In this example, INSTALLER would be able to access two tabs.
        "type": "tabs"

Last updated