Experlogix Smart Flows 4.15.0

Previously when creating an Microsoft Dynamics 365 F&O connector, the system provided a generic error if you attempted to create the connector before installing the Microsoft Dynamics 365 F&O app. We've added a more specific warning to prompt users to install the app before finishing the Microsoft Dynamics 365 F&O connector setup.

We've added a new warning when deleting data sets. If the data set(s) are linked to a template, users receive a warning if that data set is mapped to a template in the project.

We've added the Disable field reducer setting to the Flow setting page in the Control Panel. When checked, the system retrieves the data without performing an analysis. Disabling the field reducer can save time for large, complex templates.

We have added the ability to see document compilation and generation time. This value displays whenever either value takes longer than 10 seconds. Admins and Designers can review these values in Template Builder, Project Console, and during Flow generation.

In Project Console, when selecting and deselecting a primary entity, all fields are selected instead of no fields. We've added a filter on the advanced fields to resolve the issue.

Users without the appropriate credentials to create an F&O connector have an additional option to use the Smart Flows Admin credentials. This additional checkbox displays during the create configuration record stage.

We've automated the Send to Docusign flow block to pull the Docusign data set even if a Designer forgets to select it manually.

When configuring a Sugar connector, the system does not verify that the presented options are valid after the connector completes the reset process. This results in an internal server error. We've implemented a fix to show only valid checkboxes after resetting.

After cloning a custom data set, some users received the error: Invalid combination of data sets. This error is due to the cloning process sharing an identical name. We've added a fix to use unique naming during the cloning process.

Microsoft Dynamics 365 CE users experienced a logic error where the Condition flow block would always display false when comparing the same "Field," and the "Value" condition is True." The same issue occurs when using the Operator "Does not Equal." The system experienced this bug due to the data not being retrieved earlier in the flow execution. We've implemented a permanent fix to resolve the issue.

Some users experienced an error where changing a condition in a composition template resulted in the condition reverting to the settings before the change. This error was due to the system logic iterating the node based on the user's changes. We've implemented several code changes to fix the issue permanently.

We've previously improved the project clean-up function in 36785 and 36931. We've now added a smaller batch and save action within transactions. This ensures that errors during transactions minimize the amount of rollback.

When creating a data set in the Project Console, an vague error displays when selecting a data set type for a connector that does not exist in the project. We've added validation tests to check the available connectors and only provide data set types for existing connectors.

When using custom or Docusign data set fields in the Project Console, the system allows users to use the name of an existing field without creating an error. We've added additional validation to notify the user and require a unique field name.

In the data set builder, when using a custom data set numerical field and using a either the arrow keys or arrow buttons, the system allows the value to go below the minimum value. This error was related to the JSON Schema and we’ve added a permanent fix to to specify the “type” the resolve the issue.

Due to failed validation, some users experienced an issue where the dates from custom fields could not be used for filtering. We've implemented a permanent fix for the issue.

When exporting multiple flows with included dependencies and samples, the Export button can still be clicked, resulting in an error. We've changed the Export button to be no longer interactive while the Export process is running.

When using a custom data set to display a message at the flow output, the year displayed differs from the formatted date. This output error is due to the subtle difference between the "yyyy" formatting for the calendar year and the "YYYY" for the year of the week. We've updated the dropdown in the Flow Builder to use a custom value to resolve the issue. At the same time, we’ve made changes to formatting throughout the Flow Builder to provide a permanent fix.

The system only sends one email using two Docusign fields with different routing orders but the same email address. The system produced this error due to a design oversight; we did not configure the system to allow identical emails with differing routing orders. We’ve added additional system logic to handle this and provide a permanent fix.

Some users experienced an issue after the signing ceremony where the signed fields did not display. This error was related to the group label not being checked. We've implemented a fix where the system automatically applies the correct group labels.

In Project Console, when opening the System language dropdown menu, there are no entries to select. This error was caused by the order of operations when calling for language selection; the "ngOnInit" command failed to retrieve the entries. We’ve made code fixes to resolve the issue permanently.

