Migration Process - For Customizations

Different types of customization migrations are explained below.

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 19.0 *.conf file located at <<AssistEdge Build Folder>>\AssistEdgeAutomation\runtime\generic\logstash\logstash-6.7.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. See Database Migration for more details on it.

Custom Code for Microbots

  1. DLLs get migrated with DB. See Database Migration for more details on it.
  2. Export the microbots from previous version, and then import them to the migrated setup.

EV Notification Customization Migration

To migrate the customized notifications/alerts from the previous version to the new version:

  • 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 from in Customization Guide.
    • To know more about 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\

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