> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-systems/schindlerid/the-call-manager-interface-plugin/configuring-secure-free-floors/configuring-the-reporttimepatterns-registry.md).

# Configuring the 'ReportTimePatterns' Registry

To enable Time Pattern status reporting you will need to create the registry entry 'ReportTimePatterns' on the middleware PC.

To create the 'ReportTimePatterns' registry, perform the following procedure:

1. From the Start menu, click **Run...**
2. Type in 'regedit' and click **OK**.

   The Registry Editor opens.
3. Path your way to HKEY\_LOCAL\_MACHINE\SOFTWARE\Gallagher\Command Centre

   **Note:** If using a 64 bit system, browse to HKEY\_LOCAL\_MACHINE\SOFTWARE\Wow6432Node\Gallagher\Command Centre
4. Right click, and then click **New** from the drop-down menu. Another drop-down menu displays. Click **DWORD Value**. Your new DWORD Value is populated at the bottom of the registry values list.
5. Enter the DWORD Value name 'ReportTimePatterns'.
6. Double-click your newly created DWORD Value.

   The **Edit DWORD Value** window displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-74621fbfe7de256930fd4332d670e6f49611aa41%2Fschindler_registrykey.png?alt=media)
7. Select **Decimal** as the Base then enter a value, (e.g. 1) and click **OK**.

   **Note:** If a value is not entered or the 'ReportTimePatterns' entry is not defined, Time Pattern status reporting will not be supported.


---

# 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://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-systems/schindlerid/the-call-manager-interface-plugin/configuring-secure-free-floors/configuring-the-reporttimepatterns-registry.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.
