Experlogix Smart Flows 4.23.0

In Project Console, users encountered an issue when downloading flow execution testing data using the "Download All" option. After selecting a test execution in Flow Executions (Reporting), the download action failed, resulting in an error. This issue has been resolved, and users can now successfully download all flow execution testing data.

This update introduces automatic user creation in Smart Flows upon the first login. When a user logs in with a connector (e.g., Microsoft Dynamics 365 CE, Microsoft Dynamics 365 F&O, Salesforce.com, Sugar) with a valid Smart Flows role, they are automatically created in the system. If your connector Smart Flows security role does not match Smart Flows, Smart Flows will update to match your connector security role and overwrite the Smart Flows role. This behavior is the default for projects created after Experlogix Smart Flows 4.23.0 and can be managed via User Management in Settings. In existing projects, admins must manually enable it to adopt the new behavior. See Settings for more details. This behavior will replace the automated user synchronization, which is deprecated.

The name, description and record reference of a sample can now be updated at all times, even when the referred record has been removed from the connected application.

This fix resolves an issue in the Microsoft Dynamics 365 CE connector’s Data Set Builder where selected columns were not retained when switching between views (fields, lookups, and relations). Previously, only the "Name" and "System Name" columns displayed after changing views. Now, the system preserves the selected columns across all views until the user manually changes them, ensuring consistent and expected behavior during data set management.

In Flow Builder, for flow blocks containing a relative date selection input field two issues were identified. First, when selecting an absolute date, the system incorrectly displayed a date one day before the selected value in the input field. Second, when switching to relative dates, selecting a value other than "Days" in the unit dropdown was not applied correctly. These issues have been resolved. The absolute date selected now correctly reflects the input field value, and the selected unit in the dropdown is correctly applied to relative date selections.

The Experlogix Documents buttons have been deprecated for the Legacy Dynamics 365 Web Client, which Microsoft officially deprecated in 2020. Due to recent updates and bug fixes for version Experlogix Experlogix Documents 4.23.0, Smart Flows buttons will no longer appear in this legacy client. The functionality remains fully supported in the Dynamics 365 Unified Interface.

In Microsoft Dynamics 365 CE, some users experienced an issue where two Smart Flows buttons appeared instead of a single button with a dropdown. This error occurred while using Google Chrome version 128.0.6613.113. Now, only one Smart Flows button displays in the Microsoft Dynamics 365 CE ribbon when accessing the app using Chrome.

Experlogix Smart Flowsnow includes an Edit Document flow block. This new flow block enables users to pause, edit a generated document, and resume the flow. It also introduces flexibility by allowing mid-flow document modifications, making it ideal for scenarios where document input or revisions are necessary before continuing the flow.

The Edit Document flow block includes a rich text editor for descriptions and an option to retain the document in Content Manager from Experlogix Documents by selecting Keep the document in Content Manager. By default, the document is removed upon flow completion unless this option is selected. Users can access the document through a button in Flow Execution Panel to make edits and resume the flow. For more information, see Edit Document flow block.

This improvement allows users in Microsoft Dynamics 365 F&O projects to update existing custom relationships in the Relationship Manager without needing to recreate them. Previously, you could only view existing relationships and had to create a new one if changes were required, leading to additional steps and potential template reconfiguration. Users can update relationships directly, streamlining the design process and reducing redundancy, see Relationship Manager.

This functionality will benefit teams who frequently update templates and relationships. The system will display a warning if relationship edits could impact existing templates.

Previously, an error occurred when attempting to update a Microsoft Dynamics 365 CE date field with the Date Only format using an Experlogix Documents Form data set. The issue arose when mapping Experlogix Documents fields of type Day or Date/Time (with the time input disabled) to a CRM date field with 'Date Only' behavior. Despite selecting and inputting the correct date in the Experlogix Documents Form, the flow would fail during the Update Record flow block. The issue was limited to fields with the 'Date Only' behavior, while the 'Date and Time' fields with the 'User Local' behavior worked as expected. This has now been resolved, and the flow successfully updates the 'Date Only' fields from Experlogix Documents Form data sets without errors.