When creating Assets with an existing PDF, the user receives an error. The issue occurs on multiple PDF versions, not just the 1.20 version. We've implemented a fix for the issue and added support for PDF 2.0 and PDF/A-3. For more information on compatibility, refer to the Version Compatibility Matrix.

We've added additional stats to the Flow reporting Dashboard to provide additional oversight for administrators. The additions are related to compilation time and file sizes; refer to the Reporting page for more information.

Some users continue to receive a licensing warning on the Licensing tab in Project Console even after renewal. This issue was due to the MessageCategoryEnum.FULL_SCREEN line not clearing upon renewal. We've implemented a permanent fix for the issue.

The API Call flows/executions/Id began to fail inconsistently during automated testing. This failed test was due to the Cypress framework, and we've applied a code fix. After the fix, automated testing passed with no issues.

When producing the flow execution display message, the system added a space to the first line. The system error was due to the whitespace setting using "pre-wrap"; we've fixed the issue by switching to "pre-line."

We've added a new user interface to the Flows tab in Project Console allowing Admins and Designers to see more advanced data statistics for their projects. Analytics such as template compilation time and size of compiled templates are now readily available; refer to the Advanced tab for more info.

A small group of users experienced an issue where if a flow were to run, start, and then to wait in quick succession, there would be no way to cancel the waiting state. This error was due to a design oversight where it was unexpected that the user would put a flow into waiting mode immediately after running. We’ve changed the code to accommodate this use case and provide a permanent fix.

When checking the checkboxes for “flyout behavior” and “custom tags” and then unchecking them, the system rechecks the boxes for the user. This error was due to the system not checking the boxes for updates. We've added a fix so that the system checks for updates before refreshing the state of the checkboxes.

We’re proud to announce the availability of a French translation for the Template Builder user interface.

The Generate Document link contains an added space in front of the link address during flow output. The system error was due to the whitespace setting using "pre-wrap"; we've fixed it by switching to "pre-line."

Some users experienced a missing document link after executing a Send to Docusign flow block. This error was due to duplication in the iteration key. We've implemented a permanent fix.

When calling for roles on the "name" value, the system returns the Designer role instead of the Admin role. We've made changes to filtering, Id, UUID, and Displayname. We have also removed a deprecated Maven plugin to provide a permanent fix for the issue.

When using the PUT method with the HTTP request with HTTP connector flow block, some users experience missing body input. This system experienced this error due to several older schemas directing the process. We've made multiple changes throughout to provide a fix.

Some users with on-prem and private instances experienced IllegalAccessError. The error in image handling was inherent to Java 17, and updating to Java 17.0.4 resolves the error and associated issues.

When importing data sets with multiple samples, some users experienced an error where the data set would only contain one sample. This error was due to system not connecting the data set with all of it's sample during the import process.

When importing data sets with multiple samples, some users experienced an error where the data set would only contain one sample. This error was due to the system not connecting the data set with all of its samples during the import process. We’ve implemented a permanent fix for the issue.

When receiving an error related to a field, there are still errors that use placeholder variables. We've made multiple changes to increase the insertion rate for field names to make error messages more effective for troubleshooting.

When executing a post request /flows/executions/statistics?groupTimeBy=HourOfDay without a body, the request returns a null pointer exception. We've fixed the pointer in the code to provide a permanent fix.

Some users experienced an error when creating a new template. Suppose the name on the server version matches a template's name on the local hard drive. In that case, the server version cannot overwrite the local version. The process experienced this error due to using the wrong template label in response to the question to overwrite. To resolve the issue permanently, we've done the following

• Clarified the naming language to be more specific
• Updated the overwrite question to "Namevariable already exists on your local machine and is not created for the template you want to open. Do you want to start this template with that local copy?" to increase clarity on the action to be taken.

Some Microsoft Dynamics 365 CE users experienced an inability to make changes to their flows after deleting the Create Note flow block. This processing error occurred due to some legacy empty strings. We’ve removed the empty strings and added an automated test to fix the issue permanently.

