Experlogix Smart Flows 4.25 Release Notes
This page provides release notes for the entire 4.25 release of ExperlogixSmart Flows, including the major release version 4.25.0 and all subsequent minor releases.
Current Version: 4.25.0 on 02/09/2025
Previous Versions: 4.24.2 on 06/05/2025
Download Installers
Experlogix Smart Flows 4.26 Download Installers
Release Preview Guide
|
ID |
Type |
Title |
Description |
|---|---|---|---|
|
48252 |
Deprecation |
Deprecation of using the SharePoint registry to configure OAuth |
Microsoft has deprecated the use of SharePoint for registering OAuth configuration. Instead, the registrations are done in Microsoft Entra.
Now, when the user is creating a SharePoint connector, Smart Flows supports app registrations in Microsoft Entra (Azure). This change is implemented to align with Microsoft’s direction. |
| 48330 | Feature | Experlogix Documents Locked during the Flow Execution |
When editing a Microsoft Word, Excel, or PowerPoint document in the browser during the execution of a Review and Approve Document flow block, the flow execution will now wait to resume until the edited document's state is unlocked. This in-built mechanism provides more certainty that the flow execution will pick up the latest version of the edited document. |
| 48278 | Feature | Introducing three new Docusign Flow Blocks |
Smart Flows is updated with three new flow blocks for Docusign connectors: Create, Update, and Send Docusign Envelopes. These flow blocks are available only for advanced flows. Each block performs the following function:
|
| 46974 | Feature | Support Document Conversion to PowerPoint and Excel File Types | Smart Flows Designers can now generate or convert source documents into Excel spreadsheets and PowerPoint presentations. This eliminates the need for additional plugins. |
| 45089 | Feature | Nested Form Recognized as a Dependency | Now, the system recognizes the nested form as a dependency of a form data set (Experlogix Documents). The user can view the associated nested form in the Dependencies section. |
| 47067 | Feature | Store Documents and Send Emails during Flow Execution (Microsoft Dynamics 365 Business Central) |
The Microsoft Dynamics 365 Business Central Connector for Smart Flows has been enhanced with additional functionality to support production use. These enhancements include:
|
| 47142 | Feature | Document link received via SMS |
In the 'Send to Docusign' flow block, a new feature allows users to share envelopes via SMS. This streamlines the process, saving time and effort in signing documents. Smart Flows leverages Docusign’s SMS feature to provide this functionality. Please be advised that this feature is not included in all Docusign subscription plans. |
| 47962 | Feature | eInvoicing - Data to File and Convert to ZUGFeRD Flow Blocks |
With regards to eInvoicing, Smart Flows now supports the following blocks in Flow Builder:
|
| 47617 | Feature | Persist Flow Definition Throughout Execution |
Smart Flows now captures and persists the flow definition at the start of each flow execution. This ensures that the entire execution runs against a consistent version of the flow, even if the flow design is changed or removed during the process. This catches unexpected errors or behaviors when resuming a long-running flow after a waiting state. |
|
48431 |
Feature |
Add Docusign Fields in Header & Footer |
Templates have been updated with new functionality where end users can add Docusign fields in the header and footer sections. This allows designers to position placeholders for Docusign signatures and initials in repeating sections of a template, improving visibility and consistency across the Template. This feature is available for both standard and composition templates. |
| 48400 | Fix | False positive success message when registering for an Experlogix Documents account |
When an administrator registered for a new Experlogix Documents account and the registration process failed, the administrator viewed a success message nonetheless. Now issues of the registration process have improved error handling. |
|
48816 |
Fix |
Optimized data retrieval time for Microsoft Dynamics 365 CE Connectors |
In some cases, connectors of Microsoft Dynamics 365 CE which were configured to not use the newly implemented individual user authentications, would not take full advantage of all previously implemented optimizations for data retrieval time reduction. We have deployed a fix so that, regardless of connector configuration, data retrieval from Microsoft Dynamics 365 CE is optimized for retrieval time reduction in scenarios that require a high number of data queries. |
| 48182 | Fix | Optimized handling of waiting state when anonymous form is saved as draft multiple times |
When an anonymous form was saved multiple times during flow execution, each draft evoked a new waiting state, causing unnecessary use of resources. Now the waiting state is evoked only once, regardless of multiple saved drafts. |
| 48199 | Fix | No cascading of security roles for Microsoft Dynamics 365 CE users |
When Microsoft Dynamics 365 CE users were given more than one Experlogix Smart Flows security role, they did not automatically get the highest role that was associated. We have fixed the issue and users with multiple roles now get the highest role attributed in the Smart Flows project. |
| 48293 | Fix | Resolved Flow Execution with Large Records |
Previously, when flows were executed in bulk for a large number of CRM or ERP records, occasionally an error message "Error, could not execute statement [Arithmetic overflow error for data type tinyint, value = 400.]" was displayed. Now, we have fixed the issue. Users can run a flow in bulk for up to 256 records, and the flow executes successfully. |
| 48056 | Fix | Resolved issue with sending email via SugarCRM with attachments based on an asset with special characters in its name |
When a user executed a flow with an Email (SugarCRM) block and the generated email contained an attachment based on an asset with special characters in the name, the flow failed, and an error message "Cannot invoke "com.XperiDo.Plugins.sugar.model.response.SugarUpdateResponse.getSugarRecord()" because "createdSugarDoc" is null" was displayed. We've fixed this issue, and the flow runs successfully irrespective of special characters in the asset name. |
| 48031 | Fix | Issue in Sample Loading |
When creating a sample for a Salesforce dataset with unsupported root objects, the UI continued to load, showing an endless spinner to the user. We have fixed this issue; the UI stops loading and displays an empty dropdown. |
| 47649 | Fix | Fixed Mapped Field Issue in Sugar |
While creating a flow in SugarCRM, the user can map email fields like To, CC, and BCC. Upon running the flow, occasionally the field mappings were not resolved. Now, the mapped fields are resolved in the email as expected. |
| 47895 | Fix | Unexpected error messages displayed during Salesforce connector creation | When the end users created a Salesforce connector, occasionally an error message "PromptFlowNot a valid enumeration for type: class com.sforce.soap.metadata.FlowProcessType" was displayed. We have fixed the code and no errors pop-up now during the Salesforce connector creation. |
| 47695 | Fix | Resolved the Display of SSO Users' Nickname to First Name | Previously, when a user logged into the Flow execution panel with an SSO connector, the application displayed the SSO user's nickname in the user table. We have now updated the application to display the SSO user's first name. The application will display the nickname if the SSO user's first name is unavailable. |
| 47786 | Fix | Login-in issue resolved in Sugar tenants | In rare cases when a user logs into two different tenants (SugarCRM) with the same ID, the SugarCRM system throws an Internal server error during the second login. We have fixed the issue and now when the user logs in the second time, the application works without any errors. |
| 46805 | Fix | Unable to Remove Users in Project Console | Previously, removing a user who had updated the Project Settings resulted in an error message, preventing their removal. This issue has now been resolved, and users can be removed smoothly without any interruptions. |
| 46818 | Fix | Fixed Flow Execution in Dynamic 356 CE | When a user initiates a Flyout (Run in the back)-tagged flow, in some cases the browser opened the Flow Execution Panel. We have now updated the code to display a message in Dynamics 365 CE, indicating that the flow is being executed in the back as expected. |
| 47560 | Fix | Flows in drop down button are not visible to Microsoft Dynamics 365 CE users with a Smart Flows role inherited from a team | If a Microsoft Dynamics 365 CE connector was configured with a hidden API key, and users would inherit their Smart Flows security roles from a team, they would in some cases not be able to see the flows associated with that security role be listed in the Experlogix Documents dropdown button in the command bar. We have fixed the issue and now Microsoft Dynamics 365 users can see the flows associated with their roles, regardless of whether the role has been assigned directly or via team membership. |
| 47521 | Fix | Flow execution fails when creating a datetime value in a create data flow block, based on a timestamp from a Read Document properties step | When a flow would contain a step to create data or update a record that contains a datetime mapping which is linked to a previous Read Document Properties flow block, executions of that flow would fail. The issue has been fixed and now the datetime mappings are processed correctly and the flow executes without errors. |
| 47522 | Fix | Fixed Sorting Issue | When the user performs a sort by Modified by in the Templates or Flows ,table of the Project Console the application sorts the items in the table based on the Modified by user's Last name. Now, the application sorts based on the first name and then on the last name. |
| 47129 | Fix | Issue with multiple Review and Approve flow blocks in a single flow | When a flow would contain multiple Review and Approve flow blocks, where the first one would use the "Map a document" method of retrieving the document to be reviewed and the second one would use the "Map a document" mechanism, flow executions would end in error, stating that the document for review could not be retrieved. We have fixed the issue and now executions of flows with multiple review and approve block succeed. |
| 48139 | Improvement | Error while creating connector via Active Directory for Dynamic CE 9.1 Windows Server 2016 | In the Edit connector dialog box, when an administrator created a Microsoft Dynamics 365 CE connector authorizing via 'Active Directory' to a Microsoft Dynamics 365 CE version 9.1 instance hosted on Windows Server 2016, an authentication error message was displayed. We have reworked the installation code and fixed the issue. No such error messages are displayed when a connector is created in this combination. |
| 46696 | Improvement | Validation of To and From fields before Saving a Flow | In Flow Builder designers would be able to save a flow definition that contained an Email (Microsoft Dynamics 365 CE) flow block without providing a value for the required "To" and "From" fields in the configuration of the Email block. This caused issues when executing the flow. We have fixed this issue by not allowing users to save the flow when the To and From fields are empty. |
| 47639 | Improvement | Warning Message displayed for Failed Document Deletion | Previously, in Flow Execution Panel, when a flow that was set to delete generated documents immediately after successful execution, would fail to delete intermediary documents generated in a Translate document or Edit document flow block, the system did not notify the user. The failure was only viewable via the log of the run. Now, when a document fails to be deleted, the system displays an error message in the flow execution, so users can manually delete the document as needed to ensure clean-up policy compliance. |
| 48103 | Improvement | Bulk execution timeout issue |
Previously, bulk flow executions run for any number of CRM or ERP records were allotted the same execution time as flows executed for a single record, which occasionally led to premature termination (time-out) of flow executions for a large number of records. Now, we have allotted different time-outs to different flow configurations based on the number of records for smoother flow execution. |