Changes for page 225 - Pop-up Party
Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 262.1
edited by Carlijn Kokkeler
on 2024/06/19 09:27
on 2024/06/19 09:27
Change comment:
There is no comment for this version
To version 81.1
edited by Erik Bakker
on 2023/05/16 09:06
on 2023/05/16 09:06
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 - 223-IdyllicImage1 +197 - Pay Attention - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,17 +1,26 @@ 1 - Inlast sprintcycle,we haveworked onreleasinganew [[runtimeimage>>doc:Main.ReleaseInformation.RuntimeImages.V310.WebHome||target="blank"]],which contains severalbug fixes,andincreases thedebuggerduration.Moreover,wehaveworkedonourSwaggerUIsettings,filtering,and SpEL Expressions. Findoutall featuresandfixesbelow.1 +Another couple of weeks have passed, so it is time for a new release. We have delivered additional minor (bug) fixes in this release and released the event streaming alerting. The last is a real improvement in managing your event streaming solution. Furthermore, you will find several enhancements in working in nextGen environments. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs. 223-IdyllicImage||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.197 - Pay Attention.WebHome||target= "blank"]]. 4 4 5 -====New features==== 6 -* Design - API management: Model contacts are now able to select a default SwaggerUI environment from the API management settings in Design phase. The environment selected here will be the first and the default value of SwaggerUI server dropdown. (#438) 7 -* Capture - Settings: It is now possible to filter the message types in Capture on whether they are used. (#1281) 8 -* Manage - Monitoring: Wiretaps and debugging sessions will now collect messages for 10 minutes, this used to be 5. Note that the JMS server needs to be updated in order to also store the messages for 10 minutes instead of 5. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. Moreover, helptexts have been added for clarification. 5 +=====New features===== 6 +* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information. 7 +* Manage - Alerting: Added support for providing alerts on event streaming topics: consumer lag, topic approaching maximum size & messages added to the topic under the threshold. Two new alerts are introduced to send alerting messages to the user when messages added to the topic is greater than a threshold or when topic messages consumed is below a threshold. These new alerts are applied for all runtime architectures we support. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information. 9 9 9 +=====Minor changes===== 10 + 11 +* Create - Flow Testing: we add some minor UI improvements and validation to prevent a test case from being in live mode and automated. 12 +* Deploy - Deployment plan: If you run the deployment plan to deploy machines and run into issues, your deployment plan will be stopped at the step that gets a warning, and you can see a warning message on the left side. That is easier for you to figure out problems and fix them. Afterward, you can run that step again by selecting "Refresh" and "Execute." 13 +* Deploy - Architecture: We increased the grace period for shutting down runtimes when they run on Docker environments. 14 + 10 10 ====Bug fixes==== 11 -* Create - Flow Designer: The SMB outbound gateway with the GET command did not work, this has been resolved. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. Moreover, helptexts have been added for clarification. 12 -* Create - Flow designer: We fixed a transformation tooling issue where it was not possible to view an XSLT in certain cases. 13 -* Create - Flow Designer: In rare occurences, when a TaskScheduler was used, a deadlock situation could occur due to thread starvation. The number of threads available to the TaskScheduler has been increased to resolve this issue. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. Moreover, helptexts have been added for clarification. 14 -* Create - Flow Designer: The recommended SpEL expression used for contructing a multipart/form-data HTTP request was no longer valid. The [[documentation>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Data Handling.expert-data-handling-multipart-form-data.WebHome||target="blank"]] has been updated with the new standard and the updated expression is now part of our default test suite. (#1215) 15 -* Create - Properties: Support has been added to provide the SFTP session factories with a known_hosts in string format rather than file format, so it is easier to setup SFTP. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. Moreover, helptexts have been added for clarification. 16 16 17 +* Create - Store: We fixed an issue that you sometimes do not see the list of message definitions or the list of transformations when you export new or update your store item. 18 +* Deploy - Architecture: We fixed an issue were some cloud environments would not automatically wake up. (#952) 19 +* Deploy - Architecture: You can apply your changes to only one or both zones on 3rd generation double-lane models. (#947) 20 +* Deploy - Architecture: We fixed an issue where runtimes were not removed from a machine, while this was expected behavior according to the architecture. 21 +* Deploy - Architecture: The gen two karaf container will now exit when an Out-of-memory error occurs for gen three cloud environments. This will cause an auto-healing restart, after which the container can run properly again. Note that to make this functionality available a new "base image" was created which will automatically be applied to all gen two karaf containers when you create a new release and deploy it via the deployment plan causing redeployments. 22 +* Design - Message Definitions: "Message format" button is also available in view mode. (#919) 17 17 24 +====Remarks==== 25 + 26 +* Manage - Statistics: Improved rollup and storage of metrics when running your solution in the next generation archticture. Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off.