Review the updates in released versions of Interactive Forms package such as new and enhanced features as well as fixes and limitations. The page also lists the release dates of each version, and the compatible Control Room and Bot Agent versions.

Versions summary

Note:
  • To download an individual package (updated in an Automation 360 release where you want only the package), use this URL:

    https://aai-artifacts.my.automationanywhere.digital/packages/<package-file-name>-<version.number>.jar

  • For Interactive Forms package, the naming convention is: bot-command-uiforms-<version.number>.jar

    For example, bot-command-uiforms-3.1.2.jar

For detailed steps on downloading a package and manually adding it to the Control Room, see Add packages to the Control Room.

5.1.5

  • Compatible Bot Agent version: 21.88 or later
  • Compatible Control Room version: 10195 or later
Fix
When formatting a Number field on a form using the Use comma to separate thousands option, the number no longer only displays two digits on using Interactive Set action on number field. It now displays the correctly formatted number (for example, if you enter 12345, the number displays as 12,345).

5.1.4

  • Compatible Bot Agent version: 21.88 or later
  • Compatible Control Room version: 10195 or later

Fix

When a form contains a Number Field with the Use comma to separate thousands format type enabled, the correct value in interactive forms is successfully retrieved.
When creating a form with a Number element using an Interactive Forms package earlier than version 4.3.2, the number now displays correctly on the form instead of a blank page.

When using the Interactive forms:Set command to set the values in a table, if the table variable contains a Boolean value, the form no longer loads a blank form.

Service Cloud case ID: 02164573
The hyperlink now opens properly in the user's selected browser choice.

4.4.5

  • Compatible Bot Agent version: 21.88 or later
  • Compatible Control Room version: 10195 or later
Fix

The folder element in the Interactive Forms package no longer generates an error when any file is changed in a selected folder.

Service Cloud case ID: 02159921
After running the Change Form Title command in an interactive form, the correct new title now displays on the form. If Change Form Title is blank, then Automation Co-Pilot displays as the default value in the form title. Additionally, the Automation Anywhere logo icon has been updated in the header.

When you have two previous interactive forms which display within a trigger loop, if you add a third interactive form within that same trigger loop, it now displays properly.

Service Cloud case ID: 02168161

4.3.2

  • Compatible Bot Agent version: 21.88 or later
  • Compatible Control Room version: 10195 or later
Fix
When adding a title to a form, you now have the same editing experience when using the Rich Text Editor with Electron or with JavaFX.

Previously when using Electron with the Rich Text Editor, these text editing features were not available: Bullets, Numbers, Font color, and Highlight color.
When adding a label to a form in Process Composer, the label is now aligned properly based off of the alignment set for the label element.

4.1.10

  • Compatible Bot Agent version: 21.88 or later
  • Compatible Control Room version: 10195 or later
Fix
When entering data into a form, the selections made for radio buttons and numeric elements now persist when moving to a second form.

Previously, the selections did not carry over to the second form.

If multiple forms are used in a process, the second form now displays correctly when the automation is run.

Previously, the second form experienced flickering and did not display properly.
Limitation
Intermittently, Interactive forms has not been displaying when a user is on a shared screen. As part of this behavior, instead of the user seeing the form, a flashing Automation Anywhere icon displays in the toolbar. When this occurs, we recommend that the user click the icon to view the form on the shared screen.

4.1.5

  • Compatible Bot Agent version: 21.88 or later
  • Compatible Control Room version: 10195 or later
Fix
When the form window is displayed in the Interactive Forms package, the close button is now enabled if it is enabled in the form properties.

Previously, the close button was disabled.

4.1.0

  • Compatible Bot Agent version: 21.88 or later
  • Compatible Control Room version: 10195 or later
Fix
The user interface for interactive forms is enhanced to ensure the elements are centered and displayed correctly on the screen. Additionally, non-utilized image elements in interactive forms are now rendered as blank areas.

4.0.1

  • Compatible Bot Agent version: 21.88 or later
  • Compatible Control Room version: 10195 or later
Whats changed
Check Box works properly in interactive forms.

4.0.0

  • Compatible Bot Agent version: 21.88 or later
  • Compatible Control Room version: 10195 or later

Whats changed
After adding a new dynamic element to a form, the dynamic element now displays while rendered.
Snapshot and Checking the Check Box now work properly in interactive forms.
The padding on both sides of an interactive form has been centered.
The Powered by footer is now visible at the bottom of an interactive form.
Fix
Fixed security vulnerability issue. For more information, click the release download link and view the Security & Compliance reports at A-People Downloads page (Login required).

3.1.2

  • Compatible Bot Agent version: 21.88 or later
  • Compatible Control Room version: 10195 or later
Whats changed
Internal changes for improved security.
The user interface in forms has improved accent color and padding, for symmetry.

3.0.0

  • Compatible Bot Agent version: 21.88 or later
  • Compatible Control Room version: 10195 or later

Whats changed
Due to back-end updates, the package jar file size has increased which has resulted in the initial package download time to increase.
With this enhancement, in any automation a key-stroke or a mouse-click on a text-box, text-area, rich-text, number, date, or time element will trigger the associated rules. This is in addition to the focus-out cursor motion functionality that also triggers the associated rules.
Initially, the system displayed an error only if a form was called in an automation where the mandatory fields were not populated with data. Now, when creating or rendering a form from any automation, if the mandatory fields are missing value, the system displays an error.
In the Forms Composer, the rich-text element should be configured with 350 pixel width for a complete rendering of rich-text editor properties.
To troubleshoot issues for rendering an interactive form, refer to this new log-file location for more details: C:\ProgramData\AutomationAnywhere\BotRunner\Logs\uiForms-electron.log.
Limitation
The dynamic components for forms is not supported.

2.29.1-20230403-101855

  • Compatible Bot Agent version: 20.11 or later
  • Compatible Control Room version: 8750 or later
Fixes
Security updates to address vulnerabilities in Blackduck Apache PDFBox.