Enterprise A2019.15 Release Notes

Release date: 14 August 2020

Review the new features, supported packages, changed features, fixed features, security fixes, and known limitations in the Enterprise A2019.15 (Build 5933) release. IQ Bot and Discovery Bot are on Build 5931.

Enterprise A2019
Discovery Bot
IQ Bot
Bot Insight
Automation Anywhere Robotic Interface

Enterprise A2019

To verify which Bot Agent version is compatible with this release, see Compatibility with release builds.


New features
Introducing Discovery Bot and Automation Anywhere Robotic Interface Enterprise A2019 Discovery Bot \| Automation Anywhere Robotic Interface
Migration from Enterprise 11 and Enterprise 10 to Enterprise A2019 (currently available only to those in the Migration Early Adopter Program) Enterprise A2019 Migration to Enterprise A2019 is currently only available to select customers through our Migration Early Adopter Program. If you are interested in learning more about this program or a timeline for when migration will be available to all customers, contact your Automation Anywhere representative.
Perform an action on multiple objects of the same type Enterprise A2019 The variable anchor in AISense Recorder enables you to perform an action on multiple objects of the same type. Use variable anchor
Run Enterprise 11 bots from Enterprise A2019 Enterprise A2019 The V11 TaskBot package enables you to run Enterprise 11 bots from Enterprise A2019 in the Enterprise 11 Control Room. V11 Task Bot package
Enhancements to the Interactive forms Enterprise A2019 Interactive forms include the following updates: You can include the Dynamic element of the selected form in the Change label action. In the Dynamic area actions: You can add a maximum of four elements for the Add row in Dynamic area action. In the Add element screen, use additional options from the Type drop-down menu such as Checkbox, Dropdown, File, Snapshot, RadioButton, Text Area, and TextBox. Interactive forms package
Support for interactions with Oracle EBS tables Enterprise A2019 and Community Edition Use the Universal Recorder or the Recorder > Capture action to read data from an Oracle EBS table. The following actions are now supported: Get Total Row Get Total Column Get Cell text by Index Get Cell index by text
Expanded data type support in DLL package Enterprise A2019 and Community Edition The DLL package now accepts dictionary and list variables as input parameters or to hold action output. Using the Run function (Legacy) action
Create device pools using API Enterprise A2019 You can now create a device pool and add unattended Bot Runners to the device pool using an API. This API uses deviceIds, automationScheme, ownerIds, and consumerIds as parameters to create a device pool. Device Pools API


