This article provides an in-depth understanding of the DocumentsCorePack online service structure, deployed on Microsoft Azure. We will walk you through the document generation process, from the initial request for a document to the final document available in the Dynamics 365 environment.
Please refer to Figure 1 for a schematic representation of the DocumentsCorePack Online Scheme:
1) Initiating a document generation request: You can manually dispatch document generation requests through our user-driven document generation dialog. You can also trigger them from within Power Automate (Flows) or Dynamics 365 Processes using our Process integration. Every document generation request creates a record of the so-called AutoMergeWorkingItem table.
2) Push Request to Document generation service in the Cloud:
When you save the AutoMergeWorkingItem, this calls a specific web URL, signaling the cloud service about the new document generation request in the Dynamics 365 environment. Notably, there is no data transfer at this point.
3) Document Generation:
The cloud service, securely communicating with Dynamics 365 web services using methods provided by the Dynamics 365 SDK (TLS 1.2, OAuth authentication), loads the template and the necessary data from Dynamics 365 to create the requested document. The VM hosting the cloud service does not store any information unless you have activated debugging. If activated, this could result in Dynamics 365 data appearing in debug files (access for customers and support team, automatically deleted after 7 days).
4) Document Return to Dynamics 365:
The generated document is securely transmitted back to Dynamics 365 via web services using methods provided by the Dynamics 365 SDK (TLS 1.2, OAuth authentication). The document is not stored on the VM at any point.
Please note:
- We employ Server-to-Server authentication or App-Access for communication between the cloud service and Dynamics 365, thereby eliminating the need for login credentials storage.
- Our Azure account hosts the document generation service. To guarantee high performance, the service will be located in the same data center as the Dynamics 365 instance.
IMPORTANT: For clients with specific security considerations, DCP offers the flexibility of installation on their own Azure VM or local hardware. This eliminates the need to transfer any data to mscrm-addons.com. However, to ensure optimal performance, we recommend installation on the VM.
The installation can be done directly from our website.
That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.