Planet Crust has released a new update of Corteza with several new features, such as record list filter preservation in the local browser storage. Additionally, a list of changes and fixes is included.
Release notes:
-
- Added an empty check for module field name validation (
d3c33a6
). - Added more descriptive tab titles based on what page the user is currently on (
d6bb352
,a7f36e5
). - Added record list filter preservation in the local browser storage (
52ff728
,bc2dd98
). Note that the saved filters are only available on the browser they were saved in.
- Changed static translations for Low Code modules (
5efb7c9
) and integration gateway filters (98f8e4b
). - Changed resource configuration input states to be more consistent (
2ef02c5
). - Changed date-time record filter format template to ignore seconds (
fc2eab1
,07c409e
). - Changed resource activity log store definitions to be more restrictive and less flexible (
e7ed1d8
). - Changed record module fields to show a user-friendly label of the nested user field instead of the user ID (
0d4d74b
). - Changed chart configuration by hiding the “add metric” button when no module is selected (
a3177bc
).
- Fixed queue search on the Admin web application (
98a5d95
,e6a0b0f
). - Fixed integration gateway route search on the Admin web application (
f821dd8
,5ddddf8
). - Fixed broken resource translation migration when the related resource was deleted (
1786eda
). - Fixed chart configuration’s improper error handling (
d4bf472
) and improper state handling when a new chart was created (41b0a15
). - Fixed improper resource translation handling for Low Code module field’s hint and description properties. The two properties were flipped (
q7fbaf94
,1c6b793
), incorrectly removed from resource translations when removed in the field configuration popup (d4c9243
), and not reflected on the web application (18de72f
). - Fixed charts failing to load in cases of incorrect state management (
629d306
). - Fixed record list filter not resetting when deleting filter rows (
00b491d
). - Fixed improper authentication scenarios loading when running the in development mode (
d280fc7
). - Fixed improper refresh token expiration. When new refresh tokens got issued they did not adjust the expiration timestamps (
e7d3df1
). - Fixed new Low Code record pages failing to load due to missing button definitions (
b135287
). - Fixed item selection lists (primarily module fields) where the item would get duplicated (
9a33368
). - Fixed the system crashing once user attempts to exchange invalid credentials by redirecting them to the login page (
0c49832e
). - Fixed improper
peer-closed
connection error handling which needlessly spammed error tracking systems (ab248fe1
).
- Added an empty check for module field name validation (
View the full changelog.
How to install Corteza
You can follow the local setup instructions for a local development or demonstration instance of Corteza. If you are looking for setting up a live deployment, check out the extensive production setup instructions. If you have questions, you can engage with other community members on the Corteza forum.
How to upgrade your Corteza instance
To upgrade your instance to the latest version of Corteza, follow our Upgrade Guide.
About Planet Crust
Planet Crust is the creator of and driving force behind Corteza, a 100% open-source low-code rapid application development, business process management and integration platform for software vendors, system integrators and internal development teams. For more information or to try Corteza on the cloud, please visit www.planetcrust.com.
About Corteza
Corteza is a 100% open-source low-code rapid application development, business process management and integration platform for software vendors, system integrators and internal development teams. Corteza comes with an Apache 2.0 license and all code is published and can be reviewed at https://github.com/cortezaproject. All Corteza code is contributed to the Commons Conservancy Software Foundation. To stay up-to-date on the project, follow @CortezaProject on Twitter.
Leave a Reply
Want to join the discussion?Feel free to contribute!