> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/3.5.1/guardian/standard-registry/policies/policy-creation/creating-a-policy-through-policy-configurator/policy-workflow-step-13.md).

# Policy Workflow Step 13

Since this is a cyclic step, we need to add the requirements as sub-steps to be completed in each cycle, and an exit condition.

We add the first sub-step by clicking on the “Request” button in the top navigation bar.

Again we add a tag, set the permissions, make this step active by default since it is required, select the schema type of the document – inverter in this case since we are adding an inverter sensor, and select the Id Type, since sensors are given DIDs, we select DID.

Next, we select the UI as a “Dialog” as we have done before from the drop-down. We then add content and title.

![](https://content.gitbook.com/content/EvaEsaNo09Ib5tjr1yj1/blobs/Xl7B5UTQYQh0CVpxXY8L/PW_image_19.png)

**Programmatically this workflow step looks like this:**

```
              "children": [
                // Button to create new sensor.
                {
                  "tag": "add_sensor_bnt",
                  "defaultActive": true,
                  "permissions": [
                    "INSTALLER"
                  ],
                  "blockType": "requestVCDocumentBlock",
                  "schema": "9d31b4ee-2280-43ee-81e7-b225ee208802",
                  // Generate new DID for the new sensor.
                  "idType": "DID",
                  "uiMetaData": {
                    // Open the a dialog containing the new sensor.
                    "type": "dialog",
                    // Text on the button.
                    "content": "New Sensors",
                    //Button style.
                    "uiClass": "btn",
                    //Dialog title.
                    "dialogContent": "New Sensors",
                    //Description.
                    "description": "Description",
                    //Dialog style.
                    "dialogClass": ""
                  }
                },
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guardian.hedera.com/docs/3.5.1/guardian/standard-registry/policies/policy-creation/creating-a-policy-through-policy-configurator/policy-workflow-step-13.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.