# Architecture

## **DocBits Cloud customer**

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-84a4ad8ff56a4779e5f4cee37b01d1fbe29077a7%2Fimage.png?alt=media" alt="DocBits Cloud Customer Architecture"><figcaption></figcaption></figure>

## DocBits On premise

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-eb8289d0d7c4f9781ae16960e0ec3bef975e76b3%2Fimage.png?alt=media" alt="DocBits On Premise Architecture"><figcaption></figcaption></figure>

Doc**Bits** seamlessly integrates with Infor LN/M3 through ION API, ION Desk, and Infor Standard BODs. Our API integration allows us to export data to Infor and perform master data validation in Doc**Bits**.

## **DocBits Operator Architecture**

All connections between components are secured using industry-standard encryption protocols. SSH, HTTPS, and other secure channels ensure data integrity and confidentiality throughout the system.

**On Premise:**

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-47863c6c69d2efe6ed657b55ea2058b9f90315f1%2FOperator_On-Prem.png?alt=media" alt=""><figcaption></figcaption></figure>

{% content-ref url="architecture/prefect-local-setup-requirements" %}
[prefect-local-setup-requirements](https://docs.docbits.com/overview-and-basics/architecture/prefect-local-setup-requirements)
{% endcontent-ref %}

**Cloud**:

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-3eaf3a85aa3cd96829d617b37268edc45ae2263c%2FOperator%20Cloud%20.png?alt=media" alt=""><figcaption></figcaption></figure>

## Exporting Data to Infor

We use the ION API to send the PDF with attributes to IDM and the BOD Sync.CaptureDocument to ION Desk. In ION Desk, we transform the [Sync.CaptureDocument](https://docs.docbits.com/infor-integration-and-configuration/exporting-in-docbits) to the desired target BODs based on the document type being processed. These transformed Infor BODs are then automatically imported to LN or M3.

{% hint style="info" %}
Export to [Infor](https://docs.docbits.com/infor-integration-and-configuration/exporting-to-infor)
{% endhint %}

## Master Data Validation in DocBits

To identify the supplier or compare/match purchase order lines, we activate a trigger in LN/M3 that sends the Sync.RemitToPartyMaster, Sync.SupplierPartyMaster, and Sync.PurchaseOrder BODs to Doc**Bits**. We configure this process in ION Desk by defining the dataflow to a specific connection point to Doc**Bits**.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-347f504c6a34003468369c3fab9e6e2ab3fa9292%2Fdocbits_architecture.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
[Master Data Validation](https://docs.docbits.com/infor-integration-and-configuration/importing-customer-master-data)
{% endhint %}

## Email Import OAuth Office365

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-cfd8be409f7999b310d33eb698f4613a9a3f1511%2Fo365_architecture.png?alt=media" alt=""><figcaption></figcaption></figure>
