> 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-finance-and-operations/process-management.md).

# Process Management

This document provides an overview the existing features for the Process Management solution.

## Activation module

Via the module 9A Raptor DWH > Setup > 9A Document Management parameters – tab Process Management can the process integration activated by choose a supported provider. The Process management solution supports two providers at this moment: Business events and AgilePoint. When you want to work with AgilePoint, please activate the Active checkbox and fill the necessary parameters in the group Setup. These fields aren’t used if you want to work with business events.

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

To activate the process integration, navigate to the **9A Raptor DWH > Setup > 9A Raptor Document Warehouse Parameters** and select the **Process Management** tab.

The **Process Management** solution currently supports two providers:

1. **Business Events**
2. **AgilePoint** **NX**

To use **AgilePoint NX** as the provider, follow these steps:

* Check the **Active** checkbox.
* Fill in the required parameters in the **Setup** group.
  * **URL**: e.g. <https://as.nxone.eu>
  * **Portal URL**: e.g. <https://app.nxone.eu>
  * **Username**: Service account (ensure you include the domain) e.g. `nxone\user`
  * **Password**: The password for the specified service account

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

## Functionalities

The following functionalities are available in the **Process Management** solution when used in combination with the **Input Management** solution. Each functionality indicates which process provider is supported.

1. **Start Process**:\
   Initiates a new process and stops the current process.\
   *Supported by all process providers.*
2. **Cancel Process**:\
   Stops the current process.\
   *Supported by all process providers.*
3. **Open Process**:\
   Provides an overview of the current process.\
   *Supported only by AgilePoint.*

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

Imported invoice data includes two process fields:

* **Current Process Status**: Displays the status of the current process.
* **Process Actual User**: Displays the user currently responsible for the process.

These fields enable the creation of custom views with filters, allowing you to:

* View and manage **open processes**.
* Identify the **responsible user** for each invoice.

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

## Process comment integration

You can add comments before starting or cancelling a process. These comments are stored with the corresponding imported invoice.

Before using this functionality, ensure that it is activated in the **9A Raptor Document Warehouse Parameters**.

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

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

## Actor Integration

The **Process Management** solution supports six actors by default:

* **First 2 Actors**: These represent the **vendor responsible** and **purchase requesters**.
* **Remaining 4 Actors**: These are optional actors that can be manually populated in your imported invoices.

To apply this feature to existing invoices, simply **reinitialize** the invoices, and the default actors will be automatically filled in.

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

## Process history integration

The **Process Management** solution supports **history tracking**, which logs changes made to a process through Power Platform or AgilePoint.

The purpose of this functionality is to provide end users with a clear overview of the changes and actions that occur during the flow of the current process. By tracking these changes, users can easily understand the process progression and identify what has happened at each stage.

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

The current **history table** includes four fields that are available for logging changes during the process. These fields are **free-text** and do not have any validation or relationships with other existing tables. The fields are as follows:

1. **Created Date and Time**: The timestamp indicating when the change was made.
2. **Status**: A description of the current status of the process at the time of the change.
3. **Actual User**: The user responsible for the change or action at that point in the process.
4. **Comment**: A free-text field where additional context or notes about the change can be added.

## Developing workflows

To develop workflows using the Process Management entities in Finance & Operations, see the development reference in **Integrations and Technical Reference**:

{% content-ref url="/pages/myVOGpBMz2Ul94A6qGjg" %}
[Process Management](https://docs.dynalogic.com/birds-document-warehouse-product-overview/integrations-and-technical-reference/d365-finance-and-operations/process-management.md)
{% endcontent-ref %}


---

# 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-finance-and-operations/process-management.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.
