> 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/code-hooks-6182369.md).

# Code Hooks

JobManager offers a range of *Hooks*, which can be used as desired.

A *Hook* is a call to a *Codeunit*. This call is triggered many places in the JobManager module.

This table provides the ability to change which *Codeunits* to run.

Using this option **avoids** changes to JobManager objects, making updating JobManager versions much easier.

The lines in this table is [automatically created](https://docs.dynalogic.com/birds-jobmanager-product-overview/getting-started/foundation-setup-guide.md).

*Hooks* kan be used in combination with [Custom Fields](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/custom-fields-6182361.md) or [Custom signing functions](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/custom-signing-functions-6182359.md).

{% hint style="info" %}
**As of NAV 2016 it's recommended to use&#x20;*****Events*****.** All *Hooks* are also available as *Events* in NAV 2016. In addition, there are even more *Events* available. Codeunit *6182705 JobManNavEnventPublisher* has a complete list of *Events*.
{% endhint %}

{% hint style="info" %}
If JobManager is installed as an *Extension* on **Dynamics Business Central** only the **Events** could be used. The *Hooks* are obsolete!
{% endhint %}

**The installation package for JobManager contains some examples.**

**Also see** [**here**](https://docs.dynalogic.com/birds-jobmanager-product-overview/architecture-and-development-guidelines/code-customization.md)**!**

| Topic                         |
| ----------------------------- |
| [Ref. Object Type](#field-1)  |
| [Ref. Object ID](#field-2)    |
| [Ref. Object Name](#field-7)  |
| [Key](#field-11)              |
| [Key 2](#field-12)            |
| [Key 3](#field-13)            |
| [Active](#field-20)           |
| [Run Object Type](#field-101) |
| [Run Object ID](#field-102)   |
| [Run Object Name](#field-107) |

## See also

[JobManager Foundation Setup Guide](https://docs.dynalogic.com/birds-jobmanager-product-overview/getting-started/foundation-setup-guide.md)\
[Code customization](https://docs.dynalogic.com/birds-jobmanager-product-overview/architecture-and-development-guidelines/code-customization.md)

## Reference

\
\\

<details>

<summary>Ref. Object Type</summary>

Identification of the object that triggers the *Hook*.

</details>

<details>

<summary>Ref. Object ID</summary>

Identification of the object that triggers the *Hook*.

</details>

<details>

<summary>Ref. Object Name</summary>

Identification of the object that triggers the *Hook*.

</details>

<details>

<summary>Key</summary>

Further identification of the object that triggers the *Hook*.

It is often the name of a Function.

</details>

<details>

<summary>Key 2</summary>

Further identification of the object that triggers the *Hook*.

It is often the name of a Function.

</details>

<details>

<summary>Key 3</summary>

Further identification of the object that triggers the *Hook*.

It is often the name of a Function.

</details>

<details>

<summary>Active</summary>

Indicates whether the line is active, and therefore included.

</details>

<details>

<summary>Run Object Type</summary>

Object to be called when triggered.

</details>

<details>

<summary>Run Object ID</summary>

Object to be called when triggered.

</details>

<details>

<summary>Run Object Name</summary>

Object to be called when triggered.

</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/code-hooks-6182369.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.
