Changes for page 237 - Fabulous Flow
Last modified by Erik Bakker on 2025/01/31 11:52
From 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
To version 106.1
edited by Erik Bakker
on 2023/09/15 08:33
on 2023/09/15 08:33
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 197-PayAttention1 +205 - World Explorers - Content
-
... ... @@ -1,26 +1,24 @@ 1 - Another coupleofweekshave passed,soitis timeforanewrelease.We havedeliveredadditionalminor(bug) fixes inthisreleaseandreleasedtheevent streaming alerting.The lastis arealimprovementin managingyoureventstreamingsolution.Furthermore,youwillfindseveralenhancementsinworkinginnextGenenvironments.1 +In the last sprint cycle, we focused on what we show in Manage concerning the next-generation architecture. Furthermore, we will release a new cloud template. On top of that, we will release several minor changes with a potentially significant impact. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs. 197-PayAttention.WebHome||target=3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.205 - World Explorers.WebHome||target="blank"]]. 4 4 5 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. 6 +* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture in the mount configuration of our file storage solution used on the model level. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information. 8 8 9 9 =====Minor changes===== 10 10 11 -* Create - FlowTesting: wedd some minorUI improvementsandvalidationtopreventatestcase frombeinginlivemodeandautomated.12 -* Deploy - Deploymentplan:Ifyourun thedeploymentplan to deploymachinesand runinto issues, your deploymentplan will be stoppedatthetep thatgetsawarning,and youcan seeawarningmessageon theleftside. That iseasierfor youtoigureoutproblemsandfixthem.Afterward, youcanrunthatstepagainby selecting "Refresh"and"Execute."13 -* Deploy-Architecture:We increasedthe graceperiod foruttingdownruntimeswhentheyrunonDockerenvironments.10 +* Create - 3rd Generation runtime migration: Your containers will be validated to function with the 3rd generation structure before you approve the migration. 11 +* Deploy - Architecture: The container calculations are improved. For event streaming containers, these show the number of topic proccessors deployed. Gateway containers represent the amount of operations deployed on a container. For JMS containers, these represent the number of message queues deployed. The other types of containers display the amount of integrations deployed. (#544) (#869) 12 +* Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change, and can be multiply selected. (#1046) 14 14 15 15 ====Bug fixes==== 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) 16 +* Deploy - Architecture: Users with edit rights in deploy can edit certificates. (#1054) 17 +* Deploy - Containers: We fixed an issue that some unconfigured flows are deployed incorrectly in the new generation runtimes. 18 +* General: In some places, the context menu showed too much horizontal whitespace; this has been fixed. 19 +* Create - Flow Designer: Flow designer styling implementation has been updated as part of a set of measures to solve styling issues. 23 23 24 -====Remarks==== 25 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. 22 +=====Infra and image changes===== 23 + 24 +* No infra and/or image changes is this release.