Supported packages
Package	Version
Node Manager	12.1.6000
Application	2.0.0-20200721-221935
App Integration	1.0.0-20200721-221933
Analyze	2.2.3-20200624-011702
Active Directory	2.0.1-20200721-221930
Boolean	2.0.0-20200721-221936
Bot Migration	2.4.0-20200604-174031
Browser	2.0.0-20200721-221938
Clipboard	2.0.0-20200721-221947
Comment	2.0.0-20200721-221948
CSV/TXT	2.0.0-20200726-052504
Database	2.0.0-20200723-022707
Data Table	2.0.0-20200721-222456
Datetime	3.0.1-20200721-222000
Delay	2.1.0-20200721-221959
Dictionary	2.0.0-20200624-041629
Run DLL	2.0.0-20200721-222437
Email	2.0.0-20200721-222003
Error handler	2.0.0-20200721-222009
Excel basic	2.0.0-20200721-222339
Excel advanced	4.0.0-20200723-234413
File	2.1.0-20200624-041638
File & folders	2.1.0-20200721-222011
Folder	2.1.0-20200721-222013
FTP / SFTP	2.0.0-20200721-222017
IF/ELSE	2.0.0-20200721-222021
Image Recognition	2.0.0-20200721-222024
Interactive forms	2.15.0-20200729-084624
IQ Bot	2.0.0-20200415-125005
JavaScript	2.0.0-20200721-222202
Simulate keystrokes	2.1.0-20200721-222204
Legacy Automation	2.0.0-20200721-222207 1.0.0-20200515-133334
List	2.0.0-20200721-222211
Log To File	2.1.0-20200721-222212
Loop	2.0.0-20200721-222213
Message Box	2.0.0-20200721-222213
Migration	2.4.0-20200728-033126
Mouse	2.0.0-20200721-222218
Number	2.0.0-20200721-222224
OCR	2.1.0-20200721-222225s
Office 365 Excel	2.0.0-20200721-222319
Office 365 Calendar	2.0.0-20200721-221944
Office 365 OneDrive	2.0.0-20200721-222326
PDF	2.4.0-20200721-222331
PGP	2.1.0-20200721-222333
Ping	2.0.0-20200721-222334
Printer	2.0.0-20200721-222342
Play Sound	2.0.0-20200721-222335
Prompt	2.0.0-20200721-222344
Python Script	2.0.0-20200721-222345
Recorder	2.0.6-20200626-193519
REST Web Service	2.0.0-20200721-222436
SAP	2.1.0-20200723-234637
Screen	2.0.0-20200721-222442
SNMP	2.0.0-20200721-222445
SOAP Web Service	3.0.0-20200721-222448
String	3.0.0-20200721-222454
System	2.0.0-20200721-222454
Task	2.0.0-20200624-103759
Terminal Emulator	3.2.0-20200721-222500
Trigger Email	1.1.0-20200721-222511
VBScript	2.0.0-20200721-222503
Wait	3.0.0-20200721-222505
Window	2.0.0-20200721-222507
Workload	2.0.1-20200721-222508
XML	2.0.0-20200721-222509


Changed features
User validation for change in authentication type (Service Cloud case ID: 00602788) Enterprise A2019 The username is now validated when an admin user updates the Control Room authentication configuration from Database to SAML (Administration > Settings > User Authentication). An error message appears if the username already exists. Set up SAML authentication
The Before and After fields in the String > Extract action are now optional (Service Cloud case ID: 00617151) Enterprise A2019 and Community Edition Users can now build and run bots that do not have a value in the Before or After fields. This ensures migrated bots that contain the String > Extract action can run without disruption.
Improved debugging for Image Recognition actions Enterprise A2019 and Community Edition When a bot fails while running one of the Image Recognition actions, the captured source and target images are stored in the log folder. Users can review the images to identify issues such as the application image not captured correctly or low quality of the image due to differences in the Bot Creator and Bot Runner devices. Image Recognition package


