Upgrading to 2020.3
After the Upgrade
Corredor Scripts
Corteza 2020.3 introduces a new way of how automation scripts are stored, handled and executed. The code, configuration and triggers are no longer stored in the Corteza database, but are defined as JavaScript files on the filesystem and accessed directly by the Corteza Corredor server.
All pre-installed scripts for the CRM and ServiceCloud have already been migrated and are ready for use.
|
You need to migrate any custom automation scripts manually. |
There are 2 available script-migrator commands, one for system other one for Low Code service:
docker-compose exec server corteza-server system script-migrator --dst
docker-compose exec server corteza-server compose script-migrator --dst These two commands create a simple structure under <base-location>/<service>/custom
(system/custom/ and compose/custom/) containing scripts from both services.
|
The script migrator tool directly exports the script’s source code and triggers without running any checks or tests. Make sure you test each script and trigger after the migration. |
Point script-migrator tool (base-location) to Corredor’s usr/server directory.
This creates script source files (javascript) directly to the recommended location.
The script files' names are created from the script names (with suffixing script ID in case of any duplicated). Migrator skips all deleted scripts, deleted triggers, scripts with "test" name or without any code.
|
If possible, module handle is used where a module is referenced (in Compose scripts). |