> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/planned-jobs-absence-6182605.md).

# Planned Jobs/Absence

JobManager offers the opportunity to assign a specific job to an employee for a given period. In this period the employee is only required to clock-in and clock-out. This opportunity is available in the Registration Cockpit and Registration Client.

Absence can be entered in advance, for one employee by adding a line, or for multiple employees by selecting *multi create* (e.g. vacation).

It is possible to requets and enter Absense with time. This allows more types of Absense at the same day.

In case of illness (Or other absence) you can mark [*auto stop*](https://documentation.jmgapp.dk/en-us/T_6182605_40). Then the absence (illness) will continue until the next clock-in registration occurs from the employee.

Planned abcence is shown in the Absence list in the *Registration approval* and \*Time Calculation approval.

There is a field on the line with Planned absense, that makes it possible to hide the absense from the employee.

It is possible to have a permanant absence (e.g. flex/time off). If the employee has absence, it will automatically be filled with the selected "job". The *Start time* and *End time* must be blank, and every other absence must be *prioritized*.

There is an option for overlap of absences by using the field [Prioritized](#field-7).

| Topic                           |
| ------------------------------- |
| [Type](#field-1)                |
| [Number](#field-2)              |
| [Start time](#field-4)          |
| [End time](#field-5)            |
| [Prioritized](#field-7)         |
| [Recurring Interval](#field-16) |
| [Job Id](#field-20)             |
| [Stamp Type](#field-22)         |
| [Request](#field-30)            |
| [Request Date](#field-31)       |
| [Reply Date](#field-32)         |
| [Reply User Name](#field-33)    |
| [Auto stop](#field-40)          |
| [Stopped](#field-41)            |
| [Description](#field-220)       |

## See also

[Planned Absence](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/planned-absence-6182606.md)\
[Registration approval](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/registration-approval-6182765.md)\
[Time Calculation and Approval](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/time-calculation-and-approval-6182701.md)

## Reference

[JobManager Job](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-job-6182601.md)\
[IPC Activity](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/ipc-activity-6182343.md)

\
\\

<details>

<summary>Type</summary>

Indicates the type of relation for [Number](#field-5).

**Related topics**

* [JobManager Employee](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-employee-6182311.md)

</details>

<details>

<summary>Number</summary>

Indicates the related number depending on [Type](#field-1):

| Type     | Number       |
| -------- | ------------ |
| Employee | Employee No. |

**Related topics**

* [JobManager Employee](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-employee-6182311.md)

</details>

<details>

<summary>Start time</summary>

Time from where the line starts.

</details>

<details>

<summary>End time</summary>

Time to where the line ends.

</details>

<details>

<summary>Prioritized</summary>

Check the first priority absence type if there is an overlap in the periods.

</details>

<details>

<summary>Recurring Interval</summary>

Ability to set automatic recurring. Specify for example **8D** the line will continuously be automatically copied/forwarded *8 days* ahead.

**Related topics**

* [Update Recurring Job](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/update-recurring-job.md)

</details>

<details>

<summary>Job Id</summary>

The field is a unique id for the associated job. All jobs are created in [this table](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-job-6182601.md).

**Related topics**

* [JobManager Job](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-job-6182601.md)

</details>

<details>

<summary>Stamp Type</summary>

Type of the related registration:

* Work
* Absence
* Break
* Trigger Code

</details>

<details>

<summary>Request</summary>

Status for the [request for planned absence](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/planned-absence-6182606.md).

**Related topics**

* [Planned Absence](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/planned-absence-6182606.md)

</details>

<details>

<summary>Request Date</summary>

Date where [request for planned absence](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/planned-absence-6182606.md) where sent.

**Related topics**

* [Planned Absence](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/planned-absence-6182606.md)

</details>

<details>

<summary>Reply Date</summary>

Date where [request for planned absence](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/planned-absence-6182606.md) where answered.

**Related topics**

* [Planned Absence](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/planned-absence-6182606.md)

</details>

<details>

<summary>Reply User Name</summary>

Shows who has approved/rejected the [absence request](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/planned-absence-6182606.md).

</details>

<details>

<summary>Auto stop</summary>

If selected the job continues until the employee clocks in next time after the Start Time. Could be used for example: illness, maternity leave etc.

</details>

<details>

<summary>Stopped</summary>

Indicates when the job was stopped. Set if [Auto stop](#field-40) has occurred.

</details>

<details>

<summary>Description</summary>

[Decription](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-job-6182601.md#field-10) of the related Job.

</details>


---

# 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://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/planned-jobs-absence-6182605.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.
