November 2023

30 November 2023

Migrating legacy apps

To support you in adopting VB expressions, we've added the migration capability for apps that were created using the legacy expression language.

The migration algorithm takes a legacy app as input and generates a new, equivalent app that uses VB expressions. This means you can smoothly adopt VB without starting from scratch.

It's essential to note that some complex expressions and specific controls may not be automatically migrated.

Complex expressions and several controls won't be migrated, but these cases will be highlighted as errors in the migrated app, so you can manually correct them.

Even in cases where automatic migration isn't possible, the algorithm preserves the logic of the legacy expression as a string, serving as a valuable reference to guide you in recreating it with VB.

Discover which legacy app elements are migrated and how to migrate a legacy app in our documentation.

Editing the details of a deployed app

Now you can easily update the details of a deployed app, including the app name, description, or version. Simply navigate to the Orchestrator folder where the app was deployed, open the Automations > Apps page, access the More actions menu for the desired app, click Edit app details, and make the necessary changes with ease.

Bug fixes

We’ve fixed the issue where an endless "Loading your app" state occurred when attempting to run non-public VB apps from UiPath^® Assistant.

16 November 2023

Dynamic validation mechanism

Our latest update introduces a significant improvement in the validation mechanism for runtime applications. When users provide values for the validation properties of a control during runtime, the enhanced validation not only verifies user input, but dynamically re-evaluates and adjusts error messages based on changes to these values. Here are the highlights:

Clearer and updated error messages: The mechanism updates the error when the validation properties change dynamically. Clearer messages guide users in correcting identified input issues.

Dynamic error adjustments and dismissal: For instance, if a string of five to ten characters is required, and you initially enter four characters, the error message highlights the minimum length. Once you adjust the minimum length to four characters, the error message is dismissed as the input becomes valid.

Automatic error re-evaluation: When you change a validation property and the provided value becomes non-compliant, the mechanism re-evaluates the value and an updated error message is automatically displayed.

This enhancement is applicable to controls with the IsValid property and whose minimum and maximum values can be changed during runtime, such as textbox controls, Date Picker, or Slider.

Bug fixes

Previewing an app with a complex control that referenced a Data Service entity failed when all the following conditions were met:

• entities variables were used to query the entity,

• the variables belonged to a different entity from the one the query was based on, and

• updating the queried entity assigned the wrong data type for the complex control.

This behavior has been fixed.