Changes for page 220 - Patch Parade

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-217 - Template Tango
	1	+189 - Private Eye

Author

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

Content

...	...	@@ -1,17 +1,34 @@
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.
	1	+The release brings a private store to our community and makes the latest runtime image available for our customers running on the 3rd generation architecture. Furthermore, we introduce several improvements to our 3rd generation runtime and its interaction with the portal.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.217 - Template Tango||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.189 - Private Eye.WebHome||target="blank"]].
4	4
5	5	=====New features=====
	6	+* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V110.WebHome||target="blank"]].
6	6
7		-* Create - Flow Designer & Deploy: Copy to clipboard buttons have been added to various pages.
8		-* Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce the ability to clean H2 databases from the portal. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
9		-* Manage - Alerting: The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a custom trigger for each model and environment, allowing users to edit this trigger.
	8	+=====Major changes=====
10	10
	10	+* Store - Private store. This release introduces the private store with the following features:
	11	+** Store items will be private by default and are only accessible for users that belong to the same company as the user that exported the store content. Note that the store item needs to be approved before it is visible to users.
	12	+** A new user role, "Store Exporter," will be introduced and can be assigned to the users who can create and update store items.
	13	+** Approval of a store item will be executed by eMagiz personnel, who can also set a store item to be public.
	14	+** Public store items will be importable by all users.
	15	+
11	11	=====Minor changes=====
12	12
13		-* Deploy - Architecture: For the current generation architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. Please note that only H2 databases that are registered under the standard eMagiz data folder will be removed. Moreover, it is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime. Lastly, for on-premise runtimes, only a reset of the runtime is needed.
	18	+* Create - Event Streaming: Event streaming is now available for models migrating to the 3rd generation runtime.
	19	+* Create - Transformation: source filter on attribute with empty field is more readable in read-only mode. (#732)
	20	+* Create - Migration: Improved compatibility checks related to the 3rd generation runtime migration.
	21	+* Deploy - Check properties: Informative error messages when saving or creating a property. (#576)
	22	+* Deploy - Deployment plan: We improved the deployment plan to avoid it causing problems when executing a deployment plan containing loads of steps.
	23	+* Deploy - Architecture: Added reset feature for 3rd generation runtimes.
14	14
15	15	====Bug fixes====
	26	+* Create - Settings: We fixed an issue where changing the connection type did not update all relevant flows.
	27	+* Create - Flow designer: Newly generated flows were configured with incorrect resource locations under specific circumstances.
	28	+* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish.
	29	+* Deploy - Deployment plan: While generating a default plan, flow type steps will not be created for OSGi runtimes that run on a Docker machine. (#798)
	30	+* Deploy - Architecture: Cloud slots now wake up without potential need to apply to environment.
	31	+* Deploy - Architecture: 3rd generation runtimes are included in runtime checks while upgrading your cloud environment.
16	16
17		-* Deploy - Runtime Overview: The runtime overview has been improved with respect to checks on the runtime version. (#1243)
	33	+====Remarks====
	34	+* Mendix Runtime has been upgraded to Mendix 9.19.0.