Changes for page 237.1 - Fabulous Flow

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-191 - Fifty Fifty
	1	+205 - World Explorers

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.BoukeReitsma

Content

...	...	@@ -1,53 +1,27 @@
1		-The release introduces a lot of minor fixes as a result of our "hackathon" efforts. Subsequently, we will release several 3rd generation runtime offerings.
	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.191 - Fifty Fifty.WebHome||target= "blank"]].
	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 - Architecture: We added the possibility to register network shares in your container volume settings. This enables the use of network shares without having to mount them manually on the host machine and then again on the container level. This option is only available for 3rd generation runtimes that run on-premises.
7		-* Deploy - Containers: In Deploy containers, a 'Debug' option is added for flows on the 3rd generation eMagiz runtime.
8		-** This option will temporarily be available for users on the next generation runtime. It allows one to easily wiretap messages from channels in a flow to a queue, which can then be browsed using the queue browser. One flow can be wiretapped at the time per container.
9		-** To use this option, the model must be fully migrated to Gen3, including the JMS. Additionally, only flows in a container with the Gen3 Debugging components inside the associated container infra flow can be debugged. Please consult the documentation for more information on how to set up debugging on Gen3.
10		-* Manage - Alerting: Five new triggers are available for Model in G3.
11		-** Error Message is to evaluate the headers of the original message which resulted in an error.
12		-** Log Keyword is to evaluate logging messages. You can provide one or several words which you expect in your logging events.
13		-** Queue Consumers is to check whether more than one consumer is expected on the queue level.
14		-** Queue Messages is to configure for queues where more than 100 messages on a queue can occur
15		-** Queue Throughput is to monitor issues with your system by setting thresholds for the number of messages expected to pass through the flow.
	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.
16	16
17	17	=====Minor changes=====
18	18
19		-* Data-Limit: Set data limit per environment.
20		-* Login page: The login page /login.html now redirects to the actual login page /p/login. (#671)
21		-* Create - Flow designer: Removed the unnecessary refresh button from the component creation pop-ups. (#858)
22		-* Create - Flow designer: Properties in the property overview pages are sorted as Test/Acceptance/Production. (#804)
23		-* Create - Flow designer: We improved validation and help text on Wss4J interceptors components. (#733)
24		-* Create-Flow testing: Improved the help text when adding a header type for a test message. It clearly states which Java classes can be used, along with some examples. (#742)
25		-* Deploy - Releases: Setting a release as active by pressing the deploy button creates an entry in the deploy history. (#823)
26		-* Deploy - Releases: We improved the notification pop-ups of failed machine deployments.
27		-* Deploy - Releases: We added column sorting to the pop-up showing the missing properties. (#860)
28		-* Deploy - Architecture: New cloud slots have their auto-upgrade value set to true by default. (#841)
29		-* Deploy - Architecture: A docker container's status is more visible when you open the detail page of the docker container.
30		-* Deploy - Architecture: The instance's state is now visible on the detail page about an instance. (#699)
31		-* Deploy - Architecture: We changed the wake-up time of cloud slots on Fridays to 6:00 UTC so that they no longer fall within our regular deployment windows. (#559)
32		-* Deploy - Architecture: We added runtime memory checks to 'Apply to environment' to prevent invalid deployments. (#719)
33		-* Deploy - Properties: We improved runtime selection when copying properties. (#796)
34		-* Manage - Explore: Improved the displayed error message when a message could not be loaded in the message redelivery screen. (#696)
35		-* Manage - Explore: "Save as test message" button opens a pop-up that allows you to edit your test message's name, description, content, and headers before saving it.
36		-* Manage - HTTP statistics: Fixed a typo in the HTTP statistics dashboard. (#856)
37		-* Manage - Alerting: By default, no filter is applied to the status when navigating to the "Notifications" overview or resetting the filters on the "Notifications" overview. (#486)
	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)
	13	+* Manage - Alerting - Triggers: The non-editable trigger for Event streaming topic size has been changed to trigger on 95% of the configured size instead of 80%.
	14	+* Manage - Monitoring: Viewing runtime, queue, and HTTP statistics are now limited to 7 days at a time. (3rd generation only)
38	38
39		-
40	40	====Bug fixes====
41	41
42		-* Design - Solution design: We hide systems without functional integration now. (#714)
43		-* Create - API Gateway: Security header case insensitive
44		-* Create - Flow designer: Enabling redelivery for your integration is applied after resetting your offramp and exit flow. Before this change, you needed to remove and add the integration to Create phase to use this setting.
45		-* Deploy - Containers: Applied styling to the error pop-up with the list of reasons why a runtime can't be deleted to make it easier to read. (#546)
46		-* Deploy - Architecture: Deploying your model to the cloud for the first time required you to press 'Apply to Environment' twice. This is no longer the case. (#508)
47		-* Deploy-Volumes: Network volumes are visible when the container is not deployed.
48		-* Manage - Monitoring: Fix typo in Event Processors Metrics. (#835)
	18	+* Deploy - Architecture: Users with edit rights in deploy can edit certificates. (#1054)
	19	+* Deploy - Containers: We fixed an issue that some unconfigured flows are deployed incorrectly in the new generation runtimes.
	20	+* Manage - Queue statistics: Models with a vast number of queues will now show all queues. This used to be cut off. (Gen3 only)
	21	+* General: In some places, the context menu showed too much horizontal whitespace; this has been fixed.
	22	+* Create - Flow Designer: Flow designer styling implementation has been updated as part of a set of measures to solve styling issues.
49	49
50		-====Remarks====
51	51
52		-* Mendix Runtime has been upgraded to Mendix 9.21.0.
	25	+=====Infra and image changes=====
53	53
	27	+* No infra and/or image changes is this release.