You are reading the documentation for an outdated Corteza release. 2023.9 is the latest stable Corteza release.

Upgrade Guide

This guide will help you upgrade your Corteza to the newest version in no time!

If you are upgrading multiple versions at the same time; for example from 2019.12 to 2020.9; you should follow all of the upgrade guides between the two versions.

Upgrading to 2020.9

After upgrade

Corteza Service Cloud

Corteza 2020.9 renames Corteza Service Cloud to Corteza Service Solution. The new automation scripts are not compatible with the previous namespace.

Follow this set of steps to properly update your instance:

  1. Rename the Service Cloud namespace name to Corteza Service Solution

  2. Change the service-cloud namespace slug to service-solution

  3. Go over each page in the Corteza Service Solution namespace and replace the old service-cloud automation buttons with new service-solution buttons

  4. Test your changes to assure everything works as expected

Archive

Upgrading to 2020.3

After 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 will 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 system script-migrator --dst 
docker-compose exec server compose script-migrator --dst

These two commands will 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 will create script source files (javascript) directly to the recommended location.

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).