Changes for page 225 - Pop-up Party

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-222 - Flee Frustration
	1	+214 - System Symphony

Content

...	...	@@ -1,17 +1,21 @@
1		-In the last sprint cycle, we have worked to allow cron trigggers for hours, days and months prepended by a 0. Moreover, changes in Design that will create or delete runtimes, or impact your model architecture, will trigger a warning before being put into effect in Design Architecture. We have also done several bug fixes, for example, users are not logged out from the portal anymore while deploying. Furthermore, users are now blocked from deploying at the same time on the same environment. Find out about the rest below!
	1	+In the last sprint cycle, we focused on improving failover aspects. Moreover, we improved the history of monitoring graphs, it is now possible to view data from up to the last thirty days. Lastly, some more feedback items have been solved, and several more bug fixes have been done.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.222 - Flee Frustration||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.214 - System Symphony||target="blank"]].
4	4
5		-====New features====
6		-* Design - Architecture: If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture.
	5	+=====New features=====
7	7
	7	+* Design - CDM & System Message - It is now possible to add multiple attributes to an entity at once. (#1141)
	8	+* Deploy - Architecture: We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible.
	9	+
	10	+=====Minor changes=====
	11	+
	12	+* Deploy - Releases: Deletion of releases with deployed container versions will not be blocked anymore. (#1216)
	13	+* Manage - Monitoring: New functionality to ensure that the monitoring graphs in Manage can show data from the last thirty days.
	14	+
8	8	====Bug fixes====
9		-* Design - Architecture: The number on the JMS container correctly displays the amount of queues present in Design. (#1284)
10		-* Create - Flow Designer: Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. (#1053)
11		-* Deploy - Architecture: We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. (#1282)4
12		-* Deploy - Deployment plan: Users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed. (#1293)
13		-* Deploy - Properties: Cron triggers now allow for hours, days and months prepended by a 0, for example 05.
14		-* Deploy - Releases: Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. (#1293)
15	15
	17	+* Create - Flow Designer: The help text of the Group attribute has been improved.
	18	+* Create - Flow Testing: An issue has been solved where resource paths would change after running a flow test. (#802)
	19	+* Deploy - Architecture: A new state 'Leader (single node)' has been added in case there is only one node for failover setup. A refresh button has been added in Group tab of "Start/Stop Flows" screen. To utilize this, a new runtime image, [[V.2.1.1>>Main.Release Information.Runtime Images.V211||target="blank"]], is needed.
16	16
17	17