> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/deploy/configuration/hcm-ui-configuration/attendance-management/attendance-package-extraction-and-interaction-with-hcm-application.md).

# Attendance Package Extraction & Interaction with HCM Application

## Interaction With Attendance Package

Below is the diagram of the components that are in the DIGIT HCM app and attendance package, and how the interaction happens:

<figure><img src="/files/qgyDR9q1u1KrN1w2ueWk" alt=""><figcaption></figcaption></figure>

## New Files / Changes Required In HCM App

1. Add the attendance package dependency in pubspec.
2. Create a bloc that extends the attendance listener class and creates the override methods.
3. Create model classes that import attendance models and add a companion class.
4. Create local and remote repositories as per project requirements and structure.
5. Add a typedef for repositories in untils/typedef.
6. Initialise repo in network manager, and create oplog.
7. Create SQL tables in case of offline.
8. Add navigation to manage the attendance page from the HCM app, and pass the required fields.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digit.org/health/deploy/configuration/hcm-ui-configuration/attendance-management/attendance-package-extraction-and-interaction-with-hcm-application.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.