> 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-document-warehouse-product-overview/d365-business-central/jobmanager.md).

# JobManager

Raptor can be integrated with Jobmanager, ensuring that people on the shopfloor have access to important documents when executing a job.

## 9A Raptor Integration Setup <a href="#id-9a-raptor-integration-setup" id="id-9a-raptor-integration-setup"></a>

Makes sure 'Enable JobManager Management' is on to enable the integration with JobManager.

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

## JobManager Integration

### 1. 9A Raptor Integration Scenarios

Two integration scenarios are available to ensure the integration with Jobmanager.

#### JobMan Job

JobManager operates on the same underlying records as Production Orders, Assembly Orders, Service Orders, and Projects. To avoid the need for separate entity configurations, the JobManager integration uses static impersonation. This allows JobManager pages to reuse the existing Raptor integration of the underlying Business Central document, ensuring that the correct documents are displayed without additional configuration. As a result, the 9A Raptor viewers displayed within JobManager automatically inherit the context of the originating document (Production, Assembly, Service, or Project).

To enable this integration, you need to set up the JobMan Job integration scenario. It is not necessary to set up new API fields and integration. When the JobMan Job scenario is enabled, this will just activate the viewer on Jobmanager and refer to the correct integration scenario connected to the page.

**When the JobMan Job integration scenario is enabled, the JobManager job lists are mapped to the following Raptor entities:**

Production Job list: productionOrderRouting

Project Job list: projectPlanningLines

Service Job list: serviceLines

Assembly Job list: assemblyOrderLines

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

#### JobMan Stamp Journal

The JobMan Stamp Journal refers to the 9A Viewer on the Active Jobs tile. This scenario also uses static impersonation, and reuses the existing Raptor integration.

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

## JobManager Comment Factbox

9A Raptor Document Warehouse integrates directly with the JobManager Comment FactBox. This works in both directions.

Raptor -> Comment Factbox: When a document is added to the Raptor viewer on a JobManager page (Production Jobs, Project Jobs, Service Jobs, Assembly Jobs, or Active Jobs), a corresponding linked record is automatically created in the JobManager Comment FactBox.

Comment Factbox -> Raptor: When a user adds a document through the JobManager Comment FactBox using the Add Image action, the document is automatically uploaded to Raptor Document Warehouse. The document is created with the correct metadata and tags based on the current context.

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

### 1. Setup

#### Comments Setup List

To enable the integration with the JobManager Comment FactBox, additional setup is required on the Comments Setup List page.

For each relevant job type, a line must be created that links the job type to the codeunit responsible for synchronizing documents with the Comment FactBox (codeunit = 2112963).

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

#### 9A Raptor Integration Scenarios

On the JobMan Job integration scenario, it is important that the toggle 'Save attachments to Raptor Side' is enabled.

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


---

# 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-document-warehouse-product-overview/d365-business-central/jobmanager.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.
