Experlogix Smart Flows 4.24 Release Notes

47994

Deprecated

Unable to Test Connectors

Some users experienced an "unsupported exception" message when attempting to refresh tokens when testing connectors in Project Console. AD FS 3.0, bundled with Windows Server 2012, was the root cause. Microsoft officially ended support for Windows Server 2012 on October 10, 2023. To ensure continued compatibility, users must upygrade to Windows Server 2016 or later, which includes AD FS 4.0. Released in 4.24.1

45667

Feature

Review and Approve Document Flow Block in Flow Builder

Flow Builder now includes a Review and approve document flow block, allowing other users than the active user to review, edit and approve a generated document Users can approve or decline the document, with options to provide reasons for declining. See Review and approve document.

46103

Feature

Enhanced Recipient Configuration in Flow Builder

The Send to Docusign flow block now includes a Configure recipients button, allowing users to map and overwrite recipient details like email, signing options, and authentication methods. For additional details, please refer to the Send to Docusign flow block.

46112

Feature

Add Multiple Templates to One Docusign Envelope

Designers can now add multiple documents to a single Docusign envelope, enhancing flexibility and efficiency. See the Send to Docusign flow block for more information.

46118

Feature

ID Verification in Smart Flows Template Builder

Smart Flows Template Builder now supports choosing if ID verification is needed and selecting the method (for example, IDnow, Electronic (eID), or Bank ID). Docusign handles the verification. See the Send to Docusign flow block for more information.

46124

Feature

Branding in Flow Execution Panel

Admins can now personalize Flow Execution Panel (FEP) to align with their organization's branding. This update introduces a dedicated Theming tab within FEP settings, allowing customization of the navigation bar color, logos for desktop and mobile views, Admins can upload logos with size validation, Theming settings apply universally across all users and include backend validation to ensure compliance with corporate guidelines. See Flow Execution Panel Overview for more details.

46331

Feature

Support for Individual User Authentication for Experlogix Documents Connector

The Experlogix Documents connector now supports individual user authentication for document storage. Documents are assigned to the user who initiates the flow, ensuring accurate monitoring. See the Individual User Authentication and User Authentications Tab for more information.

46800

Feature

Preview Release CPQ Connector Integration with Cloud Connect

Clients can now create Experlogix CPQ connectors by selecting a connection from a linked Cloud Connect instance. The new integration with Experlogix CPQ leverages a metadata model for more flexible data collection from CPQ and offers the capability open a Flow Execution Panel from within the web configurator, unlocking the full capabilities of Experlogix Document Automation. See Experlogix CPQ (Preview) Connector for more information.

46804

Feature

Improved Licensing Based on User Identities

We've updated our licensing model to better reflect how users interact with Smart Flows. Instead of counting users based on log ins, licensing now tracks user identities—meaning a single user accessing multiple connectors will be recognized as having separate identities. Syncing is now based on email addresses, ensuring consistency across systems.

47063

Feature

Authentication Method Toggle for Dynamics CE Connector

Administrators can now toggle between impersonation and individual user authentication for the Microsoft Dynamics 365 CE connector. This update enhances flexibility by allowing organizations to align authentication methods with internal security policies while maintaining full functionality. By default, new connectors use individual authentication, while existing connectors retain impersonation unless updated by an admin in the connector settings in Project Console. The selected authentication method is consistently enforced during data flow execution, ensuring seamless integration with Microsoft Dynamics 365 CE's role-based security. See Individual User Authentication and User Authentications Tab for more information.

46337

Fix

Custom Dataset Error in Microsoft Dynamics E-mail Flow Flow Block

In the Microsoft Dynamics Email flow block, the flow failed and the error message 'datasource entity with display name {1} not found' displayed when the To/CC/BCC email fields were populated using a custom data set. Now, the email is successfully populated.

46338

Fix

Internal Server Error when Viewing Template History

In Smart Flows, users faced an internal server error when viewing the version history of large templates published more than 50 times. Now, the version history displays correctly without errors.

46348

Fix

Items Needing Analysis Not Viewable in Data Set Optimizer

In Smart Flows, users couldn't view items needing analysis in the Data Set Optimizer. Now, a scroll bar enables users to read and navigate the list of items.

46380

Fix

Error Message Not Displaying in Flow Execution Panel

In Flow Execution Panel, generated documents without data previously did not display an error message. The issue is now resolved. If the flow execution fails, the system displays an error message indicating that the template contains fields that don't exist.

46612

Fix

