Requirements

To support a deployment of Smart Flows, your servers must meet minimum hardware and software specifications. This section covers requirements for both the Smart Flows application server and the associated SQL database server.

Smart Flows Server Hardware Requirements

Although it's possible to run Smart Flows and its database server on one machine, for performance reasons it is always preferred to separate the components. Generally, only customers with a small implementation and one environment can install on one machine.

When using multiple environments (Production, Development, TEST, UAT, etc), we recommend a separate server for non-production environments.

Experlogix Smart Flows Server Minimum Requirements

Component

Hardware Requirement
Operating System Windows Server (2016+) with AD FS 4.0+
Processor Dual-core
RAM 8GB
Disk Space <500MB

We recommend using the AdoptOpenJDK 21 LTS build using the Hotspot VM, select here to download.
Please contact Experlogix Support if you need help in updating Java.

Experlogix Smart Flows Server Software Minimum Requirements

Software Requirement
.NET Framework: 4+

Java: Java SE Development Kit 21 or higher

Smart Flows Database Requirements

Experlogix Smart Flows Database Server Minimum Requirements

Component

Hardware Requirement
Operating System Windows Server (2016+) with AD FS 4.0+
Processor Quad-core
RAM 8GB
Disk Space Dependent on the size and amount of documents generated and the scheduled cleanup
Generated documents of 150kB are stored on the database for 30 days and you generate 2000 documents a day. You will need approximately 9GB to store those documents.
Experlogix Smart Flows Database Server Software Minimum Requirements

Software Requirements
SQL server version 2016 or later
Smart Flows requires a SQL Server authentication-based user
TCP/IP must be enabled, with a fixed TCP/IP port
Connect via a JDBC Connection String, username, and password

OAuth Permissions for Microsoft Dynamics 365 CE Connector

For Microsoft Dynamics 365 CE, a service account is necessary when configuring the connector. Client ID and secret are not supported. Smart Flows uses user delegation. This allows Smart Flows to access data from Microsoft Dynamics 365 CE on behalf of the end user.

Required Permissions

  • Read permissions for every entity that you want to use in your flows and templates.

  • Permission to create a letter, e-mail activity, task, and note regarding any of those entities.

  • Full control for the Smart Flows Configuration entity created by our managed solution (another way of doing this is by giving the Smart Flows Admin role to the service account).

  • If you want to use the e-mail for Microsoft Dynamics 365 CE flow block to send e-mail on another user's behalf see - Power Platform | Microsoft Learn to send e-mails in the name of those users.

  • The delegate role to allow the service account to act on behalf of the user.