Fixed features
Service Cloud case ID	Description
00609293	The AATaskName system variable now uses a backslash (\) to support the migration of Enterprise 11 bots that use this variable to Enterprise A2019.
00600367, 00620149	When calling REST APIs for using the REST Web Service command, the API now returns the correct status and the response code.
--	When Work Items are processed for automation in the Bot Agent, you can now view the workload automation name in the Workload > Queue > View Activity in progress and Run bot with queue > View pages, even when the workload automation ID and schedule automation ID are the same in the Control Room database.
00606636	The migration of 11.3.x bots that read a date from a file to an Enterprise A2019 variable now results in the correct date format: dd/mm/yyyy. Previously, a series of numbers were displayed in Enterprise A2019.
00576004	Fixed an issue where some emails were retrieved with HTML tags, even when the user selected the Plain text option.
00585830	Fixed an issue where the Loop > For each meeting in calendar iterator only returned details for the first meeting of the day. Now, the output variable refreshes after each iteration and returns details for each meeting.
00505228, 00576757	When the browser language is set to Japanese, error messages from the Control Room > Administration > Settings > Email page are now displayed correctly. The distorted Japanese character issue is now fixed.
--	You can now check in any forms or bots in the Public folder that were created using any of the earlier versions of Enterprise A2019.
--	You can now use the Get action without any errors for an empty dynamic element of a form during bot runtime.
00575400, 00597633	You can now use Email trigger to start a bot even when Microsoft Office is set to a non-English language.
--	If you are using the Snapshot element, the form is no longer minimized even if you set an invalid file path to save the snapshot during bot runtime.
00566225	If you add a form with a Japanese name, error messages are not displayed during bot runtime.
00571773	If you have added element label or text in Japanese and set Font name > System default, the form elements are now displayed without any distortion during bot runtime. Create a form
00620911	For the Select file element in a form, the file path is now displayed correctly when you select a file with a Japanese name during bot runtime.
--	If a form has a Dynamic field, any errors within any of the available elements are now displayed immediately during bot runtime.
--	An error is now displayed if you use the Tab key to navigate out of the Dropdown element in a form during bot runtime.
00616251	If a Bot Runner (attended or unattended) user is running a bot and an event trigger that is associated with this user starts, the event trigger is now queued and deployed after the current bot has completed.
00557617	The Simulate keystrokes action now supports ASCII characters when the device language is set to Russian.
--	Installing cloud-based license files is now supported on Control Room deployments using Linux CentOS 7.
00615038	All packages and actions now work with the “Portuguese (Brazil)” browser language. Previously, some packages and actions caused an unresponsive Control Room when “Portuguese (Brazil)” was selected as the browser language.
--	You can now reset the password successfully when the service credential expires or is disabled. Previously, users intermittently experienced issues while resetting the password.
--	The default logging for Bot Agent is no longer in debug mode. Previously, debug mode was the default logging, which caused an increase in the number of logs and resulted in high storage space and decreased system performance.
00588077	If you create a copy or edit the content of an existing CSV file, the modified content that is uploaded in the Control Room will now display correctly and will not cause any run-time error when the bot is executed.
00541524,00531540	You can now run bots even when the path of the bot location is more than 255 characters. Previously, the bot failed with an error.
00615106	The Bot Scanner now analyzes large bots within a few minutes.
00610366	Keyboard shortcuts such as Ctrl+C, Ctrl+V, and Ctrl+X work as expected on Internet Explorer.
00577850, 00608065, 00597132, 00596397, 00619463	The Control Room now does not become unresponsive after a period of inactivity.
00608824	An error is no longer encountered when a bot opens the Excel application after it is forcefully terminated.
00542144	The wait option in various packages now works as expected for applications based on HTML technology. Previously, the wait option used to wait for a period in multiples of 15 seconds based on the value provided. For example, if the wait value was in the range of 1-14, the system waited for 15 seconds.
00508478, 00504802, 00569822	An error is no longer encountered when a bot is running and an application window is closed when the bot is performing the find window operation.
00494857	A user that does not have the Register device permission can no longer register a device by creating a custom Bot Creator role.
00501619, 00614130, 00620198	An error is no longer encountered when a user deletes a device after upgrading to a later version of Enterprise A2019.
00616786	Fixed an issue where periodic scheduled bot deployments failed with the following error message (even though the credentials provided by the bot is correct): `Either your username or your password is incorrect. This might be due to a misspelling, your Caps Lock might be on, the password might have expired, or the domain might be required. To continue, retype your username and password.`
00494893	Fixed an issue where the Error handling > Catch action was not handling a runtime error with the record variable. Previously, the Catch action did not capture an `index out of bounds` error when the record variable was entered in a Message box action with the index specified by name.
--	The Get Property datetime format within the Active Directory package now displays the information using the system datetime format.
--	When you edit a bot using a previous package version (for example, Enterprise A2019.13 version) and the Desktop session automatically starts, if you exit the Bot editor while the Desktop session is trying to launch, the current package version will now be displayed when you open a new Bot editor instance. Previously, the previous package version (for example, Enterprise A2019.13 version) was displayed.
00563346	Credentials with non-ASCII characters are now allowed to be stored in the Credential Vault in the Control Room. Therefore, when you run TaskBots to open files that are protected using passwords containing non-ASCII characters, the application does not respond with an HTTP 500 error.
00525552, 00470841	The Run task no longer fails when the child bot name contains allowed special characters. Previously, when the child bot name contained allowed special characters, the run task displayed an error message.
00501212	Fixed an issue in the SMTP settings where the Control Room was sending notification emails for all of the conditions, including the disabled conditions.
00607005	A security scan of Enterprise A2019 no longer reports the Recorder package as a malicious software. Previously, the security scan reported it as a malicious software because the check.exe file was missing the root identification certificate.
00564129	On an operating system configured for Japanese, the Roles pages in the Control Room now shows English text as expected when you select English in the Control Room language selection.
00629523	When you upgrade from an earlier version of Enterprise A2019 to a later version and change the If package version to the latest one, conditions combined with the AND or OR condition now appear in the logic. Previously, except for the first condition, the rest of the conditions with the AND or OR condition were not shown.
00631477	When Work Items from multiple queues are processed for Workload automation from one device pool with the round-robin method for a time slice of 5 minutes, the Workload automation does not run in a loop and thereby causing an increased CPU usage.
00633829	As system admin permissions for Workload automation are verified by the application when you run a bot with queue from a single device pool to process multiple Work Items concurrently, CPU usage does not increase drastically.
00615086	Fixed an issue where the Java Application Launcher continued to run after a user stopped the Bot Scanner, which caused device performance issues for some users.
--	Variables of the List type are now available for migration from Enterprise 10 andEnterprise 11 to Enterprise A2019.
00607949	Disabled packages will not be enabled when you upgrade from an earlier version of Enterprise A2019 to a later version. Previously, packages that were disabled were enabled after an upgrade.
--	You can now debug a bot with watch variables that contain Japanese characters. Previously, watch variables containing Japanese characters did not output a value.
00623186, 00624876, 00624060, 00627123, 00629873, 00639523, 00630880, 00634577, 00636166	The correct status of a deployed bot now appears instead of `Device yet to be determined` in the Control Room Activity page, and the user is allowed to delete the device that has completed running a bot. The following message no longer appears: `Device is part of active deployment`.
00573461	Fixed an issue where a bot was failing in preprocessing mode if the user had inserted and then disabled the Error Handler > Catch action without also disabling the Finally or Catch actions.
00629046	In the Database package, when you use Microsoft Excel as a database, the bot launcher now executes properly. Previously, the bot launcher stopped working when reading data from an Excel sheet that had some empty rows.


