> 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/command-centre-client/quick-tips-for-configuring-the-event-occurrence-time-filter.md).

# Quick Tips for configuring the 'Event Occurrence Time' filter

* When creating an Activity Report, by default the **Event Occurrence Time** filter is already added. You can edit this instance of this filter condition, but will not be able to add another instance of it.
* **Report Period:**

  The ‘Report Period’ controls allow you to enter a start and end time for the report. Pre-defined periods are provided for simplicity, or custom start and end times can be entered.
* If you select **This Week** or **Last Week** for the 'Report Period', an additional 'Week Start Day' drop-down appears, allowing you to select the appropriate day for the first day of the week.

  The 'Start Date' and 'End Date' will both match the 'Week Start Day'. Selecting User Settings rather than a day from the drop-down list allows you to change the 'Start Date' and 'End Date' to different days of the week.

  ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-2501b29fc4460c62d16304370e06656918f4434c%2Freport_eventoccurencetime_weekstartday.png?alt=media)
* The default value for **Last \[n] hours** is set as "8" hours (valid range is 1 - 999), with the idea that at a shift change an operator may want to run a report based on however many hours the last shift was. A standard shift would normally be 8 hours, hence the 8 hour default setting.
* The “Filter Days” area can be expanded by clicking the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-896b081fa28b003ad94ed8ff39ddc852cff42812%2Fhoverarrow.png?alt=media) at the right of the grid. When expanded, Filter Day sliders display to allow for specific day filtering.
* Day filtering can either be done on All Days or individual days. To define times for specific days of the week, uncheck the **All Days** slider which is enabled by default.
* Clicking on a Filter Day slider opens a time box to allow selection of the time period to be included in the report.

  ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-bd00be25fc7e4d84204418be3f56b82c41345232%2Ffilterdayslider.png?alt=media)

  Editing the time period in the **All Days** slider will duplicate the start and end times in the days **Monday** through **Sunday**. This allows you to set the start and end times ONCE in the **All Days** slider, and then make small adjustments to specific days by unchecking the **All Days** slider and adjusting one or more of the individual day sliders.
* Multiple active periods within each day can be achieved by subsequent clicking inside the slider.

  ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-cce5e9d5b50fe5a7bf2428783154051230a734b3%2Ffilterdayslider2.png?alt=media)
* Checking the **Allow change when report is run** checkbox allows the filter to be edited at runtime.


---

# 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/command-centre-client/quick-tips-for-configuring-the-event-occurrence-time-filter.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.
