Changes for page 215 - Tiny Tales

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-212 - Failover Fiesta
	1	+215 - Tiny Tales

Content

...	...	@@ -1,27 +1,14 @@
1		-In the last sprint cycle, we focused on ....
	1	+In the last sprint cycle, we focused on improving the event streaming graph. Moreover, we have done some bug fixes. First of all, the validation for queue names with respect to spaces has been improved. Furthermore, it is now possible to remove an onramp that was previously linked to an all-entry. Lastly, it is now possible to log in to eMagiz by pressing enter when the username field is selected.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.215 - Tiny Tales||target="blank"]].
4	4
5		-=====New features=====
6		-
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.
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	10	=====Minor changes=====
11	11
12		-* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
13		-* Deploy - Deployment: The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
14		-* Deploy - Architecture: The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'. The risk level is either medium or high.
15		-* Manage - Alerting: You can now add external recipients to your environment directly, like internal users. (#917)
16		-* Manage - Monitoring: It is now possible to select the MQTT broker in the queue metrics dashboards.
17		-* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
	7	+* Manage - Monitoring: The event streaming graph has been improved so that the offset difference of a topic is the sum of the offset differences of each partition in that topic. (#951)
	8	+* Deploy - Releases: Previously, the latest ten versions of a flow were not always selectable for a release. This has been improved so that from now on, the latest ten committed versions of each flow are always available. (#1137)
18	18
19	19	====Bug fixes====
20	20
21		-* 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.
22		-* Deploy - Cloud template: An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
23		-* Deploy - Deployment: Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
24		-* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by a container.
25		-* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. (#1108)
26		-
27		-
	12	+* Login: In the login screen, users can now "press enter" to log in when the username field is selected.
	13	+* Create - Flow Designer: The validation regarding undesired spaces for components that use a queue name has been improved. (#1012)
	14	+* Create - Flow Designer: An issue has been fixed where removing an onramp linked to a combined entry was impossible. (#1021)