> 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/available-entities-operations.md).

# Available entities: operations

This page describes the entities regarding operations, such as projects, production, assemby and service.

Raptor is now integrated with projects, production, assembly and service in BC. The functionalities are available on the following entities.

## Projects (jobs)

Project Card list and card

* Documents linked to the general project order

Project Task Lines

* Navigate to documents linked to a certain task of the project with the 'View Line documents' button
*

```
<figure><img src="../../.gitbook/assets/image (5).png" alt=""><figcaption></figcaption></figure>
```

Project Planning Lines

* Navigate to documents linked to the planning lines of the project. The viewer is available on both the general overview of all the planning lines of the project, and the planning lines of a certain task
*

```
<figure><img src="../../.gitbook/assets/image (8).png" alt=""><figcaption></figcaption></figure>
```

*

```
<figure><img src="../../.gitbook/assets/image (10).png" alt=""><figcaption></figcaption></figure>
```

It is also possible to create purchase orders and sales invoices directly from the project card. You can add the project number to the entity configuration of both the purchase order and the sales invoice ('NAL Job No.'). This allows the project number to be included as a tag on the generated documents.

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

## Production

Production Order list and card

* Documents linked to the general production order
* Raptor functionalities available on the following types of orders
  * Planned Production Order
  * Firm Planned Production Order
  * Released Production Order
  * Finished Production Order (archive page)

Production Order Lines

* Navigate to documents linked to a certain line with the 'View Line documents' button

Production Component Lines

* Navigate to documents linked to the components of a certain production order line by clicking on the components action on the line.

Production Routing Lines

* Navigate to documents linked to the routing of a certain production order line by clicking on the routing action on the line.

## Assembly

Assembly Order list and card

* Documents linked to the general assembly order

Assembly Lines

* Navigate to documents linked to a certain line with the 'View Line documents' button

## Service

Service Order list and card

* Documents linked to the general service order

Service Order Lines

* Navigate to documents linked to a line on the service item worksheet (Lines > Line > Service Item Worksheet > Lines > manage > View Line Documents)

Service Item Lines

* Navigate to documents linked to a certain line on the service order with the 'View Line documents' button (Lines > manage)


---

# 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/available-entities-operations.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.
