Migration Process - For Customizations

The different types of migration process for customization are explained below.

• Logstash Customization Migration
• Custome Code Migration
• EV Notification Customization Migration
• Custom Configration in Config Files
  
  

  NOTE:

  The third-party drivers modified in the previous version must be updated in RPA 20.0 post migration. Ensure that the updated drivers are compatible with the available applications.

Logstash Customization Migration

The below steps need to be performed manually as server-side components are not incorporated in workbench.

 

To apply the customizations done in logstash in the previous version to the new version:

1. Go to config folder of logstash of previous version.
2. Copy the customizations done in previous version from rpa_logstash.conf file.
3. Update the respective 20.0 *.conf file located at <<AssistEdge 20.0 Build Folder>>\AssistEdgeAutomation\runtime\generic\logstash\logstash-7.10.2\aeConfig\rpa folder.

Custom Code Migration

This section covers the migration of customized codes for RPA and Microbots.

Custom Code for RPA

DLLs get migrated with database. For more information, see Database Migration.

Custom Code for Microbots

To custome code for Microbots:

1. DLLs get migrated with DB. For more information, see Database Migration.
2. Export the microbots from previous version, and then import them to the migrated setup. For more details, see Automation Studio.

EV Notification Customization Migration

This section explains how to migrate the customized notifications/alerts from the previous version to the new version.

 

To migrate the customized notifications/alerts:

• For AssistEdge 17.5 and earlier versions: 
  
  EV Notification which was available in 17.5 and earlier versions has been replaced with Vanguard. Vanguard was introduced in 17.6 version.
  • To migrate your alerts and notifications customizations to the latest version, see Customizing Alert and Notification section in the Product Customization.
  • For more information on Vanguard configurations, see Configuring Vanguard.
• For AssistEdge 17.6 onwards:
  Copy the customization done in AssistEdge 17.6 version to 19.0:
  • 17.6 SQL path: <<AssistEdge Build Folder>>\RPA18.1\app\Modules\SQL
  • 17.6 Oracle path: <<AssistEdge Build Folder>>\RPA18.1\app\Modules\Oracle
  • 18.1 path: <<AssistEdge Build Folder>>\RPA18.1\app\Modules\Vanguard\Monitor\Xml
  • 19.0 path: <<AssistEdge Build Folder>>\RPA19.0\app\Modules\Vanguard\Monitor\Xml\
  • 20.0: Access Module Configuration > Vanguard tab available in the Admin module of RPA 20.0 instance and make the customization changes that were done to the required alert/notifications. See Module Configuration.

This step is performed manually as server-side components are not incorporated in workbench.

 

Custom Configuration in Config Files

The changes in the config files must be done manually post migration. For more details, see  Module Configuration.