Changes for page 225 - Pop-up Party

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-222 - Flee Frustration
	1	+188 - Close Encounters

Author

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

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	+The release brings several improvements to our 3rd generation runtime and the interaction with it. On top of that, we have several feedback items and bug fixes.
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.188 - Close Encounters.WebHome||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	+=====Minor changes=====
7	7
	7	+* General: Code mapping is now available for models migrating to the 3rd generation runtime.
	8	+* General: Added functionality that allows you to search by pressing "Enter" on various pages across the platform.
	9	+* Store: Renamed several display names across the Store functionality to get better clarity on what it can be used for.
	10	+* Deploy - Deployment plan: When a runtime is being deployed which is constantly crashing and thereby causing problems the restart of the runtime is limited to just 5 times.
	11	+** After 5 times the runtime will remain in the stopped state.
	12	+* Deploy - Releases: The activate release functionality gained a performance improvement for models that use the 3rd generation runtime.
	13	+
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	+* Flow designer: Newly generated flows were configured with incorrect XSD or XLST resource locations under specific circumstances. (#718)
	16	+* Deploy - Architecture: Prechecks for cloud template upgrades failed unexpectedly under particular circumstances. (#703)
	17	+* Manage - Runtime statistics: Data measurements of eMagiz-Mendix Connector runtimes are not missing anymore.
	18	+* Manage - Error Dashboard: Solved a problem that caused a user to see a general error when opening the Manage Dashboard while running a 3rd generation runtime architecture.
15	15
16		-
17		-
	20	+====Remarks====
	21	+* Mendix Runtime has been upgraded to Mendix 9.19.0.