Some users experienced an error where changing a condition in a composition template resulted in the condition reverting to the settings before the change. This error was due to the system logic iterating the node based on the user's changes. We've implemented a permanent fix for the issue by adding additional logic to the node to ensure it properly iterates based the user's actions.

When changing the user interface language to Dutch or French, instances of the word “of” remain untranslated. We've added the translation to our system for both Dutch and French.

Some users experienced an error when adding languages to Smart Flows. Languages added in Project Console weren't reflected in Template Builder. This system error was the result of the cache not updating with the new language and instead relying on persistent memory. We’ve implemented so that the system uses the cache for languages going forward.

When combining the user-editable alternatives setting with the ask questions first option, no user-editable alternatives display during the flow execution. This bug was due to the system not having the additional logic to consider all situations. We’ve added additional system logic to resolve the issue permanently.

Some users on private cloud servers experienced the NoClassDefFoundError. We suspect the root cause of this error is a concurrency issue Designers have a reduced number of Project Console abilities- they are unable to make major changes that could break the project. They can also access the Template Builder add-in for designing templates.. We have updated our version of pdfbox and applied a possible fix to make the PDDocument initialization static. We will continue to monitor the situation for additional issues and opportunities for improvement.

Admins and Designers can now optimize their data sets based on the fields used in their templates. The system automatically marks unused entities and fields in the data set. Then Admins can use the Optimizer tab to remove the unused entities. Optimized project Admins should expect improved template compilation time and other related build activities.

In the Project Console list views, the page number interface overlaps the dropdown menus for the top navigation. We've implemented a fix to give the dropdown menus precedence and always display on top of other items.

When resetting a user’s password, the system indicates whether the user exists within the system. To increase system security, the system no longer indicates whether the username is valid or exists in the project.

In the Project Console, when users selected the cogwheel icon on the composition template type, the cogwheel remained gray. We've updated the UI so that the cogwheel displays blue when the user selects it.

Deleting the non-default Portal connector displays a dependency error in projects with multiple Portal connectors. We've made an update, so the warning only displays on the default Portal connector.

We've removed the textcolor plugin because it is deprecated in TinyMCE 6.0. Removal of the textcolor plugin does not affect any existing or new projects.

In Project Console, on the Microsoft Dynamics 365 CE connector configuration page, clicking on the URL Microsoft Dynamics 365 CE instance does not open the instance. Additionally, Smart Flows no longer displays in the browser. The root cause of this error was the link configuration. We’ve updated the link configuration to open the Microsoft Dynamics 365 CE instance in a new tab and keep Smart Flows open in the existing tab.

Some Docusign users experienced an error where the Send to Docusign flow blow does not produce a .docx file as directed by the Generate document flow step. The bug resulted from a lack of validation between the Generate Document flow step and the Send to Docusign flow block. We've added validation logic between the two points, with the Generate Document flow step taking precedence.

When viewing the list of supported metadata types in the Send to Sharepoint flow block, the naming and order of options do not match the list in SharePoint. We've updated the dropdown naming and order to match the SharePoint types we support precisely.

Users can now select a specific language when running a flow. When a language is selected, the flow only compiles the selected language. This can save time due to the lengthy compilation time for large complex templates.

We've increased the number of entities displayed in the Relationship Manager tab for Microsoft Dynamics 365 F&O connectors and during data set creation. This improvement allows for faster selection, searching, and filtering of entities.

After configuring the Metadata>Value field, the field replaces the entered Value with [object Object] after making and saving changes. The error resulted from the type of object used for the Value field. We've switched the field to a string value to resolve the issue permanently.

When filtering on a Sugar data set, the content that should be filtered out displays in the List view. This error was caused by POST "filter" and Endpoint "Users." We have implemented a correction in the call and response to provide a permanent fix.

For flows with a template in multiple languages, when using the Switch flow block to allow the user to select a language, only the default language is shown during the flow run. The user cannot select a language if the template does not have a default language. This error was due to the logic for the list of values not allowing for an empty default cause. We've updated to code to allow for an empty default case so that language values display regardless of a default case.

