Version updates 11.2.5

Released on 12/19/22

In this version

Release date:  May 10th, 2023

  • When creating a case from OData, an issue occurred when the creating user had multiple organizations assigned. The "Organization" attribute value was not sent, resulting in the case being created using the first organization assigned to the user. This caused display issues for the assigned user.
  • Correction of an issue with the integration between our system and SAP where the connection path was being sent incorrectly. The issue has been resolved, ensuring seamless communication between the two systems.
  • Adjustments made to prevent the BACACHESYNC table from growing too quickly and causing performance issues. These adjustments have been implemented to optimize system performance and ensure that the table remains at an appropriate size.
  • Adjustments made to the Scheduler configuration to improve performance aspects that slowed down its closing.
  • An adjustment was made to the behavior of the Case Creator Phase, allowing users to access the timeline without encountering errors. With this update, users can now easily access the timeline, except when the first task in the milestone is a sub-process.
  • An issue was identified where the system was removing all user roles when using Postman for user synchronization, despite successful authentication and update requests being sent. This issue has since been resolved, ensuring that user roles are properly retained during synchronization.
  • An adjustment was made to the FileUpload widget to show the thumbnails of the uploaded files.
  • An adjustment has been made to the Brazil time zone to remove Daylight Saving Time.
  • If a template contained a special character that was not supported by the automation engine, an error would occur during generation. However, this issue has been fixed, and templates can now be generated without error, regardless of the special characters they contain.
  • Deleting cases through the Management Console caused an error due to an attribute not being included in the deletion script. The issue has been resolved by adjusting the script.
  • A security measure has been implemented in the Bizagi Work Portal to prevent open redirect vulnerabilities.
  • A validation has been added for virtualized entities to ensure that queries are correctly mapped out and errors are avoided.
  • Adjustments have been made to the connection with Oracle databases to address issues with poorly generated queries to the database. 
  • An adjustment is made to the maintenance tasks to prevent the deletion of user access to processes until they are completely closed (sub-processes included).
  • The query list in Bizagi Studio is now alphabetized, making it easier to locate specific queries, even when dealing with a long list.
  • When working with virtualized combos in a form, an error occurred where non-editable combos would delete selected values when advancing to the next task. This issue has been resolved.
  • An adjustment has been made to the display of error messages, so that they now appear in the correct way when prompted, rather than using a different modal window.

Release date: 19 December 2022

  • For security reasons, Microsoft has stopped supporting Basic Authentication for both Exchange Online and Office 365 tenants.
    This has impacted Bizagi customers accessing Exchange Online external mailboxes via the Email Integration feature.
    Hence, this version includes changes to switch the protocol to use OAuth Client Credentials authentication.
    If you are impacted by Microsoft's change, you need to update your version, include four keys in the Bizagi scheduler and perform some changes to your Exchange configuration.
  • A new set of security features will help secure access to the Bizagi Dispatcher for SAP Cloud connector. Bizagi uses OAuth based authentication, aligning with the best practices published by SAP.
  • The Bizagi Dispatcher .zip file has been updated to allow users to connect in a secure way from SAP on-premises to Bizagi Studio.
  • The Visible, Editable and Required properties were not working appropriately when configuring forms in Bizagi Studio. This has been fixed.
  • Security updates on the endpoints used by REST methods to obtain user information.
  • In the Work Portal, there was a bug that prevented sorting search form results by a selected attribute. This has been fixed.
  • Bizagi Studio rules and expressions editor has been updated, adding missing function parameter descriptions and correcting misspellings found.
  • The definition of filters for Document Templates has been adjusted in order to avoid conflicts or incorrect behavior in execution.
  • In the mobile app, there was a bug in the Record View control that froze the app when trying to customize a form. This has been fixed.
  • An error in Query forms data tables prevented a query to be exported correctly to Excel. This has been fixed.
  • In Bizagi Studio, attributes associated with collections could be created pointing to the same entity. This caused an error when editing a Process Entity, preventing the creation of new attributes. Hence, a validation has been implemented to prevent the creation of attributes that point to the same entity.
  • Adjustments were made in SOAP web services data storage and retrieval to correctly handle escape characters contained in XML files.

