# 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).

![](/files/VHvFsbaNsdhevPFe51mY)

**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": [
        "INSTALLER"
      ],
      "uiMetaData": {
        // In this example, INSTALLER would be able to access two tabs.
        "type": "tabs"
      },
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guardian.hedera.com/guardian-dev/guardian/standard-registry/policies/policy-creation/creating-a-policy-through-policy-configurator/policy-workflow-step-8.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.