Changes for page 264 - Strict Separation

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-264 - Strict Separation
	1	+190 - Fast Forward

Content

...	...	@@ -1,31 +1,32 @@
1		-This release includes our new user management for models running on our latest versions of the API Gateway **and** Event Streaming offerings. Furthermore, it includes a new **[[environment template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** that improves machine behavior in a single-lane cloud configuration when runtimes are added or removed. On top of that, we introduce several improvements that enhance and clarify the user experience throughout the platform.
	1	+The release finishes up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs and some minor enhancements. Furthermore, we introduce several improvements in the interaction with the portal.
2	2
3		-Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.264 - Strict Seperation.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.190 - Fast Forward.WebHome||target="blank"]].
4	4
5		-==== Minor changes ====
	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"]].
	7	+* Manage - Explore: The Queue browser is a new feature that enables you to explore the queues on your jms-server and view (and delete) the message on them. It is only available if you migrated your JMS server to the 3rd generation runtime.
6	6
7		-* Deploy - User management: Several new functionalities are released, improving the user experience when dealing with user management. To experience these improvements, you need to be running on the latest version of our API Gateway and/or Event Streaming offering.
8		-** When you click “Apply to environment” in Deploy > User management, a pop-up now displays all pending changes. You can select only the changes you want to apply (cherry-pick), and any related dependencies will be automatically selected. This helps prevent mistakes and ensures consistency when applying updates. With this enhancement, you can more easily and safely customize configurations per environment.
9		-** For fully migrated models (using DSH for Eventstreaming), the ‘transfer to design’ and ‘apply to environment’ buttons are combined. All changes will be shown when you press ‘apply to environment’ and will be applied when you press ‘apply’.
10		-** For fully migrated models (using API MAM for API gateway), the ‘transfer to design’ and ‘apply to environment’ buttons are combined. All changes will be shown when you press ‘apply to environment’ and will be applied when you press ‘apply’.
11		-* Deploy - Property: When saving a property, we now perform an optimization check. These improvements help reduce redundancy and keep property configurations cleaner and easier to maintain.
12		-** If other properties share the same name and value, we will recommend grouping them to improve manageability.
13		-** If any runtimes in the list of linked runtimes do not use the property, we suggest removing those runtimes from the list.
14		-** If none of the linked runtimes use the property, we recommend removing it.
15		-* Deploy - Releases: It is no longer possible to try to deploy a release that contains runtimes that are not linked to any flows in the architecture. (#1066)
	9	+=====Major changes=====
16	16
17		-==== Bug fixes ====
	11	+* Manage - Redelivery: You are able to explore the message redelivery functionality for the 3rd generation architecture and see more details about it. Beside that, you are also able to redeliver the message(s) in this page.
18	18
19		-* Design - Import XSD: Added the ability to import XSD files with an element of type 'all'. (#1146)
20		-* Design - Swagger Configuration: Errors related to the generation of the Swagger UI in eMagiz have been resolved. Users will no longer encounter errors when generating JSON (new cases). (#1424) (#1337)
21		-** Additionally, users can now define multiple tags per operation. Multiple tags should be separated using “-”. (#838)
22		-** An issue affecting the generation of examples for custom-defined schemas in the request and response body has also been fixed.
23		-** Schema validation has been extended to help prevent configuration mistakes. Existing errors related to referencing or schema definitions in the request/response body may still be present. However, when opening the edit page and clicking Save, the extended validation will be triggered. If the configuration results in an error, the validation will indicate this so it can be corrected before saving. (#924)
24		-* Create - Flow Testing: Users will get a pop-up error message related to their broken test case and will be asked to fix it. For automated test cases, a warning about broken test cases is shown to users who want to create a new version in the flow designer.
25		-* Deploy - Release Execution: The description of a manual step in the deployment plan is only shown once while deploying. (#933)
26		-* Manage - Alerting - Triggers: Fixed synchronization issue for log triggers, preventing unexpected behavior when all log triggers must be re-sent (#961)
	13	+=====Minor changes=====
27	27
28		-==== Remarks ====
	15	+* Design - System message: 'Request' and 'Response' entities are generated and set as root entities automatically for new SOAP web service integrations in 3rd generation runtimes.
	16	+* Create - Flow designer: sensitive information stored in property values is masked. (#790)
	17	+* Create - Flow Designer: when migrated from Gen2 to Gen3, the flow's JSON will be generated so user can use it to compare with the previous versions.
	18	+* Create - Flow Designer: when importing store item from another partner, a error popup will be shown instead of default error message.
	19	+* Deploy - Releases: The activate release functionality gained a performance improvement for gen 3 models.
	20	+* Deploy - Architecture: Before apply to environment, we require a confirmation from you if those are some breaking changes that may cause issues in AWS. (#828)
	21	+* Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571)
	22	+* Deploy - Architecture: "HTTP settings" page changed to "Runtime settings", where you can enable/disable both HTTP and control bus per runtime.
	23	+* Deploy - Releases - When activating a release you will be reminded of empty runtimes. Empty runtimes are runtimes without flows in the release. These runtimes should be removed from your architecture.
29	29
30		-* General - Portal: We have removed part of our platform's functionality as it was not used anymore.
31		-* General - Help Text: We have updated our help text widget to align it with the new UI options in Mendix. (#1757)
	25	+====Bug fixes====
	26	+* Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508)
	27	+* Create - Flow Designer: When copy and paste, support objects such as "property placeholder", "support.bus-connection-caching" and "support.bus-connection-plain" are not duplicated (#793)
	28	+* Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in setup step.
	29	+* Deploy - Containers: We fix an issue that the container overview does not show the entry flows which should run on that container. (#863)
	30	+* Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814)
	31	+* Deploy - Architecture: The deploy runtimes option is only visible for admin. New menu item "Deploy agent" is added and visible for all users to show the command which can be uses to deploy agent on premises machine.
	32	+