Experlogix Smart Flows 4.19.0

In Microsoft Dynamics 365 CE, when viewing a custom currency field on Contacts as a sample and when that field exceeds 10 million, the format is displayed incorrectly with a dot after the first number and an E7 at the end of the string. After the fix, Microsoft Dynamics 365 CE users see custom currency values displayed as expected, regardless of length.

In Flow Builder, users with a Create task flow block linked to an Accounts data set in Sugar observed that the Due delay value was not applied during the flow execution. This resulted in the task due date and start date being equal to the current date. After this fix, the Create task flow block correctly applies the Due date delay value when executing the flow.

In Flow Builder, when an E-mail (Salesforce) flow block is configured to send an e-mail, but the checkbox is not selected to create an activity, the flow execution produces an error. E-mails are treated as activities in Salesforce, so if you attempt to send an e-mail from Salesforce without creating an activity, the process fails since it can't save it back to the activity manager. After this fix, the system provides a better error message to indicate the cause of the issue and that the field is required; see E-mail (Salesforce) for more details.

When attempting to run a flow within Microsoft Dynamics 365 F&O, some users experienced a 404 error. This error was only replicated on data sets for Sales orders with a nested custom relationship. After this fix, users no longer receive a 404 error, and the data from the flow displays as expected.

We've added the ability for users to export their flow execution data from the Reporting dashboard in Project Console. Users can now export all flow execution data or export several filters such as statuses, users, flows, or the classification; see Reporting for more information.

In Template Builder, some users experience an issue when connecting via Salesforce; the system does not display the expected templates. Additionally, when users refresh the connection, they receive an Internal server error message. After the fix, affected users see templates display as expected and can refresh their connection to the Salesforce connector.

In Flow Builder, users with complex expressions with pseudo relations in Template Builder experienced an error where their data would not consistently output to the document. This was due to the complex interaction between the expression and the Field Reducer in Flow Builder. We recommend using the Data Set Optimizer instead and disabling the Field Reducer to ensure consistent data outputs.

In Flow Builder, the system throws an error when a user sets Flow Settings to "Ask questions first" and has an Approve Document flow block in their flow. This error is due to the system's inability to "Ask questions first" and complete the Approve document flow block since they are both user-input actions. The system cannot request document approval as a part of "Ask questions first" since the document has not been generated yet. We've updated the error message to indicate that the two are mutually exclusive; you can disable Ask questions first" or remove the Approve Document flow.

We have improved our interface to indicate when a generated document is no longer available due to clean-up actions. When reviewing the Generate document flow block, unavailable documents have an eraser icon. When selecting a link for unavailable data or documents, the system displays the error messages "Your data has been cleaned up" or "Your document has been cleaned up." Finally, for Flow Execution Panel, when a document is unavailable due to clean up, the error message " Failed to download the document..." shows instead, "The data and the document was intentionally removed for security purposes."

In Project Console, a limited set of users experienced an error in the Data set builder where one entity with a 1:N relationship was displayed only on the backend, not the front-end. The root cause was how the data set was sorting the entities. After this fix, the ordering of the data set no longer affects whether the entity displays.

In Flow Execution Panel UI Settings, some users experienced issues switching their Interface language from English to French or French to English; only some interface parts were translated. After this fix, users see consistent and complete user interface translations based on their Interface Language selection.

In Project Console, some users experienced a CORS A page refers to a part of the interface that causes a change to the final part of the URL forward slash without using a # error when running flows from Microsoft Dynamics 365 CE if they had an invalid Salesforce connector in the project. This error was due to the flow execution incorrectly targeting the invalid connector. We've added a validation check on the displayname for connectors, and flows for valid connectors will work as expected.

In Flow Builder, some users with advanced flows experienced an error when creating an Occurs condition—specifically, an Occurs condition with two subconditions: one on Account and the other on Account number. When the user attempts to edit either subcondition, the mapped field for the subcondition selected for editing is switched to the other mapped field, such as Account being switched for Account Number, and vice versa. After this fix, when editing these subconditions, the mapping only changes as the user directs.

In Project Console, when importing a flow, the system does not throw an error when importing a flow into the project without the required HTTP connector. After this fix, all future imports where the flow calls for an HTTP connector that is not in the project will produce an error to notify the user of the missing HTTP connector.

In Flow Builder, when running a flow, so long as watermarks are applied to the generated documents, they do not count towards the license limit. To ensure Designers know whether a test will count toward the license, we've added a message that displays when watermarks are disabled to indicate that the flow run will count towards the document license limit.

In Flow Builder, users can configure a flow to automatically remove all data that a flow has received and any documents generated after each successful flow run. By default, this setting is unchecked for all flows; for more information, see Settings and Flow Settings.

We've added the ability to retrieve documents from the FilePicker field in an Xpertdoc Portal Smart Form. Any flow block that accepts a document as input can leverage the FilePicker field. However, only one document can be received per field. For more information, see Linked Fields and Use a Document from a Smart Form.

In Project Console, some users experienced errors when generating or previewing documents for a Salesforce connector. The root cause of the issue was that when a field was deleted in Salesforce, it still displayed in the Smart Flows data set. This mismatch also caused the Data Set Optimizer user interface to fail when viewing the affected data sets, resulting in an infinite spinning wheel. After this fix, the system will indicate which field is missing without causing the Data Set Optimizer to fail.

In Project Console, Administrators can submit a request to modify the number of users or total documents associated with their product plan. This allows you to increase the scope of your license within your existing product plan with a minimal increment interval of 5,000 for documents. See Licensing for how to complete the request.

TheStore in Microsoft SharePoint flow block previously allowed entire XML documents to be passed to the flow block parameters. If a large enough document was passed, it could shut down the connection manager and require a manual restart. We've set a 435-character limit for the Store in Microsoft SharePoint flow block to prevent an accidental shutdown of the connection manager.

Smart Flows now supports individual user authentication for SharePoint and Docusign connectors. This authentication pattern replaces authentication through a service user that is authenticated during connector setup (either with or without impersonation of the active user). Users will be asked to authenticate individually when they run a flow containing a step related to the SharePoint or Docusign connector, after which an authentication token will be stored for them. Tokens expire after a preset number of days. They can be revoked by the user in Flow Execution Panel or by an administrator in Project Console. This new authentication pattern can be switched on or off at the connector level. Admins can also define behavior for flows running in non-interactive mode; see Individual User Authentication for more information.

When triggering a flow from a host system, some users experienced an error where the E-mail (Dynamics) flow block failed to retrieve and apply XML data from an early flow blow to the "From" field. This error was due to the system's inability to resolve the XML into an entity reference. After this fix, the affected users' E-mail (Dynamics) flow block completes sending the e-mail without producing an error.