Changes for page 256 - Power Up
Last modified by Erik Bakker on 2025/11/04 12:44
From version 283.1
edited by Erik Bakker
on 2025/10/09 09:19
on 2025/10/09 09:19
Change comment:
There is no comment for this version
To version 173.1
edited by CarlijnKokkeler
on 2023/12/21 16:12
on 2023/12/21 16:12
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 54-OtherOne1 +211 - Log Luminary - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,22 +1,19 @@ 1 - This releasefeaturesvariousupdatestoourplatform,withauser-centricfocus,aswework onwrappingup improvedfunctionalityfor our neweventstreamingbroker. Allthoseimprovements will be shared inthefuture once everythingisready.Additionally,wewill releasenew**[[environment templates>>Main.ReleaseInformation.CloudTemplates.WebHome||target="blank"]]**toupdate ourunderlyinglibraries.1 +In the last sprint cycle, we focused on improving several aspects related overviews and logging. It is now possible to see an overview of all runtimes on running machines, see runtimes and flow versions in the missing properties overview, and see which runtimes will be restarted or redeployed in a pop-up displayed when starting the deployment plan. Moreover, crash handling has been improved, as well as runtime logging and the display of the deployment execution error message. Lastly, several other minor changes and bug fixes have been done, mainly relating to the Deploy and Manage phase. 2 2 3 -Please find out more on our [[Release blog>> doc:Main.Release Information.Release Blogs.254-Other One.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.211 - Log Luminary||target="blank"]]. 4 4 5 -==== Minor changes====5 +=====New features===== 6 6 7 -* General - Cloud Template: A new [[environment template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]], for every type of **cloud** we offer, is available that updates underlying libraries. 8 -* General - eMagiz Store: Introduced a new state generation license type for store items. This license is now required for models intending to utilize store items that depend on state generation capabilities. (#1400) 9 -* Capture - Settings - Integrations: Update column label to be more consistent (#1710) 10 -* Design - Data model: When you change the data type of the attribute in the Design phase while a flow has a transformation in Create, before saving the changes, you will see the confirmation popup with the warning message because the changes will impact your transformation in Create. (#1163) 11 -* Create - Flow testing: Specifying the type of a header on a test message has been made simpler: Instead of having to type the class name, the most common types can now be selected in a dropdown menu instead. It is still possible to provide a custom type. (#1711) 12 -* Deploy - Architecture: We added the refresh button in the footer of the “Runtime details” popup in the Deploy Architecture. (#1708) 13 13 14 -==== Bug fixes ==== 15 15 16 -* Create - Flow designer: Resolved the issue where resizing columns in the ‘Java mail sender’ support object would make the columns ‘stick’ to the mouse. (#1320) 17 -* Create - Flow designer: Several broken Spring documentation references in help texts are updated to new documentation pages. (#1534) 18 -* Deploy - Releases: Changed the text on the wrench icon when hovering for the create phase release to “Property configuration“ to differentiate it from regular property releases. (#1571) 19 -* Deploy - Releases: Resolved the issue where resizing columns in the 'Compare properties' would prevent further interactions with the popup. (#1668) 20 -* Deploy - Releases: Warning message showing the set advised number of flows per container is fixed to show the correct number when a release is approved for the next environment. (#1059) 9 +=====Minor changes===== 21 21 11 +* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start. 22 22 13 + 14 + 15 +====Bug fixes==== 16 + 17 + 18 + 19 +