...
We are glad to inform you that the latest 2022.20.03 versionof the SWAT Framework is out. Below is the list of issues thatare part of this release.
New Features
| Priority | Key | Akioma Release Notes |
|---|---|---|
 | SWAT-7255 | Extended DynSelect |
with option to enable and disable preSelectExistingInput(); enablePreSelectExistingInput(); disablePreSelectExistingInput(); | ||
| SWAT-5207 | Required validation rule and required attribute are now synchronised |
Bugs
| Priority | Key | Akioma Release Notes |
|---|---|---|
| SWAT-7309 | Fixed error header in Datagrid2 , which threw an error when oHeader |
| object is not available. Past behaviour was returning false , and has been returned to the previous state. | ||
 | SWAT-7308 | Extended repository caches to |
| account for dynamic screen definitions so multiple dynamic forms open correctly. | ||
| SWAT-7306 | A copy of the dependency SmartComponentLibrary |
accidentally overrode Consultingwerk.Util.DatabaseHelper |
| and rendered the update to that class unnoticed for applications utilizing SWAT. Removed src/backend/Consultingwerk/Util/DatabaseHelper.cls |
| which is not overridden anymore. | ||
| SWAT-7298 | The hasChanges |
trigger was executed on disabled fields because it was only checked for attribute 'readonly' === 'readonly' . Extended check |
to 'readonly' !== undefined && 'readonly' !== false | ||
| SWAT-7254 | Clicking in form fields without making changes marks it with hasChanges() == true . Fixed error by checking only for input type 'number' |
and 'string' |
| to mark field |
as hasChanges() = true; |
Looking forward to hear your feedback.
...