In the Project Console, when working with tag items, users can now mouse over tags to display the full tag name.

Some users in Template Builder experienced a failure to trigger errors. Despite the configured settings in Template Builder, errors would not occur. The cause of these errors was due to a design oversight where the system does not produce an error if the process does not retrieve the required template resources. We’ve made code changes to allow for situations where the process does not return template resources as a permanent fix.

Template Builder only displays 20 language variants, even if more language variants are associated with the template. This error was due to the default page size. We've increased the default size to 50.

Some users experienced an error when sorting via the Created On date entity in the Template History table. When the filter is enabled, no changes occur in the table. We've made multiple code changes to provide a fix, add a descriptive error and automate testing for the solution.

In projects with multiple Portal connectors, some users experienced an issue where selecting the "Edit Smart Form" button resulted in the wrong Portal instance opening. This issue was due to the system using the first created Portal connector instead of the default Portal connector. We’ve added a code fix always to use the default Portal connector.

When creating a Docusign data set, the first field created only appears after pressing the Create button. We've implemented a fix so that the field displays immediately.

Some users experienced an error while filling in the fields for a User; the system would delete the characters. This error was due to the system attempting to save while typing. We've extended the period before auto-saving to resolve the issue.

When adding tool tips to a Docusign data set via group labels, if more than one tool tip is added the system throws an error. This error was due to a typo in the code. We've added additional code coverage and validation to provide both a fix and an automated test to allow for multiple tool tips.

Users can start Flows with an API key by using an X-User-Id header. Suppose the value for the header matches an existing user in the Smart Flows user list. In that case, a flow can be started via impersonation. The value must be the user Id, email, or username.

When attempting to delete multiple connectors simultaneously, the system only deletes one connector while the second connector selected remains. Additionally, the error: could not execute statement displays. Despite testing, we were unable to reproduce this error. We continue to monitor the situation for recurrence.

Some users experienced an issue with Email flow blocks for Microsoft Dynamics 365 CE and Sugar connectors that prevented them from editing the message body during the flow run. The issue was caused by duplication in the code, causing unexpected behavior. We plan to continue optimizing and creating separate classes in future versions.

Some users with a Microsoft Dynamics 365 F&O connector could not export multiple custom relations. We've made multiple code changes to fix the issue permanently.

Users who attempt to use Samples with French special characters receive an error(Internal error occurred: MalformedByteSequenceException: Invalid byte 2 of 2 byte UTF-8 sequence) when saving. This issue was caused by an error when encoding the characters. We've implemented a permanent fix for the issue.

In previous versions of on-prem deployments, we used an older algorithm to encrypt the application.properties file. However, that older standard resulted in a relatively easy-to-crack algorithm. We have updated an improved PBE algorithm for encryption.

When the option "users can ignore the presented options and create their own" is selected for the Document Name, the field does not appear during the flow run, and no value can be added. We've made several changes in the code to resolve this issue permanently.

Some users experienced an issue when using the Merge Document flow setting. When using the Merge Document setting, the user input is not mapped and does not display in the generated document. This bug was due to how the system determined which data to merge. We've implemented a fix and added automated testing to maintain it permanently.

When creating a custom data set and using a number field with a maximum value, when the value of the field exceeds the limit, the user receives the error “ERROR.GENERAL.MAX_VALUE.” We've updated the system to provide the error, "The value of this field is too high."

When adding a value to a single line type field with the linked field customization selected, the mapping is added before the text. This bug was caused by how the system handled complex variables during flows. We've optimized the implementation to improve complex variable handling.

In the Project Console, the system does not maintain the aspect ratio when scrolling on the Licensing page. This loss of aspect ratio results in the page elements running off the page. We've implemented a permanent fix to resolve the issue.

When creating a custom relationship with an F&O connector, the success message displays "Sample successfully created." We've updated the message to display "Custom relationship successfully created."