We are working on the best option for connecting K2 Cloud to an premise SQL server or potentially Azure SQL server . At a high-level, we are designing a process for the client that will engage an OCR reader to extract data from an invoice then a bot verifies the information on the invoice is correct and approves and pays invoice if correct. If it is not correct, the bot will toss an exception to K2 with data from the invoice along with a pdf copy for a manager to update information or approve the invoice. We are now looking to leverage an intermediary SQL database where UiPath can enter the data for the exception and then K2 can read the details from there for the manager to update or approve.
We need K2 assistance with determining the best approach for connectivity to the intermediary SQL database. Below are my thoughts/questions on our options for connecting K2.
On-premise SQL connectivity options:
- SDA – additional license fee; we would like to avoid this option if possible
- Site to Site VPN
- Opening Network Firewall Ports
- Placing Systems in a DMZ
If we were to decide on any of the three options besides SDA, how does the data get transferred to and from K2? Is there any API option or secure data transfer to help protect data in flight?
Azure SQL connectivity options:
- Create an Azure SQL Database
How would the communication work between client and K2?
Bottom line, we need a secure method of connecting and transferring data from K2 Cloud to the client environment
