The password must contain at least an uppercase letter, a lowercase letter, a number, and one special character.
|
2.
|
Update the Admin User. |
During initialization, you are asked to upload a license. This step is optional; you can upload a license later using the Control panel tab. To generate a valid license, you need the project ID. To get the license
Contact our Client Success Team.
|
4.
|
(Optional)Set up the primary connector. |
You can connect any of our available support connectors, depending on your license. Your license determines which connectors you can add—such as Microsoft Dynamics 365 CE, Sugar, or Salesforce. While you can use multiple connectors, only one of each type is supported. The setup wizard guides you through the connection process. See Connectors for coverage on all of our supported connectors.
For Microsoft Dynamics 365 CE authentication, refer to Configuring OAuth2.0 for Microsoft Dynamics (2016+).
For Configuring OAuth2.0 for Microsoft Dynamics 365 CE, refer to Authenticating your connector.
Adding more Smart Flows Projects
To test or develop multiple Smart Flows project instances, you can replicate the setup process for each project using different configuration values. This guide walks you through adding another project instance.
|
1.
|
Copy and update the application.properties file for the new project. |
|
2.
|
Update the port number. See the Prerequisites topic for valid ranges. |
Where users will access Smart Flows
1
2
3
4
server.port=1443
project.baseurl=https://xsfl-server:1443
1
2
3
4
5
server.ssl.key-store=..\yourpfxfile.pfx
server.ssl.key-store-password=yourpfxpassword
server.ssl.key-store-type=pkcs12
Set Database Connection
Database connection for test instance
1
2
3
4
5
project.datasource.jdbc-url=jdbc:sqlserver://localhost;database=smartflows-test
project.datasource.username=sa
project.datasource.password=secretsapassword
Set Admin Password
Default admin password for this instance
1
2
3
sample.user.password=secretadminpassword
|
3.
|
Update the smartflows-server.xml file: |
|
3.1.
|
Rename the service ID to match the new project name. |
|
3.2.
|
Rename the service name to reflect the new environment. |
|
3.3.
|
Update the port number to match the value in application.properties. |
You should now be able to launch the new project instance and verify its connectivity through the assigned base URL and port.