Experlogix Smart Flows 4.18.0
Previous Version: Experlogix Smart Flows 4.17.0
Release Date: 07/31/23
Download Installers
ID |
Type |
Title |
Description |
---|---|---|---|
42758 | Feature | Support Auth0 by Okta for SSO![]() |
We're supporting Auth0 by Okta as an identity provider for SSO![]() |
39937, 42815 | Feature | User authentication for Salesforce.com connectors |
Smart Flows now supports individual user authentication for Salesforce.com 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 that contains a step related to the Salesforce.com 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 the Flow Execution Panel or by an administrator in the 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 for more information.
|
42548, 42815 | Feature | Enable or disable connector for log-in | We've created a new feature allowing administrators to choose which connectors can be used to log in to Smart Flows. There is an additional filter column on the connector list view to display this setting, see Single Sign-On for more information. |
42422 | Feature | Flow run tab management settings | We've added a section in the user interface settings for the Flow Execution Panel so the user can define the format of the tab titles. |
42217 | Feature | Nested filters for filtered relations | Microsoft Dynamics 365 CE filtered relations now support using a field of a many-to-one related entity in the filter definition. Nesting goes one level of relationship deep. |
42287 | Feature | Possibility to show Smart Flows command bar buttons only on detail and list views of entities that have flows in Microsoft Dynamics 365 CE |
We've added a new feature that allows users to configure the visibility of the Smart Flows buttons in Microsoft Dynamics 365 CE. There are two options to choose from - show the button(s) on all entities or show them only on entities with flows. Button behavior can now also be managed from the Project Console during connector configuration.
|
37339 | Fix | Print job number instead of name | When running a flow with a Print flow block, the system uses the job number for the name. We've added a Print job name and configured the Job name field to show the value in the field. |
38745 | Fix | Occasional server error when uploading and XSD file to create a schema data set | We have fixed an issue with the sorting pattern for XML attributes and XML elements, that in rare cases would cause the creation of a schema data set from an uploaded XSD file to fail. |
42649, 42570 | Fix | Salesforce.com users whom are assigned an Experlogix Smart Flows permission, cannot see Smart Flows controls in the Salesforce UI if they lack the permission to read their own permission assignments | Users who don't have access to permissionSetAssignments, and have a Smart Flows permission, can now see the Smart Flows controls in the Salesforce.com UI. |
42931 | Fix | Unable to use ID field in entity reference mapping | We've fixed an issue in Flow Builder that prevented correct referencing of related entities in flow steps by mapping the actual entity reference instead of the id. |
43006, 42889 | Fix | Unable to import the Xpertdoc Smart Flows workflow assembly solution into Microsoft Dynamics 365 CE 9.0 and above | Users could not import the workflow solutions for the 4.16 and 4.17 releases. We've reconfigured the solutions connector and updated the links for core and workflow solutions for v9 and above. Please refer to Download Installers for more details. |
42196 | Fix | Occasionally an error occurs when configuring a site into a Microsoft SharePoint connector | When creating a Microsoft SharePoint connector, occasionally an error occurs when setting up the site URL. We've resolved the issue, allowing admins to create a connector with a specific site URL successfully. |
36286 | Fix | Unable to use the selected brand in the Docusign flow block | When running a flow with a Docusign step, the brand selection specified in the step configuration would be ignored. We've fixed the issue; the user can now use the selected brand in the Send to Docusign flow block. |
43004, 42656, 42658 | Fix | An error occurs when creating a sample with a maximum breadth for Microsoft Dynamics 365 F&O data sets | Occasionally samples limited in size through a maximum breadth setting, would fail to be created for Microsoft Dynamics 365 F&O data sets. We've fixed the issue. Users can now get records back for all samples, also those with a breadth limit. |
42679 | Fix | Filtering issue after closing the details of a flow execution in the Reporting section of the Control panel | When an admin applies a filter on the list of flow runs in the reporting section in the control panel, opens the detail view of the one of the flow runs and then closes that detail view, the filter would no be applied anymore on the list view of flow runs. We have fixed that now. |
42657 | Fix | Pending flows do not display in the Notification Panel | Previously, if two flows requiring user input were triggered, only the first flow triggered would display in the Notification Panel for some users. We've fixed the issue. Now, the system displays all pending flows in the Notification Panel. |
42721 | Fix | Issue related to mapping images in Microsoft Dynamics 365 CE notes after import | When users import a template into a project that has a different Microsoft Dynamics 365 CE connector than the source project, mappings containing notes with images would not be able to retrieve and render the images. We have updated the behavior to always reference a project's default Microsoft Dynamics 365 CE connector in mappings with formatting preservation that are configured for embedded image rendering. For more details, please refer to Why are my attached images missing from my Dynamic 365 CE Note? |
42902 | Fix | Updating the Microsoft SharePoint folder structure pattern settings for a Microsoft Dynamics 365 CE plugin causes Store in Microsoft SharePoint steps that are configured to use the SharePoint Document Location to fail | We have fixed an issue where updating the SharePoint document location path pattern on a Microsoft Dynamics 365 CE plugin would not propagate correctly to the corresponding application setting. This resulted in errors when executing flow steps to store a document in its SharePoint document location. |
38897 | Fix | Filtering error on data set table if sorted by Created by or Modified by | We fixed a filtering error that would return no results if you would apply a filter on the data sets table in the Project Console after you first sort the data set table by the Created by or Modified by column. |
42334 | Fix | Issue discovering flows and templates that have the same name when analyzing dependencies in Data Set Optimizer | We've fixed an issue with the analysis of dependencies in the Data Set Optimizer. When the analyzed data set would have a dependent flow and a dependent template with the same name, these items would not be discovered during analysis, causing the analysis results to be incorrect. We have changed the analysis mechanism to support this pattern. |
42852 | Fix | Microsoft Dynamics 365 CE datetime fields not always recognized as such in Flow Builder | When referencing fields from Retrieve data steps in Flow Builder, datetime fields are marked with a calendar icon and have a formatting pattern setting. Datetime fields in the primary entity of Microsoft Dynamics 365 CE data sets, however, were not categorized by Flow Builder as such, thus not offering the user building the flow to select a formatting pattern. We have fixed the issue so that all datetime fields in primary entities of Microsoft Dynamics 365 CE data sets are now recognized as datetime fields within Flow Builder. |
43036 | Fix | Complex schemas containing multiple XSD files are downloaded with the file extension .xsd instead of .zip | When downloading a complex schema data set, the extension of the downloaded file was.xsd, where it should have been .zip. We have rectified that. |
43033 | Fix | Content type header of response for template schema endpoint set to the wrong type | When using the API endpoint to retrieve the schema of a template via the templates/{templateId}/schema endpoint, the response was set to the wrong content type. It was set to application/json instead of application/octet-stream. We have changed the content type of the response. |
36074 | Improvement | Add loading spinner to Mapping window in the Create data step of Flow Builder | We've added a loading spinner animation to the Mapping window in the Create data step of Flow Builder to indicate that the system is still active when loading a data set. |
36185 | Improvement | Smart form submission confirmation | Previously, some users could reopen an already submitted Smart form. Users who open a completed Smart form link will receive a confirmation message indicating their submission has been received. |
42961 | Improvement | Replaced Xpertdoc logo with Smart Flows logo in Flow Builder | In Flow Builder we've replaced the 'Xpertdoc' icon for Start this flow from the Flow Execution Panel with the 'Smart Flows' icon. |
42697 | Improvement | Standardized spelling of Style label in Template Builder | Template Builder was inconsistent in naming the capability to save and reuse formatting configurations as a style. We now consistently refer to this capability as 'Template Builder Style(s)' to avoid confusion. |
42335 | Improvement | Updated default behavior for the Report task pane after previewing a template in Template Builder | We've changed the default value to enabled for the checkbox "Don't show the Report pane when there are only info message after preview" under Confirm certain actions in Option settings for Template Builder. The Report task pane now only displays if there are actual warnings. |
36288 | Improvement | Updated data label in Generate Document flow block | We've improved the linked data input field in the Generate Document flow block in Flow Builder. Now, it displays the name of the data set instead of the fixed value "Data." |
42498 | Improvement | Improved the Microsoft SharePoint Authorization type dropdown menu | For Microsoft SharePoint connectors, we've improved the Authorization type dropdown menu language to better indicate the authentication type associated with each option. For example, the "SharePoint server"option has been updated to "SharePoint Server (UserName/Password)". |
42821 | Improvement | Implemented drag and drop to order option set fields in custom data sets | We've implemented a drag-and-drop option to sort option set items in custom data sets. |
42564, 42565 | Improvement | Made non-sensitive application properties available via the API and in the Project Console | We've added an endpoint in the Smart Flows Smart Form to read non-sensitive application properties. In the UI these properties are displayed in the About section of the Admin console, see About for more information. |
42612 | Improvement | Improved Docusign envelope status handling when recipients interact with approve and decline fields | We've improved the envelope status processing for Docusign. When users approve/decline an enevelope |
42552 | Improvement | Automated Salesforce CORS allow list | When creating a Salesforce connector, the system automatically adds the CORS![]() |
42391 | Improvement | Improved expired token message | We've improved the error messaging for connectors to indicate when the cause of the error is an expired refresh token, such as "... PortalException: error.refreshtoken.invalid". |
42678 | Known Issue | Unable to support Ping Identity in Template Builder | Users can log in to Smart Flows Project Console using Ping Identity, but currently Ping Identity does not support authenticating Template Builder due to technical reasons. |
|
Deprecation |
Deprecation of Experlogix Smart Flows Workflow Assembly for Microsoft Dynamics 365 CE |
We are deprecating the ExperlogixSmart Flows Workflow Assembly for Microsoft Dynamics 365 for Customer Engagement. The 4.18 workflow solution will be the last one we ship. Although we will still support integrating Smart Flows steps in Microsoft Dynamics 365 CE workflows until the 4.19 release (slated for Fall 2023), we recommend transitioning from traditional workflows with Smart Flows steps to Microsoft Power Automate flows with Smart Flows actions. |
|
Deprecation |
Deprecation of Experlogix Smart Flows Core Solution for Microsoft Dynamics 365 CE v.9.0 |
Following our rule of thumb to support the latest two versions of all connected applications, we are deprecating the integration with Microsoft Dynamics 365 CE for Customer Engagement v.9.0. Version 9.1 and 9.2 of Microsoft Dynamics 365 CE remain fully supported. |