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	+191 - Fifty Fifty

Content

...	...	@@ -1,32 +1,53 @@
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 introduces a lot of minor fixes as a result of our "hackathon" efforts. Subsequently, we will release several 3rd generation runtime offerings.
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.191 - Fifty Fifty.WebHome||target= "blank"]].
4	4
5		-==== Minor changes ====
	5	+=====New features=====
	6	+* Deploy - Architecture: We added the possibility to register network shares in your container volume settings. This enables the use of network shares without having to mount them manually on the host machine and then again on the container level. This option is only available for 3rd generation runtimes that run on-premises.
	7	+* Deploy - Containers: In Deploy containers, a 'Debug' option is added for flows on the 3rd generation eMagiz runtime.
	8	+** This option will temporarily be available for users on the next generation runtime. It allows one to easily wiretap messages from channels in a flow to a queue, which can then be browsed using the queue browser. One flow can be wiretapped at the time per container.
	9	+** To use this option, the model must be fully migrated to Gen3, including the JMS. Additionally, only flows in a container with the Gen3 Debugging components inside the associated container infra flow can be debugged. Please consult the documentation for more information on how to set up debugging on Gen3.
	10	+* Manage - Alerting: Five new triggers are available for Model in G3.
	11	+** Error Message is to evaluate the headers of the original message which resulted in an error.
	12	+** Log Keyword is to evaluate logging messages. You can provide one or several words which you expect in your logging events.
	13	+** Queue Consumers is to check whether more than one consumer is expected on the queue level.
	14	+** Queue Messages is to configure for queues where more than 100 messages on a queue can occur
	15	+** Queue Throughput is to monitor issues with your system by setting thresholds for the number of messages expected to pass through the flow.
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)
16		-* Deploy - Architecture: Adding/moving/deleting containers from machines will now not replace the underlying instances. This was only the case for singlelanes. Doublelanes do not have this behaviour and are not affected.
	17	+=====Minor changes=====
17	17
18		-==== Bug fixes ====
	19	+* Data-Limit: Set data limit per environment.
	20	+* Login page: The login page /login.html now redirects to the actual login page /p/login. (#671)
	21	+* Create - Flow designer: Removed the unnecessary refresh button from the component creation pop-ups. (#858)
	22	+* Create - Flow designer: Properties in the property overview pages are sorted as Test/Acceptance/Production. (#804)
	23	+* Create - Flow designer: We improved validation and help text on Wss4J interceptors components. (#733)
	24	+* Create-Flow testing: Improved the help text when adding a header type for a test message. It clearly states which Java classes can be used, along with some examples. (#742)
	25	+* Deploy - Releases: Setting a release as active by pressing the deploy button creates an entry in the deploy history. (#823)
	26	+* Deploy - Releases: We improved the notification pop-ups of failed machine deployments.
	27	+* Deploy - Releases: We added column sorting to the pop-up showing the missing properties. (#860)
	28	+* Deploy - Architecture: New cloud slots have their auto-upgrade value set to true by default. (#841)
	29	+* Deploy - Architecture: A docker container's status is more visible when you open the detail page of the docker container.
	30	+* Deploy - Architecture: The instance's state is now visible on the detail page about an instance. (#699)
	31	+* Deploy - Architecture: We changed the wake-up time of cloud slots on Fridays to 6:00 UTC so that they no longer fall within our regular deployment windows. (#559)
	32	+* Deploy - Architecture: We added runtime memory checks to 'Apply to environment' to prevent invalid deployments. (#719)
	33	+* Deploy - Properties: We improved runtime selection when copying properties. (#796)
	34	+* Manage - Explore: Improved the displayed error message when a message could not be loaded in the message redelivery screen. (#696)
	35	+* Manage - Explore: "Save as test message" button opens a pop-up that allows you to edit your test message's name, description, content, and headers before saving it.
	36	+* Manage - HTTP statistics: Fixed a typo in the HTTP statistics dashboard. (#856)
	37	+* Manage - Alerting: By default, no filter is applied to the status when navigating to the "Notifications" overview or resetting the filters on the "Notifications" overview. (#486)
19	19
20		-* Design - Import XSD: Added the ability to import XSD files with an element of type 'all'. (#1146)
21		-* 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)
22		-** Additionally, users can now define multiple tags per operation. Multiple tags should be separated using “-”. (#838)
23		-** An issue affecting the generation of examples for custom-defined schemas in the request and response body has also been fixed.
24		-** 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)
25		-* 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.
26		-* Deploy - Release Execution: The description of a manual step in the deployment plan is only shown once while deploying. (#933)
27		-* Manage - Alerting - Triggers: Fixed synchronization issue for log triggers, preventing unexpected behavior when all log triggers must be re-sent (#961)
28	28
29		-==== Remarks ====
	40	+====Bug fixes====
30	30
31		-* General - Portal: We have removed part of our platform's functionality as it was not used anymore.
32		-* General - Help Text: We have updated our help text widget to align it with the new UI options in Mendix. (#1757)
	42	+* Design - Solution design: We hide systems without functional integration now. (#714)
	43	+* Create - API Gateway: Security header case insensitive
	44	+* Create - Flow designer: Enabling redelivery for your integration is applied after resetting your offramp and exit flow. Before this change, you needed to remove and add the integration to Create phase to use this setting.
	45	+* Deploy - Containers: Applied styling to the error pop-up with the list of reasons why a runtime can't be deleted to make it easier to read. (#546)
	46	+* Deploy - Architecture: Deploying your model to the cloud for the first time required you to press 'Apply to Environment' twice. This is no longer the case. (#508)
	47	+* Deploy-Volumes: Network volumes are visible when the container is not deployed.
	48	+* Manage - Monitoring: Fix typo in Event Processors Metrics. (#835)
	49	+
	50	+====Remarks====
	51	+
	52	+* Mendix Runtime has been upgraded to Mendix 9.21.0.
	53	+