Changes for page 245 - Limited Exposure

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-244 - Forgotten Frontiers
	1	+191 - Fifty Fifty

Content

...	...	@@ -1,22 +1,53 @@
1		-In the last sprint, we released several stability options, mainly regarding the deletion behavior within the platform. We also released an update to the flow configuration of Mendix systems to avoid conflicts with another module that you could be using in Mendix, the Excel Importer.
	1	+The release introduces a lot of small 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>>Main.Release Information.Release Blogs.244 - Forgotten Frontiers.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		-====New Features====
	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 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 to easily wiretap messages from channels in a flow to a queue, which can the 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 which also needs to be reset. Additionally only flows in a container that has the Gen3 Debugging components inside of the associated container infra flow can be debugged. For more information on how to setup debugging on Gen3, please consult the documentation.
	10	+* Manage - Alerting: There are 4 new types of triggers 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 a one or several words which you expect in your logging events.
	13	+** Queue Consumers is to configure for queues where more than 1 consumer is expected.
	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 that are expected to pass through the flow.
6	6
7		-* General - Support: System admins can manually log out other users with active sessions. This is added to cover certain edge cases regarding locked flows. (#1197)
	17	+=====Minor changes=====
8	8
9		-====Major Changes====
	19	+* Data-Limit: Set data limit per environment.
	20	+* Login page: Login page /login.html now redirects to the real 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 now clearly states which types of 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 popups of failed machine deployments.
	27	+* Deploy - Releases: We added column sorting to the popup 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 detail page of the docker container.
	30	+* Deploy - Architecture: On the detail page about an instance, the state of the instance is now visible. (#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 HTTP statistics dashboard. (#856)
	37	+* Manage - Alerting: By default, no filter is applied to Status when navigating to Notifications, or resetting the filters on Notifications. (#486)
10	10
11		-* Create - Add Integrations: We have updated the functionality behind the "Add Integration" overview to support the following deletion cases better. (#1378)
12		-** Users cannot un-transfer an integration in the Create phase if another user is editing a part of the flow attached to the integration.
13		-** Users cannot un-transfer the last integration of a System in the Create phase if another user is editing the connector infra.
14		-** Users can un-transfer the Exit/Entry connector in the Create phase either by selecting one of the integrations or both of the integrations of the Exit/Entry connector. This process is also successful when the Exit/Entry connector is in the Deploy phase.
15	15
16	16	====Bug fixes====
17	17
18		-* Design - API Data Model: Users can remove entities that were once part of a gateway message of an API operation that has been removed/un-transferred from the Create Phase. (#1577)
19		-* Create - Flow Designer: Create phase - The help text of the “Max fetch size” property of the “IMAP idle channel adapter” better reflects its behavior and usage. (#1410)
20		-* eMagiz Connector - Flow Configuration: The issue where the new eMagizConnector Mendix module would cause conflicts with the Mendix Excel Importer module has now been resolved.
21		-** If you already have a synchronous messaging flow for a Mendix connector system, this flow must be reset before creating a new release. Make sure this new version is included in your next release. Failing to do so can break error handling for these synchronous entry flows.
22		-** After setting the new release as active, the Mendix application has to be stopped and started to use the new image. This doesn’t have to be done right away, you can await the following restart.
	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 you 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 apply 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 visible when container not deployed.
	48	+* Manage - Monitoring: Fix typo in Event Proccessors Metrics. (#835)
	49	+
	50	+====Remarks====
	51	+
	52	+* Mendix Runtime has been upgraded to Mendix 9.21.0.
	53	+