Release date: 28 October 2022

  • When creating document templates after changing the name of an entity attribute, the reference in the template was not found in the system due to the name change. This was fixed.
  • Null validations were added to the creation of document templates to ensure correct responses and that the template can be generated as expected.
  • The configured transition to failure for a service activity didn´t behave as expected so an additional validation was implemented to fix this.
  • An inconsistency in the rules for global and summary forms was deleting some required values causing errors. Given that, an adjustment was implemented to prevent read-only forms from being changed.
  • An adjustment was made to the creation of document templates to fix an inconsistency that prevents templates to be created correctly.
  • A filter for a parametric table was adjusted since it was not working properly as it showed inconsistent and unexpected information.
  • An inconsistency was occurring when generating templates from the Web portal after applying changes to the templates. Validation was implemented to ensure the mapping of values remains consistent throughout changes.
  • An error occurred when trying to refresh forms more than once in the Work Portal. This has been fixed.
  • A previous implementation in the Work Portal was preventing the download of files generated during a case. This was fixed so that files from templates can be downloaded as expected.
  • Adjustments were made to the record traces method in the logs file to allow special characters to be part of the recorded information.
  • An error message will appear when a new parameter entity is created without an attribute, indicating that the name of the attribute is not complete.
  • An adjustment is made to the connection between Bizagi Automation and the Management Console Web to include encryption for the use of the Diligent Connector which was sending unencrypted data and receiving a USER_UNAUTHORIZED error.
  • Adjustments made to the replication feature available in Studio Collaboration Services: the possibility to manage replicated entities from the Web App, the option to add new records to replicated entities is deactivated, and replicated fields are not available for modification.
  • Fixed user interface in the Work Portal to include a horizontal scroll instead of fitting several columns of a parametric entity with a lot of attributes.
  • The document template has a feature that acknowledges and notifies the user when case-sensitive commands are not written correctly (instead of creating a document wrong, the process notifies the client of a spelling error within the document).

Release date: 09 September 2022

  • The Assignment logs were removed from the administration logs when cases were closed. This has been adjusted so that even if the maintenance task moves closed cases, the assignment logs remain in the same place.
  • Changes in the configuration for Odata SetEvent method were implemented to allow the search and editing of events when another option ("Show events and tasks in search results") was activated.
  • An error occurred in the generation of document templates when changing the names of entities. This has been fixed.
  • The configuration of a webservice has been fixed since it was not working correctly in Bizagi Studio because the usual files for the generation of the assembly did not work.
  • Adjusted the email rules configuration table to include the option to delete a rule or condition.
  • The section "My cases" was eliminated from the Webparts in the app since it is not functional anymore.
  • When trying to save changes an error was happening in the process model and the error message was too generic to find the cause and resolve it. Thus, the error message has been adjusted to show more information to the user.
  • When uploading images from the server into an object in the Work Portal app, the metadata was deleted. This has been solved by upgrading the camera plugin.
  • There was an issue when trying to add an attribute to a master entity. To solve this behavior, the SQL catalog has been adjusted to allow the changes.
  • An adjustment was made to improve the performance of the Work Portal since many processes were timing out.
  • To guarantee that all maintenance tasks and jobs are executed properly during set timeframes adjustments were made in the Scheduler. 
  • Libraries used in the automation components were updated to include security patches that fix vulnerabilities from their previous versions.
  • To make sure the styles defined in html are not omitted when rendering a notification email, adjustments were made in the email notifications template.
  • The Save button was hidden in live processes when the Pilot Mode is enabled as it is not a necessary action there.
  • In the SAP Cloud Connector, when there are incorrect mappings, Bizagi did not throw any error or warning messages to verify them. This has been included.

