Changes for page 204 - Found It

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-202 - New Equilibrium
	1	+197 - Pay Attention

Content

...	...	@@ -1,36 +1,26 @@
1		-In the last sprint cycle, we focused on finishing our work on the release properties functionality introduced in this release. On top of that, we have some additional smaller feedback items and bug fixes coming out of the Hackathon for you.
	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.202 - New Equilibrium.WebHome||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	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	6
7		-* Deploy - Releases: We removed two unnecessary release options: “Set release properties” and “Check properties. “ You can quickly update your properties via the Release properties overview.
8		-* Deploy - Releases: Before activating or deploying a new release, you should fill in all properties that relate to your deployment. If there are any properties without value, we will show them to you. Then you can update them and continue your deployment.
9		-* Deploy - Properties: This tab 'Properties' for managing properties is deprecated as of Release 202. As a result, it cannot be used anymore to manage properties. You can manage your properties via the 'Releases' overview. On this overview, you can select the wrench icon on the 'Create phase release' to find the property management overview. For more information about the management of properties and the related features, click on the right-bottom corner on 'Help and check out our documentation.
10		-* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture to host a MQTT broker in a failover (i.e., double lane) architecture. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
11		-
12	12	=====Minor changes=====
13	13
14		-* Store - Export: "Store exporter" users can test their exported store items immediately without waiting for approval. (#1001)
15		-* Deploy - Releases: The infographic has been updated.
16		-* Deploy - Release Properties: Required properties are checked if they contain nested properties and are not missing values.
17		-* Deploy - Property release: Names of properties can be created/removed/edited.
18		-* Deploy - History: We deprecated the old page History, which displays the property changes in your model. The properties' history is on the Deploy phase's History page.
19		-* Deploy - Architecture: Changes made to AWS Slot settings are recorded in history. (#996)
20		-* Manage - Monitoring: Improved performance of 3rd generation runtime dashboards.
21		-* Infrastructure: Tightened security policies for a more secure infrastructure.
	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.
22	22
23	23	====Bug fixes====
24	24
25		-* Design - Import: Import into design from the store is possible, even if the integration is not in Create yet.
26		-* Create - Flow Designer: Improved validation on XPath header enricher. (#1005)
27		-* Create - Flow Designer: We fixed an issue that your flow fragment metadata disappeared when you canceled your changes of the existing flow fragment in your new version of the store item. (#989)
28		-* Create - Flow Designer: In some cases, when copying/pasting components into a flow, validation alerts would be displayed that did not belong to a component. This problem is now fixed. (#955)
29		-* Create - Flow Designer: We fixed an issue that prevents dragging and dropping an annotation from the left panel after a search from the search box. The speed of creating the dialog to enter the component’s name is also improved.
30		-* Create - Flow Testing: Properties will not disappear from the list when canceling changes on a default property value. (#913)
31		-* Create - Flow Testing: Users with view rights can edit test case names, descriptions, and property values. (#973)
32		-* Deploy - Architecture: The runtimes will display the number of connected flows, not "Zero."
33		-* Deploy - Architecture (Runtime Settings): Moved the delete button to the right side of the page and fixed the bug in the help text.
34		-* Deploy - Releases: We fixed an issue that prevented you from seeing a comparison message when hovering over an exit gate flow of the API pattern if you compare two release versions in Deploy. (#839)
35		-* Deploy - Releases: We improved the loading buttons of releases on the right pane by Order (Ascending).
	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)
36	36
	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.