We've managed to include some awesome features for SIL 4.0, in the sense that we simplified the apps' administration and the configuration of the apps. The following changes and improvements affect ALL applied to all our apps and are available free of charge to ALL who all who use the cPrime app suite, free of charge.
| Table of Contents |
|---|
Configuration Changes
Additional Tables
We have moved everythingpassed all features, including configuration, from the custom tables, and we moved transferred data access to the standard mechanism Jira provides. This is a huge move that will simplify the import / export of Jira.
...
Data sources can now be defined directly from Jira, provided which means you have the driver already in the Jira's 'lib' folder. Of course, the JNDI mechanism still works, but I bet you will find it more convenient to define a datasource directly from the apps, and have the chance to test it before usage.
...
Starting with this version, files may be stored either on disk or in database. We plan to add a feature to move all the files from disk to database or the other way aroundvice versa, again to simplify the management of the instances configuration.
LDAP Support
We now have multiple LDAP support, albeit although only for Microsoft Active Directory. We're still waiting for you to ask us to add support for other LDAP types.
...
Mail support was enhanced as well; we . We added new configuration options, one of which will simplify simplifies the development.
STL - SIL Template Language
A major change is the support for mail templates support (in fact, templates of any kind). We introduced STL (SIL Template Language), a feature that allows you to put snippets of SIL in some file and run embedded programs. The feature matches closely from the syntax point of view closely with JSP in terms of syntax, i.e. you write embedded SIL code within the corpus of the email body.
Other
We unified our thread pools across all add-onsapps. You can see now live the scripts that are running at some point in time so you can adjust your parameters accordinglyalso. Task queue also records the maximal maximum number of jobs waiting to be executed, so make sure you have enough threads.
User Interface Changes
...
You will may notice a lot of changes in the user interface; we . We aligned the add-ons apps to the Atlassian User Interface Recommendations and we introduced new menus and new shortcut links to the configuration sections. We also have changed the editor, adding more support in to it.
Incompatibilities With Previous Versions
This version presents some incompatibilities with previous version. You are required to take all the necessary precautions when upgrading katl-commons to the 4.0.0 level and up.
...
The following table lists the incompatibilities and their motivationsreasons, along with their solutions.
| Where / Functionality affected | Risk | Motivation | How to deal with it | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Scheduling |
| Scheduled tasks have become became permanent. You asked for it, we provided. Because of thisthat, the previous rules linked to the uniqueness of the distinct task as well as the keys of the scheduled tasks have been changed to reflect the new paradigmconcept. | Mitigation / solutions may be found in the corresponding section: Scheduling Routines. The identified risk is low - at least from our point of view - , 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 were doing 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 customfields 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. |
...