Previously, when importing a data set with the Fetch pattern set to OData, the system switched it to FetchXML upon import. This issue has been resolved, and the Fetch setting remains OData after import, whether in the same or a different environment.

In Flow Builder, pressing the Enter key caused an unintended Condition flow block to be added with each key press, regardless of the selected element. This update resolves the issue by ensuring the Enter key selects the Link button without creating additional, unwanted flow blocks.

We've added licensing to Experlogix Documents to provide scalable functionality to users.

Previously in Project Console, when users filtered by a specific tag and set the items per page to 10 in the Templates List view, the total number of applicable items did not match the displayed list. Users could only view the first ten items, even if more templates were tagged. The pagination malfunctioned, showing “10/10” items instead of the correct total (e.g., “10/25”). This issue has now been resolved. Pagination works correctly, allowing users to see all tagged templates across multiple pages.

When a user logs in to Smart Flows using OAuth, their login session is maintained for more efficient re-authentication. This enhances the user experience by securely storing session data, allowing seamless re-authentication.

Previously, when using an Option set (Choice) field in a Condition flow block within Flow Builder, the flow failed to execute correctly, even when the condition was true. This issue has been resolved, and conditions on Option Set fields are now validated as expected.

The new Pause Until flow block enables users to pause a flow until selected delayed output parameters from a preceding flow block are triggered. This block offers flexibility by allowing the flow to remain pending until one or more delayed parameters of preceding blocks are populated, making it ideal for scenarios that rely on external triggers or dependencies. The options are turned off if no delayed output parameters are available, ensuring the Designer can produce resilient flows.

Users can map the delayed output parameters for further use in subsequent blocks and steps, and the block tracks the total time duration until all triggers are completed for process Improvement. For more information, see Pause Until flow block.

Previously, selecting different revisions or language variants of a template always displayed the same version. This issue, caused by query parameters not passing correctly, has been resolved, and users can now preview the correct version and language of template revisions.

In Project Console, samples created through the API previously did not appear in dropdown menus, impacting data selection and retrieval. This issue affected Flow Builder Template Data Fields, where API-generated samples were inaccessible in dropdowns. This fix ensures that samples created via the API are now available in dropdown selections without requiring users to navigate to the data set's Samples List view.

We've implemented a breadth limit when using FetchXML for samples within Template Builder. This update sets a reasonable limit when previewing returns and optimizing performance when handling large data sets. Previously, previewing potential returns for samples led to fetching all data, potentially slowing down performance. Now, only a subset of the sample data is fetched by default.

Fetch methods have been standardized at the connector level to ensure consistency across data sets, allowing users to choose the method for retrieving data for their Microsoft Dynamics 365 CE. At the data set level, users can select from FetchXML, OData, or Use connector setting (which acts as a placeholder and can be cleared). Data sets imported into a new environment will inherit the environment's default fetch method, and reimported data sets will adopt any updated default settings from the connector. This update ensures a consistent and flexible data-fetching experience across environments. Fix Duplication in release note

We're proud to announce the release of the Share File flow block, which allows users to share documents stored in Experlogix Documents Content Manager through Smart Flows. This enhances document distribution for your organization by providing shareable links with customizable availability periods and interaction tracking on shared files. A license for Experlogix Documents is required, see Share File flow block. Flows can be paused and resumed upon interaction with a share link.

In Smart Flows, some users encountered an issue where the @id, @name, and @entity values were incorrectly populated switching from FetchXML to Odata in a Microsoft Dynamics 365 CE data set. After switching the fetch settings from FetchXML to OData, the XML for the same sample was inconsistent. This issue has been resolved, and now the XML output remains the same when toggling between FetchXML and OData fetch settings.

In Project Console, querying dependencies for Microsoft Dynamics 365 F&O connector as a system administrator previously returned both connector and system administrator dependencies. This fix refines the query response to display only the connector dependencies.

We are introducing the Translate document flow block in the Experlogix Documents connector for Smart Flows. This flow block enables users to translate documents generated within Smart Flows or stored in Experlogix Content Manager into multiple languages using AI-powered translation. The flow block supports implicit (Smart Flows output) and explicit (Content Manager paths) document sources, offering seamless translation integration. A license for Experlogix Documents is required, see Translate document flow block for more information.