Migration Process - For Customizations

The different types of migration process for customization are explained in the following sections.

  1. Logstash Customization Migration
  2. Custom Code Migration
  3. EV Notification Customization Migration
  4. Custom Configurations in Config File

Logstash Customization Migration

You have to perform the following steps manually, as the server-side components are not incorporated in the workbench.

 

To apply the customizations performed 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 3.0 *.conf file located at <<AssistEdge Build Folder>>\AssistEdgeAutomation\runtime\logstash\logstash-8.4.0\Config\ae folder.

Custom Code Migration

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

Custom Code for Engage

DLLs get migrated with database. See Database Migration.

Custom Code for Microbots

To custom code for Microbots:

  1. DLLs get migrated with DB. See Database Migration.
  2. Export the microbots from previous version, and then import them to the migrated setup. For more information, 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 Product Customization.
    • To know more about Vanguard configurations, see Configuring Vanguard in Installation.
  • For AssistEdge 17.6 onwards:

    Copy the customization done in AssistEdge 17.6 version to 3.0:
    • 17.6 SQL path: <<AssistEdge Build Folder>>\RPA17.6\app\Modules\SQL
    • 17.6 Oracle path: <<AssistEdge Build Folder>>\RPA17.6\app\Modules\Oracle
    • 1.1 path: <<AssistEdge Build Folder>>\RPA18.1\app\Modules\Vanguard\Monitor\Xml
    • 2.0 path: <<AssistEdge Build Folder>>\AssistEdgeAutomation\app\Vanguard\Monitor\PredictXml\
    • 3.0: Access Module Configuration > Vanguard tab available in the Admin module of Engage 3.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. Access Module Configuration > Engage tab available in the Admin module of Engage 3.0 instance and make the required configuration changes.  For more details, see  Module Configuration.