Security fixes
Service Cloud case ID	Description
00491697	The Transport Layer Security (TLS) protocol using CBC mode of encryption for configuring the network security of the Control Room is now secured from man-in-the-middle or cyrstallographic timing attack.


Known limitations
When you add a form with the Dynamic element to a bot, click Add element, select Dropdown or Radio group as the Type, and leave the Default value/ Default path field blank, the elements appear as labels during bot runtime.
You can move a form around by dragging the title bar during bot runtime.
When you copy and paste the filepath for the Select file element of a form during bot runtime, invalid characters are displayed.
When the Set focus action is assigned to a disabled form element, an error icon is displayed when the focus is lost during bot runtime.
When you enable any of the disabled fields during bot runtime, error icons are not displayed.
Error messages during bot runtime are not displayed in the language selected in the Control Room.
If email trigger is used to start a bot, the status of the most recent email that you have viewed is changed to Unread every time any bot is triggered based on the trigger interval set in the Check every drop-down menu.
In an Control Room configured for Active Directory users, the following message appears after the first admin user is created: `Do you want to leave this page?` Workaround: Click Stay on page so that you can go to the Control Room login page.
If the device is already registered by a user other than the Bot Creator and the Bot Creator has the Register device permission, then when you run a bot from the Bot editor window, the deployment fails at the `Connecting your computer to Enterprise Control Room` step.
The migration process does not migrate manual dependency files added in the Enterprise 11 Control Room using the API. Bots associated with these dependencies will be migrated successfully but will fail during execution because the system cannot find these dynamically added dependency files at runtime in Enterprise A2019.
When a bot execution is in progress and the Control Room server refreshes, the progress status of the In-Progress activity will not be displayed even though the bot execution continues without interruption.

