Changes for page 245 - Limited Exposure
Last modified by Erik Bakker on 2025/05/21 09:01
From version 98.1
edited by Erik Bakker
on 2023/07/17 21:28
on 2023/07/17 21:28
Change comment:
There is no comment for this version
To version 251.1
edited by Erik Bakker
on 2025/05/07 15:59
on 2025/05/07 15:59
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 -2 01-BeInformed1 +244 - Forgotten Frontiers - Content
-
... ... @@ -1,30 +1,19 @@ 1 -In the last sprint cycle, wefocused onplanning theupcomingquarter,finishingup,andworkingontheHackathontoalsmalleritems.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.2 01-BeInformed.WebHome||target=3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.244 - Forgotten Frontiers.WebHome||target="blank"]]. 4 4 5 -==== =Minorchanges=====5 +====Major Changes==== 6 6 7 -* Portal - Menu: The back button is changed to have text on it to make the navigation much clearer. (#949) 8 -* Design-Architecture: Topic Storage detail page contains help text. (#994) 9 -* Design - API Endpoint Specification: Improved UI and added independent scroll functionality. (#832) 10 -* Design - API Gateway: Small styling improvement on the "Edit integration page." (#954) 11 -* Create - Flow Designer: When deleting one or multiple components, you cannot change the selection before confirming or canceling the delete action. (#969) 12 -* Create - Migrate to 3rd Generation: If one or more flows break during migration, a popup will inform the flows containing errors after the migration. (#983) 13 -* Deploy-User management: The user that makes a change is recorded in history instead of the user that applies to the environment. (#979) 14 -* Deploy-Architecture: Upon pressing the “Apply to the environment” button, a confirmation page is shown. All changes made in the portal that will affect your running environment are listed here. These changes can be applied to the environment or reverted. (#828) 15 -** Changes made in Deploy Architecture with an effect on your running environment will only be listed when they are made after this release. 16 -** Changes with a direct effect will not be listed (for example, restarting a machine). 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. 17 17 18 18 ====Bug fixes==== 19 19 20 -* Design - Solutions: We fixed an issue that displayed a message mapping error despite having a passthrough API gateway. (#935) 21 -* Design - Settings: The full length of the contract number can now be registered. (#958) 22 -* Create - Migrate to 3rd Generation: Components used in Gen 2 flows that can be used in Gen 3 will not block migration. (#982) 23 -* Deploy - Deployment plan: We fixed an issue that the list of installing flows did not show in the left pane when you deploy a release version to install/start/stop some flows into your runtimes. (#990) 24 -* Deploy - User Management: As a user with view-only rights in Deploy/User management, you can now double-click on a user to open its details. (#972) 25 -* Manage - Manage Dashboards: The screen loading speed is significantly improved for all models. This is most noticeable for larger models. (#964) 26 - 27 -=====Infra and image changes===== 28 - 29 -* Changed the endpoint for sending error messages to the eMagiz Control Tower. 30 -* Updated the Spring version of the gateway supporting deploy and manage phase operations. 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: 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.