Changes for page 245 - Limited Exposure
Last modified by Erik Bakker on 2025/05/21 09:01
From version 10.1
edited by Erik Bakker
on 2022/10/14 13:58
on 2022/10/14 13:58
Change comment:
There is no comment for this version
To version 249.1
edited by Erik Bakker
on 2025/05/07 15:46
on 2025/05/07 15:46
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 185-GetReady1 +244 - Forgotten Frontiers - Content
-
... ... @@ -1,25 +1,22 @@ 1 - Releasethatupdatesthemanage statisticssectionsforournew monitoringstack.Ontopofthat,wehavereleased aloud templateandreleasedseveralotherfunctionalities.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. 185-Get ready.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===== 6 -* Deploy - User Management: Before and after applying to environment, keep track of user management changes. Export history as an excel file. 5 +====New Features==== 7 7 8 - =====Minor changes=====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) 9 9 10 -* Design System. Changed the look and feel across the portal altogether. Changes can be seen in: 11 - ** Datagids, where there is now on hover action for example. 12 - ** Pop ups 13 - ** Context menus, also have on hover action 14 - ** Styling of scrollbars 15 - ** Warning, info and error context labels. 16 -* Message Redelivery - admin logs improved to better analyze issues when they occur 17 -* Message Redelivery - improved feedback to the user when something goes wrong within the Message redelivery functionality 18 -* Create - Flow Designer: small bugs (copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed 9 +====Major Changes==== 19 19 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 + 20 20 ====Bug fixes==== 21 -* Deploy - Deployment plan. Performance of page to deploy a release increased significantly 22 -* Store - Import resources was incorrectly done in specific cases, which is now fixed 23 -* Store - Target namespace will be imported when importing an XML Message Definition 24 -* Store - When exporting components, if property values contains model name, they will be updated automatically with new model name when importing into a new model. 25 -* Store - Importing items from the store sometimes resulted in invalid JMS connection factories. 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.