Discovery Bot

Introduction

Discovery Bot enables process automation by capturing document processes, identifying automation opportunities from business processes, and prioritizing opportunities based on ROI. Users can convert these opportunities into automated processes.

Process discovery by using Discovery Bot


Known limitations
Discovery Bot is not supported in high availability (HA) mode. When two Control Room instances are used in a cluster configuration, the recording artifacts are split between the two Control Room instances and the recording might fail to process. Workaround: To enable Discovery Bot in HA mode, you must update the processdiscovery.properties file to point to the repository path specified in the Control Room: From the Control Room, go to Administration > Settings > General. Select the Control Room Database and Software tab. Scroll to the Control Room Repository section. Copy the path specified in the Repository path field. Go to C:\Program Files\Automation Anywhere\Enterprise\config. Open the processdiscovery.properties file. In the processdiscovery.data.staging path, paste the repository path in the <yournetworkshareddrive> here: \\<yournetworkshareddrive>\\Processdiscovery\\staging\\data Restart the Discovery Bot service.
When HTTP proxy is installed in a cloud environment, you can use the Discovery Bot recorder to record processes.
Custom role setup for Discovery Bot is currently not supported.
The Discovery Bot recorder continues to record your steps even after you have logged out of the Control Room. Recommendation： Manually stop the recorder to end the recording session.
The Discovery Bot recorder displays an internal error message when accessing Google Apps. Pause the recording and then resume the recording again to recapture the steps.
The recent recording (ID) created is displayed at the end of the list in the Recordings table. You cannot sort on the recording ID at this time.
The recording count for a process is incremented by one even if a user stops or cancels a recording session. The incremented number is displayed in the Recordings section in the tile for a process.
By default, you cannot move the endpoint in an upward direction in the path flow to change the selection of the steps. You can move the branch endpoint lower in the path flow to include more than one step.
You must add at least one step to a branch for you to select the branch and create an opportunity.
You must select all steps in a branch to create an opportunity. Selecting partial steps in a branch will result in branch being dropped in the opportunity that is displayed from the Opportunities tab.
Currently, the copy of field does not display the correct view information from the view (view ID) that it is copied from.
If the Control Room is not installed in the C:\ drive ( C:\Program Files\Automation\Enterprise), the Discovery Bot installer fails to install correctly. If the Control Room is not installed in the C:\ drive, then perform the instructions provided in this article:A2019.15 Discovery Bot installation issue with non-OS drive (A-People login required).
The Export to Word option supports a maximum of 500 steps.
The Convert to Bot option supports a maximum of 500 steps.


Changed features
.

IQ Bot

Review the compatibility of the IQ Bot On-Premises version with the corresponding Control Room On-Premises version.

Automation 360 IQ Bot version compatibility

For feature information about IQ Bot, see Automation 360 IQ Bot feature comparison matrix.

The IQ Bot Cloud version provides users with automatic provisioning for up to three environments such as Development, Test, and Production.

注： IQ Bot Build 5931 is compatible with Enterprise A2019 Build 5933.


