Changes for page 220 - Patch Parade
Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 17.1
edited by Erik Bakker
on 2022/11/08 08:30
on 2022/11/08 08:30
Change comment:
There is no comment for this version
To version 174.1
edited by Carlijn Kokkeler
on 2023/12/21 16:18
on 2023/12/21 16:18
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 -1 87-IntegrationSponsor1 +211 - Log Luminary - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,25 +1,31 @@ 1 - The releasebringsthenextpof theDesign storeto thepublicandreleases aew versionoftheeMagizMendixConnector thatunlocksthoseusingittomigrate tothenextgeneration runtime.On top of that,wehave severalfeedbackitems and bug fixes.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>>Main.Release Information.Release Blogs.1 87-IntegrationSponsorSwitch.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 5 =====New features===== 6 -* Design - Store: It is now possible to import Transformations and Data Models from the Store into a model. 7 -** The Design Store can now be opened from the Mapping and Data Model screens as well. 8 -** The Design Store now offers search options to find store items that include Transformations and/or Data Models. 9 -** When importing a Store item with a Transformation and/or Data Model a new merge tool is available to link the Store Items data model to the users data model or to add new attributes/entities to the user data model. 10 -** When importing a Store item with a data model that has been previously linked the links are automatically restored allowing for easy updating of store based Integrations and for easier installation of multiple Store items with the same data model. 11 11 7 +* Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview. 8 +* Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes. 9 + 10 + 11 + 12 + 13 + 12 12 =====Minor changes===== 13 13 14 -* Create-Flowdesigner:Improved the helptexts of theKafka componentstobetterexplain certain performance andload-balancingconsiderations,andadded detailed informationhowmessages (includingheaders) are convertedto/from Kafka records.15 -* Create-eMagizMendixConnectorexit:Downloadbuttonsareddedfor nonlegacyeMagizMendix connectors16 -* Create -Overview: You willnowbeable toseethe errorsthatyouhave withina flow but on theintegrationwidget. Todothis, go intoyour flowand thenumberof errorsyouhaveinit, ifany,willupdatesothatnexttime you don’t haveto navigateinsidethe flowto check how many alerts you have.16 +* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 17 +* Deploy - Architecture: Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'. 18 +* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start. 17 17 18 18 21 + 22 + 23 + 19 19 ====Bug fixes==== 20 -* Design - Store: Importing store item from response messages doesn't cause issues anymore 21 -* Design - Store: Importing response message and transformation to Api integration is possible 22 -* Design - API Gateway: The order of attributes in gateway messages were not always the same as the order in the generated Open API document. 23 -* Create - Flow Designer: Fix bugs when copy and paste components in G3 configuration 24 -* Create - Flow designer - Store: We fixed the maintaining selection of flow flagment from Store. 25 -* Manage - Exceptions of error messages: The count of error messages per exception class are now displayed (#744) 25 + 26 +* Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. 27 +* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by the container. 28 + 29 + 30 + 31 +