Version 11.3.3 Release Notes

• All Control Room users can log in and access the Bot Store from the Control Room. See Accessing Bot Store.
• New roles and permissions are available to allow users to access and download bots and Digital Workers from the Bot Store. See Enterprise 11: System created roles and Enterprise 11: Feature permissions for a role.
• View information about the bots downloaded from the Bot Store. See Downloaded bots from Bot Store.
• Download bots and Digital Workers from the Bot Store to the Control Room. See Downloading bots to Control Room repository.
• View in-progress activities and audit logs for the bots and Digital Workers downloaded from the Bot Store. See Monitor in progress activity and Audit logs for bots downloaded from the Bot Store.
• Run protected bots from the Control Room. See Running protected bots.

When scheduling a bot, you can set the Start and End time by selecting a time value from the drop-down list, which contains pre-defined time values in the 12-hour format at intervals of 15 minutes. This enables you to quickly select the time from the list, or manually set the time for the values that are not available. See Enterprise 11: Schedule a bot.

See Enterprise 11: Actions allowed on view queue page.

See List all work items in a queue.

Automatically reinstall Control Room during repair or reinstall process

When repairing or reinstalling the Control Room, after the uninstallation completes, you do not have to manually run the setup file to reinstall the Control Room. The reinstallation process starts automatically using the previous settings. See Uninstall or repair Control Room installation.

Introduced the option to Include Historical Activity when migrating bots using the Bots and Schedules option. This option enables you to retain the task run history of the bots that need to be migrated to version 11.x. See Select bots to migrate.

After the migration process completes, you can view the status of the historical activity migration (success or failure) in the History tab of the View Migration page. See Analyze migration status.

Distributed caching and messaging communication across nodes is now over TLS.

Maximum 200 Active Directory (AD) groups can be mapped to roles in the Control Room.

See Map Active Directory roles.

• Create and store Digital Workers or bot packages in the default Bot Store folder.

  See Organizing Bot Store Digital Workers and bots.

• This enables you to configure the required parameters and bot codes, which are not exposed for the protected bots. Vendor IP or the IP of the original author of the bot is now secured when viewing and playing the protected bots downloaded from the Bot Store. The source code of the protected bot or MetaBot is also not exposed. However, you can configure the value of the variables used in the protected bot or MetaBot. See Viewing and playing protected bots.

Support for PowerBuilder platform 10.5 (Zendesk # 86557, 98160, 140835)

The Object Cloning command now supports the PowerBuilder platform 10.5. This enables you to capture and play the control actions for the applications built on the PowerBuilder 10.5. Some of the Object Cloning actions might not function as expected. See Troubleshooting PowerBuilder platform controls.

HTML technology is now supported for Object cloning using Mozilla Firefox.

MetaBot support for HTML and UIAutomation is also enabled for Google Chrome.

Bot Lifecycle Management support

See Enterprise 11 Bot Lifecycle Management.

See Enterprise 11 roles.

My Tasks > Service Insights

See Managing COE dashboards across environments.

• Device Status
• Device Schedules
• Top Error Messages

See Configuring a COE dashboard.

You can upgrade the Control Room with fewer input as the setup enables you to continue using the previous configurations such as the mode of setup and database type. You are, however, allowed to update the password on the service credentials page and database port number.

See Enterprise 11: Define work item structure.

For example, two Bot Runners that have finished processing work items from Queue 1 are utilized to run work items from Queue 2 instead of waiting for Queue 1 to finish the deployment.

See Monitor in progress activity and Enterprise 11: View work items.

See Enterprise 11: Define work item structure.

See Manage historical activity.

Also, when you alter any settings under Options, the application does not validate the Port number in the Advanced Settings.

See Using Advanced Settings.

See Email Automation command.

See Using the REST Web Service Command.

See Terminal Emulator command.

See Terminal Emulator command.

When a command returns an array type variable, you can store it in the value type variable. In this condition, a separator must be used. The available separators are space (default value), comma, semicolon, hyphen, colon, and period.

<InputParameters>
   <Parameter>
        <Name>$Vinputpara$</Name>
        <Value>$Vmihirinput(Vinput)$</Value>
        <Type>Value</Type>
   </Parameter>
</InputParameters>

<retainexcelcellrowlegacybehavior>

• In progress
• Completed Successfully
• Canceled
• Failed
• Timed Out

See Bot Insight task log data.

The configuration change is to include the following within the <player> tag in the AA.Settings.xml file:

The Visual log file of the Report Designer now shows the correct From and To dates.

The Insert Keystrokes command now works properly with the TN3270 Terminal Emulator using the Advanced Technology. The Send Text option sends all the specified text on the Terminal Emulator screen before the next command is executed.

When you edit a TaskBot t