New features
New IQ Bot Pre-processor package On-Premises and Cloud The following new actions are available as part of the IQ Bot package: Convert image to PDF Get barcodes Get document info Get page content IQ Bot Pre-processor package
Search by filename in Validator On-Premises and Cloud (Service Cloud case ID: 00372981) Use the Search by filename field in the Validator screen to search a document in IQ Bot. IQ bot Validator enhancements
IQ Bot [Local Device] package (currently available on request only) On-Premises and Cloud 重要： Contact your Automation Anywhere representative to request the On-Premises package. For Cloud, it is available as a pre-installed package. Use the IQ Bot [Local Device] > Process documents action to process documents using TaskBots created in the Control Room. You can scale by processing documents on multiple devices simultaneously without setting up a separate IQ Bot cluster. You can set this up using workload management in the Control Room. Workload management The validation is done using the current IQ Bot Validator and usage metrics on the dashboards, which is available with the installed IQ Bot server. 注： You can create validators using interactive forms if they do not want to send data to the IQ Bot server. IQ Bot [Local Device] package
IQ Bot Classifier package (currently available on request only) On-Premises and Cloud The IQ Bot Classifier package enables you to group documents into appropriate learning instances for content extraction. This package is not available as part of the standard IQ Bot installation. 重要： Contact your Automation Anywhere representative to request the package. IQ Bot Classifier package
Migrate learning instances using Migration Utility On-Premises and Cloud Use the Migration Utility feature to migrate learning instances from one environment to another. Additionally, you can back up, restore, download, delete, and upload learning instances. Migrate learning instances
Control creation of groups On-Premises and Cloud Use the New groups creation setting section in the Learning Instance > Edit page to limit creating groups when uploading training documents to IQ Bot. Use the Threshold to create new groups value and Never create new groups check box to define the parameters. Bots


Changed features
For the Custom Logic feature, the identified list of Python libraries now includes an additional set of trusted libraries for IQ Bot On-Premises and Cloud. Go to Automation Anywhere support for a list of the safe libraries you can use. List of Pandas Libraries which are supported and not supported on Automation 360 IQ Bot (A-People login required)


Fixed features
Service Cloud case ID	Description
00376179	The Automation Anywhere Cognitive Project is now created without any errors even when you use the IQ Bot batch files to install or uninstall IQ Bot.
00560185	The Download Document in IQ Bot now runs without any errors, irrespective of the language in which the learning instances are saved.
00574815	You can now use the Google Vision API engine to classify the selected PDF files without creating any unclassified groups.
--	Documents are now classified correctly by the Google Vision API, irrespective of the display limitations set. Previously, an incorrect resolution limitation created unclassified documents.
--	You can now use Internet Explorer to save a document or mark it as invalid in the learning instances validator screen, without any error messages.
00620237, 00623175	After logging in to the Control Room as an IQ Bot administrator, the IQ Bot tab is no longer displayed in the navigation bar.
--	The Output.csv file generated for a validated document and validated data are now displayed without any error messages.
00605607	When you click Save current document in the validator screen, the document is saved without any errors and the corresponding .csv file is created in the output folder.
--	IQ Bot deletes learning instances from Community Edition if they have not had activity in 60 days.


Known limitations
IQ Bot On-Premises and Cloud When you click the Save and go to next group option, the available groups or the learning instances are sometimes not displayed.
IQ Bot On-Premises and Cloud A validation error message along with the corrected field is displayed in the output (.csv) file for documents validated using ValidatorURL.
IQ Bot Cloud (Service Cloud Case ID: 00647700, 00657619, 00656643) The output (.csv) files are not downloaded even when you click Download all documents button, and an error message is displayed. Contact Automation Anywhere support for more information.

Bot Insight


New features
Date Interval option Enterprise A2019 When you create new widgets that support date fields for a group or subgroup, the Date Interval option is enabled with the default option set to Month. Configuring a Line Bar Chart query
New clustered line bar chart widget Enterprise A2019 and Community Edition The Clustered Line Bar Chart widget enables you to view and analyze information about your metrics and attributes. You can provide two metrics and two attributes in your clustered line bar chart. Now when two attributes are selected, a clustered graph grouped by primary and secondary attributes is displayed. Bot Insight visualizations
New Device dashboard in the Operations dashboard Enterprise A2019 and Community Edition The Bot Insight Device dashboard displays various widgets that provide information about the utilization of the machines on which the bots are executed. You can analyze the device utilization and activity history of different Bot Runner machines. Operations dashboard


