Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Hello there,

We are glad to inform you that the latest 2022.21 versionof the SWAT Framework is out. Below is the list of issues thatare part of this release.

New Features

Priority Key Akioma Release Notes
Medium SWAT-7173 Extended {{.build/build-app-database.sh}} database build to support custom scripts.
Medium SWAT-6833 Modernized calls from webUi to backend with axios https://www.npmjs.com/package/axios.
Replaced: native fetch, http.js, XMLHttpRequest, jquery HTTP calls.
Medium SWAT-6121 Added {{freeHand}} control. Can be used to draw on a canvas with cursor input.

Available via {{akioma.swat.FreeHand}}

Tasks

Priority Key Akioma Release Notes
High SWAT-7215 Introduced production mode for all nodejs docker containers
Highest SWAT-7207 Updated "@xmldom/xmldom": "0.8.3" to "@xmldom/xmldom": "0.8.4" due to a security vulnerability
Medium SWAT-7202 Updated SCL to Release 11.7 #72746@2022-10-30 UTF-8

Bugs

Priority Key Akioma Release Notes
Highest SWAT-7229 Fixed issue where ui cache was not backwards compatible
Medium SWAT-7224 Fixed issue with faulty access to {{getValue()}} in {{dynSelect}}
Highest SWAT-7222 Updated "loader-utils" to "2.0.3" due to a security vulnerability.
Highest SWAT-7199 Updated "socket.io-client": "^4.4.1" to "socket.io-client": "^4.5.3" due to security vulnerabilities
Medium SWAT-7196 Fixed error where files generated by PASOE were not downloadable from docker container, due to wrong UMASK.
Highest SWAT-7172 Fixed issue with settings links in primaryDSOs. Introduced method to {{FetchSupportedLinkTypes}}
High SWAT-7171 Added jms adapter to OE-build and workspace docker images.
Medium SWAT-7169 Fixed error with infinite loading in designer, you to unresolved deferred promises.
High SWAT-7102 Fixed bug with where object in ribbon could not be expanded anymore, due to a typo in case sensitivity.
High SWAT-7035 Fixed a bug in Tabbar that created issues with visibility rules.

In {{Tabbar.ts}} {{setActivePage}} we removed a check, that checked if active page is a dynObject and then reset {{_visibilityRules}} to an empty array.

Looking forward to hear your feedback.

Thanks,
Build.OneTeam

  • No labels