We have managed to include certain awesome features to SIL 4.0, we simplified the apps administration and configuration. The following changes and improvements applied to all our apps are available free of charge to users who leverage the benefits of the cPrime app suite.
...
This version presents some incompatibilities with previous version. You are required to take all the necessary precautions when upgrading katl-commons to SIL Engine™ to the 4.0.0 level and above.
| Warning |
|---|
Always test your migration path before applying the upgrade in production! Do backups before! |
...
The following table lists the incompatibilities and reasons, along with their solutions.
| Where / Functionality affected | Risk | Motivation | How to deal with it | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Scheduling |
| Scheduled tasks became permanent. Because of that, the previous rules linked to the distinct task as well as the keys of the scheduled tasks have been changed to reflect the new concept. | Mitigation / solutions may be found in the corresponding section: Scheduling routines. The identified risk is low, but make sure you have a good grasp of the change. You will need to modify the scripts to reflect it. | ||||||
| Mail Templates |
| Previous versions did a simple search / replace over variables defined between dollar signs (e.g. $var$). If one variable was missing, it was just skipped, and an error was logged. With the introduction of STL, the produced intermediate SIL script syntax must be valid, and all custom fields and variables must exist in the scope. | You will need to correct your mail templates. Make sure all variables are defined. You will find more information about the STL in its dedicated section: SIL Template language. The ending SIL script must be valid syntactically. |