Additional Changes

NOTE:  

If you are using an Oracle version prior to 12c migrate the Oracle Database to 12c before performing the Database migration.

 

RPA Process Owner (RPAProcOwner) Access Changes

RPAProcOwner access needs to be updated post migration.

 

Albie Decision Workbench Changes

Albie Decision Workbench is known as Decision Workbench in AE RPA 20.0. Older Albie licenses will not work with 20.0. You are required to upload 20.0 Albie licenses to run the Decision Workbench


Once migration is performed follow the below mentioned steps to use the Albie Decision Workbench (Decision Workbench in AE RPA 20.0):

  1. Access the Admin portal and go to Configuration > Manage Role > Specify Role Access > Assisted Automation > Decision Workbench.
  2. Provide one or more of the required accesses. Available options are- SME1, SME2, and Manager.

Continuous Monitoring - File System Triggers with UNC Path

The file trigger is created in the previous version.Ensure that the migration is complete.

 

To migrate it to the new version:

  1. Login to Control Tower. You need to have RPA_Trigger_Management access.
  2. Go to TRIGGER MANAGER tab.
  3. Disable the Continuous Monitoring File System trigger with UNC Path.
  4. Click Edit trigger icon.
  5. Select the check box for the Is directory path in UNC format option.
  6. Enter credentials and domain for the given UNC path.
  7. Save and Enable the trigger.
  8. Repeat steps 4-7 for all Continuous Monitoring File System trigger with UNC path.

 

NOTE:  
  • Valid Only for file trigger with UNC path (ex : \\12.34.56.789\ABCD\EF\GH), not for file trigger with local path.
  • For file based trigger (UNC Path) user Id and password is required if you are migrating from version previous than 18.x. 

 

Cognitive Service Migration (17.6)

Cognitive Activity (17.6) is deprecated. Newer advanced version (18.0) has been introduced.

 

Cognitive Activity (legacy version:17.6) cannot be edited via Automation Studio but still executable from robot and studio. It is recommended to replace the activity with newer version of cognitive services for future support.

Listener URL in Load Generator process

Once the migration is completed, you need to update the listener URL in the Automation Studio. You get a list of the URLs after the installation is completed. Kindly update the listener url to following endpoint:

 

 <https or http>://<hostname>:<port>/listener/rpa/api/message

 

To update the Listener URL:

  1. Login to Automation Studio.
  2. Go to Application tab. Click the respective Web Api application. 
  3. Update the URL under the Search Properties in the right panel.

 

If listener URL is used in any customization, you must update the same at all places in Automation Studio.


Sample Error:


 

NOTE:  

On test run, if sample error appears, then contact your administrator to setup RabbitMQ credentials using ae rabbitmq command.

 

Upgrade Command in Control Tower

From AssistEdge 18.0, upgrade command has been removed from Control Tower. Patch Management serves the purpose of upgrade functionality in AssistEdge.

 

User Access Restriction in Update Management

User access restriction has been added from 18.1 to prevent unauthorized users from applying patches on other user’s robots. It restricts access to Update Management page in Control Tower.

 

To grant access for different roles:

  1. Super User: Super user can upgrade all Robots and Agents. 
  2. Manager: Manager can access and upgrade robots with profiles that are assigned to the manager.
  3. Robot Owner/Process Owner: Robot Owner can upgrade robots that are assigned to self.
  4. View Only: This feature is valid only with a combination of Super User and Manager access. If this access is checked, users can view the Update Management page; however, the system does not allow to make any modifications. 

Vanguard

For vanguard, existing customization for 18.x version will not work as it is in 19.0. The customization should be changed as per new Vanguard framework. For more information, see Product Customization.

 

Salt and Key

There is a change in default length of Salt and Key used for encryption and decryption of application credentials. For more information, see Advanced Configuration for Key and Salt section in Installation.

 

Integration for CyberArk

19.0 integration with CyberArk is completed through certificate instead of DLL. For more information, see ControlTower.