Release date: 08 July 2022

  • Unnecessary checks were prompted due to an issue with the impersonation token inside the Work Portal, but it has been adjusted now.
  • In order to guarantee the security of the information, HTML encoding is implemented in the message that a user can include when sending invitations to a subscription, model or project.
  • A file that used JQuery version 3.3.1 has been removed from the Customer Portal as it compromised the security of the system and performed an outdated function.
  • In the Forms Recognizer of the Bizagi Studio, the empty cells of database records were parsed as "__emptycell__" in the information sent, which was taken as the actual value. This behavior has been fixed to send space in the JSON representing the empty cells.
  • The feature of web parts in mobile devices was restricted to the scope initially set for projects when used for start forms that didn´t display the error message modal. The error modal is now included in the implementation to adjust this issue.
  • Time zone inconsistencies were occurring when creating cases through SOA layer on a Test cloud project. The times and dates entered by the system did not reflect the customized time zone. This has been fixed.
  • When assigning the value of a combo control in forms, an inconsistency was appearing due to its association with a format not contemplated in the system. This has been fixed to allow assigning values to the combo control.
  • An error was preventing timer jobs to execute properly in the Scheduler on the production environment. A fix was implemented to stabilize multi-thread scenarios that caused the error. 
  • A size adjustment was made to the properties window in Bizagi Studio so it will always be smaller than the computer screen size.
  • The assignation logs were deleted from the administration logs when cases were closed. This was adjusted so that even though the maintenance task moves closed cases, the assignation logs stay in the same place.
  • SAP cloud wasn´t able to recognize some attributes of its services so this connection was fixed.
  • There was an issue with the authorization to access specific reports in Bizagi Studio. It prevented users to see their accounts from the Work Portal. This has been fixed.
  • An unexpected behavior when executing and accessing BAM reports has been solved by adjusting the corresponding queries.
  • Adjustments were made to the colors of live filters in the Work Portal to show the text in the labels since the text used to take the same color of its background therefore it was not visible.
  • Adjustment of the error message when the Interface Wizard fails in Bizagi Studio, and adjustment in the connection configuration to allow interfaces with the special characters like: =!#&'()$+;@[]
  • An internal reading error occurred in the metadata of the templates due to a difference in data processing. To fix this behavior, adjustments were made to the data processing and filters in order to display them correctly in Bizagi Studio.
  • Fixed all the conversions of int 32 to int 64 when involved the field idworkitems.
  • An issue in the Scheduler was creating duplicate cases and queueing them up for execution after a conditional event. This error has been fixed.
  • Bizagi Sites' map controls are temporarily unavailable due to changes in Google’s API that have affected their operation. We are working on a solution.
  • Now you can deploy by command line for data export and import. This applies to Data Synchronization (.bdex files) and Process Templates (.btex files).

Release date: 13 May 2022

  • The Work Portal's user anonymization message has been improved, adjusting some grammatical errors and adding a clarifying note stating that customized user properties are not anonymized.
  • In the Work Portal, a component in the User configuration tab of the Users administration option was not loading properly, preventing the use of some features. This has been fixed.
  • There was a bug in the password recovery functionality when users belonged to a Windows domain, as Bizagi was trying to change the password directly in Windows. This has been fixed.
  • An error occurred when trying to access the Work Portal with a domain that exceeded the 25 characters limit (established for all database attributes). To fix the bug, the maximum size for the domain in the WFUSER table has been increased to 100 characters.
  • In the Work Portal, some inconsistencies in the History and Administration tabs for Entities and Activities caused the Timeline log records to be saved and displayed incorrectly. This has been fixed.
  • There were some performance issues in the Development and Test environments when using entity virtualization and failing to connect to the source database. This has been fixed and now the Work Portal displays an error message when the connection cannot be made, instead of retrying or virtualize wrong data.
  • When embedding Bizagi as a Webpart, the data required for authentication was not being communicated correctly to the other tool, causing an error. This has been fixed.
  • The LDAP import function was creating duplicate entries in the WFUSER table due to a misconfiguration in the Scheduler. This has been fixed.
  • The Mobile app has been adjusted to ensure proper validation of Image controls (regardless of the version they were configured in) and correct operation of the Inline edit and the Hand signature widget.
  • There was an error in the query that lists the records of actions made in activities, as the records were being duplicated. This has been fixed.
  • Fixed an error that prevented the one-click deployment to run more than once in Bizagi Studio.
  • Fixed an unexpected behavior in the OData layer that occurred due to a problem with filters applied to dates during integration with the database.
  • In Bizagi Studio, an inconsistency in the authentication object prevented it from being updated with the latest changes, causing problems during execution. This has been fixed.
  • An error was occurring in start forms created through the SOA layer, which erroneously indicated that a parameter entity was being modified in Test and Production environments. This has been fixed.
  • Eliminated a query launched by OData requests that consumed an excess of server execution memory and was not necessary.
  • The Work Portal’s Theme Builder has been adjusted to correctly display the icon colors in Inbox activities when the themes are different from Bizagi or Bizagi light.
  • An error occurred for some services when integrating Bizagi with the SAP Cloud Platform, as the SAP Cloud configuration wizard could not recognize these services’ attributes. This has been fixed.