Fixed features
Service Cloud case ID	Description
00540647	Dates are now displayed correctly on the dashboard after the data is grouped based on the date. Previously, incorrect dates were shown on the dashboard.


Deprecated feature
The Widget Event Distribution by workbench is removed and will no longer be displayed in the Audit Dashboard.

Automation Anywhere Robotic Interface

Introduction

Automation Anywhere Robotic Interface (AARI) enables users to design a process workflow to address their business requirements. The processes incorporate human and bot tasks using forms to define parameters and render supported UI elements on the web. When using AARI on the web, users create requests to use their created process workflow for process instances (case) and run their tasks.

AARI is available as a part of the Enterprise A2019 installer. You can view the AARI components in the Administration page.

Configure roles for AARI on the web

重要： This AARI version has limited availability and is available only to sales and internal users.


Known limitations
When you edit a checked-out process that contains conditional steps with variables, you cannot edit and save these conditional steps. The steps will revert any new variables you add. Workaround: Delete and add a new condition.
The If, Else If, and Else actions cannot be placed before another bot logic in your workflow. You can only place these actions at the end of the bot logic. Workaround: Make a clear boundary on the conditional block.
In a process, when you use a date format such as 2020/07/04 in the input_date field in Bot Task, the bot does not accept the date input. Workaround: Create a separate date variable to use an input.
Form elements that are not supported and are deleted by the process editor include: Button, Dynamic, Select File, and Snapshot. Workaround: Instead of using the Button element, add a form action.
The Import bots and Export bots user interface labels do not match for a process but are still applicable to importing or exporting a process.
When you access a public process, the Request display name field in Process entry is not locked and can be edited. The existing variable in the field can be changed but not saved.
The Task display name option in Process entry has a field set to initialData that cannot be edited in the process editor.
The Feed data into form table in the process editor does not allow editing.
The Element name field in the Bot Task and Human Task cannot contain spaces.
When you create two forms and assign the data of the first form to the second form using $FormStep.input[]$ , the second form data is not evaluated.
Redo functions are only available for canvas interactions. The redo functions are not available by default until your first canvas interaction. The functions are available again when you interact with your second canvas.
A team name that has a length of 20 characters or more is not accepted.
Limitations in AARI on the web Navigation bar When you open too many request tabs, the tabs are hidden in the navigation bar. Timestamp The timestamp of the closing step shows a duplicate timestamp of the starting step in request view. Imported process When you export a process from an Control Room and import that process as public to another Control Room, the imported process cannot be viewed. Workaround: You can check in and then check out the process, or import the process as private and then do a check-in. Configuration page In the device pool configuration page, the Bot Runner users check box cannot be deselected. Workaround: Double-click the check box in the header. Process management page A check-in process that is deleted from the Control Room repository is still visible in the process management page. Form rendering The Masked data option is not fully supported for all elements. When this option is added to hide data, the data is visible. The Checkbox and Radio Button elements do not fully support horizontal format. When these elements are configured to display horizontally, the elements are displayed vertically instead. The Document element is not fully supported. When this element is configured to a Default file path, the entire document is not rendered. The Number element encounters issues with large numbers. When this element is configured to contain three number fields and number values with trailing zeroes, commas, and decimals, these values are not honored and are not rendered. When number values are entered in a number field, such as a phone number box, the number values are not accepted. The Text Box element encounters issues with number-only input. When this element is configured in a form to submit data, the Submit option is not enabled when the field contains only numbers. The Password element encounters issues with maximum character limits. The maximum limit is not enforced when a password is entered in the initial form. This element does not contain values when submitted in the request tab. The Select File element does not support the Open the doc in browser link. When this link is open in the initial form, the link redirects to the web main page. When a process is configured with two forms that contain a Dropdown element, the process creation shares the Dropdown element data between the forms. However, when you view the data in the request tab, the Dropdown element in the second form does not receive data from the first form.