...
Use the System Exporter and System Importer to compile, export, and import Workflow Packages. To automate the steps in the CI/CD process use the mzcli command packageexport [hide](2.3[/hide]) to build Workflow Packages from the command line, and use the command systemimport [hide](2.3[/hide]) to import the Workflow Packages as MZP files.
| Note | ||
|---|---|---|
| ||
See the section mzcli for a complete list of supported mzcli commands. |
...
- Selected workflows with all their dependencies (profiles, Ultra, APL, etc).
- All code necessary to execute the workflows.
- A package information file containing information about which exact version each configuration was generated in, so that the system can detect a mismatch between the system it runs on and the system it was generated on.
Rollback
Since a Workflow Package is a fixed, unmodifiable version of workflows and other configuration, the only action needed for a rollback is to switch to the version in which the workflow package is executed. However, if the rollback is performed because of errors in the latest package, it is recommended to remove that package from the system.
| Note | ||
|---|---|---|
| ||
To rollback a scheduled Workflow Package it is recommended to change the scheduling settings without removing the package. |
Upgrade
When a Workflow Package is installed or is upgraded, the package content is always validated against the system version. A workflow package can consist of generated code and if the code generation version differs between the and the package, the package is then flagged as outdated. In this case, a new package must be createdon a installation with the same version before continuing.
...