Changes for page 245 - Limited Exposure

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-242 - Stability Score
	1	+244 - Forgotten Frontiers

Content

...	...	@@ -1,20 +1,19 @@
1		-In the last sprint, we released several items to improve the platform's stability across the various ILM phases. Our most significant change is a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] that allows models running on our current-generation architecture to better control their resource management within the cloud models. In addition, we released various improvements in the platform regarding clarity and stability.
	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.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.242 - Stability Score.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.244 - Forgotten Frontiers.WebHome||target="blank"]].
4	4
5		-====New Features====
	5	+====Major Changes====
6	6
7		-* Cloud - Templates: We have implemented a feature for cloud models to improve resource management control within your production environment. This is released as part of a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]].
	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)
	8	+* Create - Add Integrations: We have updated the functionality behind the "Add Integration" overview to support the following deletion cases better. (#1378)
	9	+** Users cannot un-transfer an integration in the Create phase if another user is editing a part of the flow attached to the integration.
	10	+** Users cannot un-transfer the last integration of a System in the Create phase if another user is editing the connector infra.
	11	+** 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.
8	8
9		-====Minor Changes====
10		-
11		-* Design - Message Definition: When editing a system, CDM, or Gateway message, you can now add and remove attributes to an entity in the message model using an improved version of the ‘Add attribute(s)’ popup in the message designer.
12		-* Store - Overview: The statistics tab in Store item details shows the number of imports and the models where a store item has been imported to, which is only visible to store admins. (#799)
13		-* eMagiz Connector - Softcrow: Softcrow restoration has been added to the eMagiz Connector.
14		-
15	15	====Bug fixes====
16	16
17		-* Create - Transformation: In the Transformation tab of the Create phase. Newly created attribute operations of type aggregator can freely switch positions with a destination filter using the move left or right buttons. (#1307)
18		-* Create - Flow Designer: Updated help texts and documentation references that pointed to Joda time with the relevant Java DateTimeFormatter options to reflect the current state of libraries supported in the runtime images.
19		-* Manage - Triggers: You can no longer add HTML in the trigger fields for our current generation of alerts. This is to prevent potential malicious code from ending up in emails sent to customers.
20		-
	15	+* 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)
	16	+* 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)
	17	+* 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.
	18	+** 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.
	19	+** 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.