> 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/parameters.md).

# 9A Raptor DWH Parameters

The 9A Raptor Document Warehouse parameters view allows an administrator to manage all configuration related to Raptor. It can be accessed via 9A Raptor DWH > Setup > 9A Raptor DWH parameters.

## General <a href="#general" id="general"></a>

### Enable HTTP Logging <a href="#general-enable-http-logging" id="general-enable-http-logging"></a>

See [Inquiries and reports](https://docs.dynalogic.com/birds-document-warehouse-product-overview/d365-finance-and-operations/inquiries-and-reports.md#http-logging)

### Timeout <a href="#general-timeout" id="general-timeout"></a>

Sets the timeout in milliseconds for outgoing network requests.\
When set to 0, it defaults to 100000 (100 seconds).\
This setting can be put higher in case you encounter timeout errors.

### Use Key Vault <a href="#general-use-key-vault" id="general-use-key-vault"></a>

**Azure Key Vault Integration Overview**

Azure Key Vault is supported for storing secret keys and passwords for integrations. This section describes its setup in D365 F\&O. For integration-specific settings, refer to the related documentation.

**Key Resources for Azure Key Vault**

* [Azure Key Vault Documentation | Microsoft Docs](https://docs.microsoft.com/azure/key-vault/)
* [Set Up Azure Key Vault Client - Dynamics 365 | Microsoft Docs](https://docs.microsoft.com/dynamics365/)
* Best Practices for Azure Key Vault Usage

**Key Considerations**

* **Resource Groups**: Resource group usage varies by customer policies.
  * Use separate resource groups for **non-production** and **production** environments.

**Setting Up Azure Key Vault for D365 F\&O**

1. **Create an Azure Key Vault**.
2. **Register an Azure App** and generate a **secret key**.
3. **Create an Access Policy** in the Key Vault and link it to the App registration.

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

**Adding New Secrets**

The creation of secrets depends on the modules the customer has purchased. It is recommended to use the following names, but custom names can be used if necessary:

* **ContextManagement**: Secret key for access to Document Warehouse.
* **OutputManagementDox42**: Client secret for the Dox42 Azure App registration.
* **OutputManagementDox42User**: Password of the user account linked to Dox42.
* **OutputManagementSmartFlows**: API key for access to SmartFlows.
* **ProcessManagementAgilePointUser**: Password of the user account linked to AgilePoint.

**Configuring Azure Key Vault in D365 F\&O**

Once the steps above are completed, configure Azure Key Vault in D365 F\&O as follows:

1. **Set the Default Company**: Set the company to **DAT** for Azure Key Vault parameters. The Key Vault parameters are stored per company, but the Raptor parameters are stored globally.
2. **Access Key Vault Parameters**:
   * Navigate to **System Administration** > **Setup** > **Key Vault Parameters**.
   * Create a new Key Vault setup with the name **'RaptorKeys'**.
   * Enter the following required parameters:
     * **Key Vault URL**: The Vault URI (can be found in the Azure Key Vault Overview).
     * **Key Vault Client**: Application ID of the App registration used for authentication between D365FO and Azure Key Vault.
     * **Key Vault Secret Key**: The secret key from the App registration (step 2).
3. **Create New Secrets**:
   * The secret names must match the proposed names below to ensure proper integration. The "Secret" field in D365FO should match the secrets created in Azure Key Vault (step 3). Set the **secret type** to 'Manual'.
     * **RaptorDocumentManagementSecret**
     * **RaptorOutputManagementDox42Secret**
     * **RaptorOutputManagementDox42UserPwd**
     * **RaptorOutputManagementSmartFlowsSecret**
     * **RaptorProcessManagementAgilePointUserPwd**
   * Format the **Secret URL** as: `vault://keyVaultName/keyVaultSecretName`.

**Activating Azure Key Vault Integration in 9A Document Management**

After the setup is complete, activate the Azure Key Vault integration:

1. Navigate to **9A Raptor DWH Parameters** via **9A Raptor DWH** > **Setup**.
2. Enable **Use Key Vault** and complete the necessary parameters for existing integrations, including endpoints and user accounts.

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

## Document management <a href="#document-management" id="document-management"></a>

### Setup <a href="#document-management-setup" id="document-management-setup"></a>

The document management integration can be activated through the following path:

**9A Raptor DWH** > **Setup** > **9A Raptor DWH Parameters** – tab **Document Management**.

After onboarding, an external system and secret key are provided for the F\&O environment. The URL remains the same for all customers, as **Document Warehouse** operates as a single multitenant environment.

<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-fa410b80a3724ba5139d13140de6b1a33ad866e6%2Fimage%20(274).png?alt=media" alt=""><figcaption></figcaption></figure></div>

A **service account** (the 'On behalf of' parameter) is required for all communication between D365 F\&O and the Raptor API. The service account should be a user in Raptor and assigned the 'D365-FO' external system (see [External Systems](https://docs.dynalogic.com/birds-document-warehouse-product-overview/setup-and-configuration/external-systems.md)).

### General <a href="#document-management-general" id="document-management-general"></a>

**Tag documents outside FO**

{% hint style="info" %}
This setting is deprecated and might cause issues when used in combination with cascading tag relations. Please use [#document-management-distribution-setup](#document-management-distribution-setup "mention") instead.
{% endhint %}

For standard D365FO flows, documents attached through document handling (e.g., from a sales order) are automatically copied to related records like sales order confirmation journals or sales order invoice journals. When this parameter is enabled, documents that aren’t directly added to document handling but are available in the **Document Warehouse** will be searched and tagged with the appropriate label (e.g., sales order confirmation, invoice, etc.).

**Distribution Setup**

**Processing Mode Options:**

* **None**: No document distribution is performed.
* **Synchronous**: Documents are tagged or copied to a new tag within the same thread (real-time processing).
* **Asynchronous**: Documents are tagged or copied to a new tag in a separate thread (background processing).

## Output management <a href="#output-management" id="output-management"></a>

In **9A Raptor DWH > Setup > 9A Raptor Document Warehouse parameters**, you are able to configure providers for document creation outside of the standard SSRS or Business Documents.

Options are:

* SmartFlows
* dox42 (recommended by 9A)
* XperiDo

### SmartFlows <a href="#output-management-smartflows" id="output-management-smartflows"></a>

To connect to a SmartFlows environment, you need to provide the environment URL (<https://your-company.smartflows.xpertdoc.eu>) as well as an API Key, generated in the SmartFlows administration console.

### dox42 <a href="#output-management-dox42" id="output-management-dox42"></a>

To connect to a dox42 environment, you need to provide the environment URL (<https://your-company.dox42.online/dox42restService.ashx>).

Next to the environment an Azure app registration needs to be created as well as a service account to communicate with a linked SharePoint instance (which holds the document templates).

To create the app registration, follow these steps:

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

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

The value for the redirect URL is customer specific and will be provided after a new Dox42 environment has been ordered. This typically is https\://\<customername>.dox42.online

Make sure a secret key is generated in the Certificates & secrets tab.

In the API permission section make sure the following permissions are set:

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

Don't forget to grant administrator access!

### XperiDo <a href="#output-management-xperido" id="output-management-xperido"></a>

To use XperiDo as an output provider, the related configuration key should be activated via configuration key Ex Arte Raptor > Output management. This configuration key Is disabled by default. As XperiDo is end-of-life, this is only supported for existing XperiDo customers.

To activate XperiDo, fill in the URL, username and password for the XperiDo webservice.

### Enable report logging <a href="#output-management-enable-report-logging" id="output-management-enable-report-logging"></a>

The 'Enable report logging' setting can enabled to log all requests to the output providers. This setting can be useful for troubleshooting. The logs are written to the report at 9A Raptor DWH > Inquiries and reports > Output management > Report logging.

### Archiving processing mode <a href="#output-management-archiving-processing-mode" id="output-management-archiving-processing-mode"></a>

The 'Archiving processing mode' setting can be used to change the behaviour of the archiving of generated documents. If the 'Save in 9A Raptor DWH' option is set in the print destination settings and the destination is not '9A Archive' itself, then the 'Archiving processing mode' has an effect.

<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-6bbb71e164bbbe1635b5cd6b95fdc899c4d607f6%2FS541lFnYnz.png?alt=media" alt="" width="328"><figcaption></figcaption></figure></div>

The 'Archiving processing mode' options are:

* Synchronous: Archiving is done immediately after printing.
* Asynchronous: After printing, the archiving request is put in a queue table.
* Synchronous outside transaction: After printing and if the code is running inside a transaction, then the archiving request is put in a queue table. If the code is not running inside a transaction, then the archiving is done immediately after printing.

An example flow of the 'Synchronous outside transaction' is the intercompany direct delivery flow where the intercompany sales order invoice triggers the sales order invoice of the end customer that can be set to be printed during posting.

If the setting is not set to 'Synchronous', then the asynchronous part needs to be scheduled using [#Archive queued reports](https://docs.dynalogic.com/birds-document-warehouse-product-overview/d365-finance-and-operations/output-management.md#archive-queued-reports)


---

# 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/parameters.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.
