> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/dineplan/backoffice/automation/clock-information.md).

# Clock Information

### **Overview** <a href="#overview.6" id="overview.6"></a>

The Clock Information feature allows users to view clock-related information recorded in the system. Users can filter the displayed records by Name and a specific date range using the "From" and "To" fields.

The results are displayed in a table with details such as Code, Employee, Type, and Date, making it easier to review clock information for a selected employee and period.

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-2f41a38240bdbbcec7af7df48cdd98d67d733145%2Fimage%20(149).png?alt=media" alt=""><figcaption></figcaption></figure>

### **Screen Elements** <a href="#screen-elements.6" id="screen-elements.6"></a>

| **Screen Element** | **Description**                                                |
| ------------------ | -------------------------------------------------------------- |
| Name               | Allows you to specify the employee name to filter the records. |
| From               | Specifies the start date for the search.                       |
| To                 | Specifies the end date for the search.                         |
| Code               | Displays the code associated with the clock record.            |
| Employee           | Displays the employee associated with the record.              |
| Type               | Displays the type of clock record.                             |
| Date               | Displays the date of the clock record.                         |
| Close              | Closes the Clock Information screen.                           |

### **Working** <a href="#working.6" id="working.6"></a>

1. Enter the required employee name in "Name", if required.
2. Select the start date in "From".
3. Select the end date in "To".

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-9c3a8d4d7caee2d26252cdee7eecd5f04bec19e9%2Fatt_61_for_3422715932.png?alt=media" alt=""><figcaption></figcaption></figure>

4. The clock information matching the selected criteria is displayed in the table.
5. Review the clock records under "Code", "Employee", "Type", and "Date".

<figure><img src="https://3400173661-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0EE0WqKESoD8hlEpFQQL%2Fuploads%2Fgit-blob-f07a9c47a161ed720af8627083794029264d51ef%2Fatt_62_for_3422715932.png?alt=media" alt=""><figcaption></figcaption></figure>

### **Use Case** <a href="#use-case.6" id="use-case.6"></a>

* Review clock information for a specific employee.
* View clock records for a selected date range.
* Check the employee associated with a clock record.
* Review the type of clock record recorded for an employee.
* Identify the date associated with a clock record.

### **Notes** <a href="#notes.6" id="notes.6"></a>

* The "From" and "To" fields can be used to specify the required date range.
* The displayed records include "Code", "Employee", "Type", and "Date".


---

# 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.rbsgo.com/dineplan/backoffice/automation/clock-information.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.
