# Policy Workflow Step 17

Next, we need to add an information block to our policy to specify what happens if the application is rejected by clicking on the information button in the top navigation bar.

We then name the block through the tag, set permissions, activate by default such that rejection notifications are caught, stop the process if received, and then name the notification and define the message.

![](/files/LaJwIjUITLPVREifUJ76)

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

```
    // Block to display rejection info (i.e. the INSTALLER was not approved by StandardRegistry).
    {
      "tag": "installer_rejected",
      "blockType": "InformationBlock",
      "children": [],
      "uiMetaData": {
        "type": "text",
        "description": "Your application was rejected",
        "title": "Rejected"
      },
      "stopPropagation": true,
      "permissions": [
        "INSTALLER"
      ],
      "defaultActive": true
    }
  ]
},
```

This completes the installer steps of the policy.


---

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