Missing Document Download Link in Flow Execution Report

When running a flow in Flow Builder, the progress object in the flow execution report did not contain a link to download the document. Now, when users view the progress object, the system provides a link that allows them to download the document.

46738

Fix

Input Data Missing When a Flow Report is Exported and Imported into Another Project

When creating and running a flow from Microsoft Dynamics 365 CE or an XML/schema data set, input data is missing when exporting and importing the flow report into another project. Now, when users export and import flows, the input data is included.

46764

Fix

Incorrect role assignments in Microsoft Dynamics 365 CE/SSO integration after user sync

In the Microsoft Dynamics 365 CE/SSO integration, some users experienced incorrect role assignments after syncing users. Now, when users sync, they will have the correct roles assigned to them as configured in the Microsoft Dynamics 365 CE/SSO.

47526

Fix

Sugar Mapped Field to and CC Issue

We fixed an issue in the Email (Sugar) flow block. The email fields mapped to the To, CC, and BCC fields were not populating correctly. Now, these fields retain their mapped email values as expected.

47602

Fix

IllegalStateException: Flow Execution Failed

We fixed an issue where resuming a flow execution failed with an IllegalStateException if a user moved a flow block from one zone to another while the flow was paused at a user input step. The flow now resumes as expected, preventing execution errors caused by incomplete zone transitions.

47996

Fix

Flow Fails With "Could Not Initialize Proxy – No Session" Error

Resolved an issue where Smart Flows failed at the Docusign step with a "could not initialize proxy – no Session" error. This occurred when pausing the flow after document generation. We've addressed the issue permanently by modifying the load behavior. As a workaround before the fix, specifying a Docusign data set in the step allowed flows to execute successfully. Released in 4.24.1

48002

Fix

Unable to Install Sugar Module Loader Packs

Fixed an issue where users on SugarCRM versions beyond 14.2 could not install module loader packs (MLPs) due to pre-execution role scripts in the manifest. The team resolved this issue starting with the 4.24.1 release. Clients on older versions of SugarCRM can use the following workarounds to install MLPs successfully. This fix self-resolves for clients on currently supported SugarCRM versions; see the Version Compatibility Matrix for version support details. Released in 4.24.1.

Workaround 1

1. Modify the manifest.php.

2. Extract the MLP zip, open manifest.php, and remove the following script at line 382:

pre_execute' => array('<basepath>/scripts/add_smart_flows_roles.php

3. Re-zip the files and upload them again.

4. After installation, manually add the following roles to the project:

   1. Experlogix Smart Flows Administrator

   2. Experlogix Smart Flows Designer

   3. Experlogix Smart Flows User

Workaround 2

1. Remove existing roles before installation.

2. Remove the Smart Flows roles before installation.

3. After successful installation, reassign the roles manually.

46391

Improvement

SQL Error on Document Names Over 255 Characters

Some users experienced an SQL exception error where entering a document name longer than 255 characters resulted in a error org.hibernate.exception.SQLGrammarException: could not execute statement. The system now displays an Error - Generate Document message with a clear explanation when the character limit is exceeded.

46639

Improvement

Improved Error Messaging for SharePoint Folder Path Issues

Users encountered confusing error messages when fetching documents from SharePoint if the path did not include /Shared Documents/ or the user removed the /. Error messages now clearly indicate that the root cause is issues with the file path.

46658

Improvement

Message not displayed in Connect blocks form when there are no blocks with which to create links

In Flow Builder, the Connect Blocks dialog previously appeared empty when no blocks were available to link, causing users to assume there was an error. To improve clarity, the dialog now explicitly states: "There are no blocks available to create links with." This ensures users understand why no connections can be made.

46809

Known Issue

Pseudo Relation and Result Set Mapping Issue

Some users experience incorrect product ID mapping in templates when using result sets and pseudo-relations. Specifically, values do not return correctly from Microsoft Dynamics 365 CE due to namespace resolution issues.
Workarounds:
1) Modify the input XML: If you have control over the input XML, add a targetNamespace to the Schema and set it in the input XML. This ensures that the application properly resolves namespaces, allowing the template to function correctly.

2) Adjust template mappings: Instead of mapping sub-elements of the pseudo relation through the result set, structure the template to loop over the top element of the pseudo relation within the result set (/Generic_-_OFP-MAN/Vendor_-_PR). Within each iteration, map sub-elements directly via the pseudo relation (/Quote/quote_details/QuoteDetail/Vendor_-PR/no). This ensures that the mappings resolve correctly.