Release date: 18 April 2022

  • An error when mapping character strings with escaped characters (\") caused integration problems with different connectors (SAP, REST, SOAP) in the Production environment. This error has been fixed and now the character strings received are correctly read and mapped.
  • An inconsistency in Bizagi Studio’s Analysis permissions generated an access error and prevented the viewing of reports from the Work Portal. This has been corrected to ensure the consistency of credentials and permissions, and now the BAM and Analytics reports display correctly.
  • When trying to download a report from Bizagi to Excel, an error occurred because one of the attributes needed was sometimes null and the process to get the reports was not handling that scenario correctly. This has been fixed and the reports feature has been adjusted to deal with null values.
  • In Test and Production environments, when the process entity was related to a parameter entity, an error occurred indicating that the parameter entity was being modified. This has been fixed.
  • The Scheduler has been adjusted so that scheduled jobs run at the time and time zone configured for the server in Studio.
  • A validation has been implemented to decide which SOAP port to use (1.1 or 1.2) when executing the interfaces of migrated projects.
  • In Bizagi Studio, there was an error in which nested containers were not restored to their previous state when restoring control states using the refresh action. This has been fixed.
  • When changing the language setting from English to Spanish in notification messages, line breaks were lost in the message body. This behavior has been fixed.
  • The New Case webpart is now supported in mobile devices.
  • An adjustment has been made in Bizagi Studio to allow the deletion of multiple email templates.
  • An adjustment has been made in Bizagi Studio to save the default value of boolean attributes when upgrading a project.
  • The Work Portal login page has been adjusted to keep the Remember me option checked if the user has checked it once.
  • Smart Inbox filters have been adjusted to consider the scenario where a project has only one application and filters involving list values work correctly.
  • When changing the language setting from English to Spanish in mobile devices, the texts of some webparts was shown only in English. An adjustment has been made to this setting for the texts to match the language configured in the user preferences.
  • In the Work Portal’s form combos, the default value was presented as [object Object] instead of the expected ----------. This behavior has been fixed.
  • Adjusted the Combo control to support up to 2000 records, so that they are displayed all at once and the list is not automatically filtered.
  • When uploading an Excel file with a % character in the filename, the upload progress bar ran  infinitely without a successful upload. This has been fixed.
  • The styles of the Theme Builder in Automation have been adjusted so that the background color of buttons allows the user to visualize the text.
  • An error occurred when trying to execute the Save Entity method from an external application because the XML request was not being read correctly. This has been fixed.

Release date: 10 March 2022

  • There was an error when deploying a project to Production, in which the system tried to convert null values of a closed workitem. This has been fixed and now null values are validated before closing a workitem.
  • The configuration of message events in the Collaboration section (Integrate step of the Process Wizard) was not working correctly. This has been fixed.
  • In Bizagi Studio Portable edition, the Environment options window was not loading correctly. This has been fixed.
  • An adjustment has been made in Bizagi Studio and the Management Console to update the content of a security property used in Windows authentication process.
  • Bizagi Studio expression validator has been updated to evaluate the System.String.Format and String.Format methods indistinctly.
  • The Library Rules editor has been adjusted to sort the rule family list alphabetically.
  • The option to view the password in plain text has been removed in Bizagi Studio.
  • Due to FedRAMP requirements for compliance, we applied a general security update in MyBizagi.

Release date: 10 February 2022

  • In the Work Portal, the Inbox was not considering all the columns when sorting cases. This has been corrected.
  • An error occurred when creating a new record in the Record View control, in which the record data was deleted when clicking the Save button. This has been fixed and data is now correctly persisted.
  • There was an error in NumberMoney and Column controls, in which values in scientific notation values were displayed incorrectly when assigned to type Currency attributes. This has been fixed.
  • When an attribute was selected from the Rules Editor Data Model tab, the XPath of that attribute was overwritten if the entity had too many attributes. This has been adjusted.
  • The configuration of the function to export table data is adjusted to contemplate the scenario where there are parametric tables without business keys.
  • An error that occurred when trying to delete an email template in an SCS project has been fixed.
  • There was an error when deploying to Production a process, which was generated by a duplication of primary keys in the temporary tables when the latter were created. This has been fixed.
  • An error that occurred when reviewing the Case Details of Process BAM reports has been fixed. Also, the alias used for SQL queries has been adjusted so that the final built-in reports display the correct information and the drill down option works as expected.
  • There was a compatibility issue between versions 11.2.4 and 11.2.5 when authenticating users through Azure AD. This has been corrected and now Bizagi validates (in both versions) users sent from the Identity Provider with the format domain\user@domain.
  • In Bizagi Studio Form Editor, it was not possible to collapse the Delete options section in the Advanced tab of the Table control properties. This has been fixed.
  • In the Forms Designer, the Table control’s Sort order property (Advanced tab) was not showing whether the sort order of the data was ascending or descending. This has been fixed and now a label is displayed (Asc/Desc) to indicate the type of ordering.
  • A translation adjustment has been made in the Expert view of Bizagi Studio. In the Spanish version, the texts of the MultilanguageProject NameOAuth Applications and Asynchronous Activity Console options found in the path Security > Authorization > Pages > Administration were adjusted. Additionally, the name of this last option is changed in the English version (Asynchronous work item retries is now called Asynchronous Activities Console).

Release date: 06 January 2022

  • In Bizagi Studio, from this version onwards, the security setting that enables the Work Portal’s Manage Process Time administrative option changes its name from Process to Manage Process Time. This setting is located in the Expert view, following the path Security > Authorization > Pages > Administration > Manage Process Time.
  • In Bizagi Sites, an error with the localization feature was preventing the correct loading of a page. This has been fixed.
  • There was an error in the CSS override feature that caused display issues in the backgrounds when migrating from version 11.2.4 to 11.2.5. The feature has been adjusted and now the backgrounds are displayed correctly.
  • In Bizagi Studio, adjustments were made to the construction of the entity name (from displayName to Name) in the Model Data step of the Wizard view. Likewise, inconsistencies in the Library Rules have been corrected.
  • When a user tried to Run On Cloud a project and login to the Dev environment’s Work Portal, the SSO authentication process behaved incorrectly. This has been corrected.
  • In the File upload control, the forms were not correctly showing the filenames that had special characters such as %. This behavior has been fixed.

Release date: 16 December 2021

  • Due to FedRAMP requirements for compliance, we applied a general security update for our mobile application.
    The change requires an update to all Bizagi Automation Servers, from version 11 and higher, regardless of the platform (on-premises and cloud).
  • A fix has been made to enable end users the possibility to assign cases and manage roles from the different locations of the Work Portal, without the need for enabling permissions to the User Administration page.
  • An error occurred sometimes when creating and updating Vocabularies, as Bizagi was including a hyphen (-) as part of the word. This behavior has been fixed.
  • An adjustment has been made on the Library Rules of Bizagi Studio to allow the visualization of the rule and its parameters, even if the rule is in use.
  • An adjustment has been made when duplicating a form, changing the name of the new form to include Copy of to be able to differentiate them.

Release date: 02 December 2021

  • Adjusted Bizagi Studio’s search feature, dependencies and rules editor to show the correct value of elements (displayName), and the version of rules and processes when editing.
  • In email templates, there was an error with the German localization settings for processes and tasks’ names (the information was always displayed in English). This has been fixed and the localization feature for email notifications has been adjusted.
  • Fixed an error that occurred in the WebApp when selecting several cases for cancellation.
  • Adjusted the form cache cleaning process to reduce cleanup time.
  • Fixed a bug that limited the authorization functions the Administrator user possess to manage users and roles in the Management Console.
  • In the WebApp, the information suggested to users was cut when long text was typed due to the suggest control fixed width. This width has been adjusted and long text is now displayed completely.

Release date: 12 November 2021

  • There was an error in the display methods of the Graphic Query’s Path functionality, which caused some elements to be shown incorrectly. This has been fixed.
  • Fixed a setting in Bizagi Studio’s dependencies window that prevented objects from loading with their complete information.
  • There was an error in the behavior of the status colors defined for the Risk signal. This has been corrected and now the colors match what is specified in the documentation. Similarly, when the signal is not configured, the default value is displayed.
  • An error that generated empty results when creating form queries in Bizagi Studio has been corrected.
  • Fixed the auto-fill behavior in the user creation/edition forms so that the fields are filled in correctly.
  • Fixed margin settings in css styles when attaching information in forms.
  • When using the File upload control, the system crashed if the file name contained special characters. This behavior has been fixed.

Release date: 02 November 2021

  • In the mobile app’s Smart Inbox, the sorting by field was not behaving as expected because when a column has the same name in different processes or a column is the result of merged columns, the system sorts attributes by value and by process. This implementation has been modified so that attributes are sorted by value regardless of their origin or the process.
  • Case sensitive attributes in the LDAP synchronization is now supported.
  • When trying to duplicate a search form, an unexpected error occurred because the duplication process was executing the update of validations and actions, even if they were not present. This has been fixed and the update is now skipped if there are no validations or actions configured on the form.
  • An additional validation was implemented in processes that require temporary files. Since these files are occasionally deleted, an error was thrown when they were not found. Now, the process validates the existence of these files and recreates them in case they have been deleted.
  • An error occurred in forms when advancing a case to a subprocess because the system was trying to execute a validation that is not possible to perform. This has been corrected.
  • Adjusted the translation of months and days of the week in Hebrew, and the configuration of the controls that inherits the reading orientation of the forms.
  • There was an error in the Entity Form document templates when registering the conditions to trigger templates. To fix this, a validation has been implemented so that a template cannot be saved without selecting the file.
  • In test and production environments, a configuration to save rules directly affected the performance of projects and environments’ migration to the newest version. This has been fixed to avoid unnecessary delays.
  • In the mobile app, the long-press feature to access copy/cut and paste options was not working correctly. This has been fixed.
  • An option was created to manage the schedule of custom jobs (occurrence, recurrence, and execution frequency) from Bizagi Studio Management Console.
  • Fixed a bug that included deleted tasks in the process of syncing offline forms.
  • A fix is ​​made to update the anonymous user token and open forms with generic users on public pages.
  • The database attribute decryption process is adjusted so that, when sending them to external integrations or consulting the data from the Work Portal, the data is displayed correctly.
  • When a rule belonging to a family was edited, the rules belonging to that family were left out of the cache and were not reloaded. An adjustment is made to re-query the deleted rules and ensure the expected behavior of scripts.
  • Keys and attributes are created in the database record synchronization configuration using LDAP to allow the definition of time-out limits. The previous settings were not adjustable and caused an error when the connection time timed out before the records were fully synchronized.
  • A new property is added in the Captcha widget to include an error message when the validation numbers are not in the correct order. This property is localizable so that the client can include the desired value and the error message is the following by default: The numbers are not in the correct order. Try again.
  • There was an inconsistency in the origin of the XPath context for document templates creation, due to the wrong property being used. This has been adjusted.
  • In the Work Portal of the mobile application, a new incoming case used to force the refreshing of all the information, regardless of the user’s active view at that moment. Since this behavior frequently caused loss of information, the application has been adjusted to prevent refreshing upon a new case arrival.
  • When performing a query over specific entity processes in which the entity had localization settings, some of the words in the query results were not translated. This has been corrected.
  • Fixed an error that prevented the correct display of tags and attributes in the Studio Collaboration Services catalog.
  • When generating a newer version of a process, there was error in which the Name of the process was shown instead of its displayName. The source for the display of a name has been changed and now the correct information is shown.
  • The lists of expressions and expression families are now arranged alphabetically when using the Copy from functionality of Bizagi Studio Expression editor.
  • When an authentication window was opened on a remote server, Bizagi Studio main window was adjusted so that it was always in the foreground. This effect is removed to prevent this window from staying fixed and obstructing other windows from viewing.

Release date: 26 August 2021

  • When enabling a Maintenance Window in the Management Console Web, the button Clean all and start maintenance was incorrectly shown in Spanish. This has been corrected.
  • There was a bug that did not allow the application attributes to be displayed in custom tables at the process level. This has been fixed.
  • When trying to create cases in the Work Portal, an error occurred due to an attribute conflict in the queries. This has been fixed and cases are now created correctly.
  • The queries configuration has been adjusted to deal thoroughly with empty cells in tables, since there is a difference in the way empty values are saved (null in database and empty in Studio rules).
  • An additional validation is included in the non-editable date control for the mobile app, as the clean data for action was not executing correctly.
  • The configuration of entity forms has been adjusted so that the context of the process is not searched (it does not exist in these forms).
  • The date format in UiPath has been reverted to the format used on previous versions.
  • Improved performance when saving forms in the Work Portal and Sites.
  • The InAppBrowser plugin has been removed from the mobile app because it is not required and presents vulnerability threats.
  • An unexpected behavior occurred when using the delegated users feature with deactivated users. This behavior was caused by a previous setting that prevented the sending of alerts to deactivate users. This has been adjusted.
  • In the WebApp and the Scheduler, BOT tasks were stuck in the asynchronous queue instead of executing, due to an error in the creation of the queue items when there was a high load on the Scheduler. This behavior has been fixed.

Release date: 02 August 2021

  • There was an error that generated data inconsistency when creating new rows inside a collection with the inline options activated. This has been corrected.
  • A style adjustment is included to correctly display labels and input elements when configuring vertical format in Bizagi Sites.
  • When an entity was modified, some values associated with it disappeared from the Work Portal (but not from the database). This has been corrected.
  • Long texts’ display is adjusted in elements that have enough space to be shown in multiline.
  • An erroneous behavior of the Scheduler that generated conflicts with the queue of tasks to be executed has been adjusted.
  • In the mobile application, the sending of required information between methods has been corrected to ensure that the forms are displayed correctly.
  • The time employed by the system to process changes in forms has been reduced with the dynamic cache cleaning disablement.
  • A check is included in filtered queries that contain a subquery, as this scenario was causing an error.
  • There was an error in the non-editable date controls of the offline forms, where changes made to values from other actions were not received or sent. This has been corrected.
  • A missing property is added in the Advanced tab of the Export option since it was not possible to uncheck certain components.
  • When performing a filter on combined controls with a related entity and selecting a key from this entity, an error was generated. This behavior has been fixed.
  • A validation is included in the containers that execute the actions associated with their elements when refreshed. The existence of the elements is verified before attempting to execute the actions.

Release date: 03 June 2021

  • Improvements in the new branding for all our products. A refreshed modernized look and feel has been introduced and we made sure every corner of our platform has been covered.