Changes for page 245 - Limited Exposure
Last modified by Erik Bakker on 2025/05/21 09:01
From version 15.1
edited by Erik Bakker
on 2022/10/28 16:23
on 2022/10/28 16:23
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 - 186-DaemonSwitch1 +244 - Forgotten Frontiers - Content
-
... ... @@ -1,35 +1,22 @@ 1 - The release bringsthenew monitoringstacktofruitionandvariousupdatesto handlingmultiplenamespaces.Ontopof that, wehaveeleasedaslewofsmaller feedbackitemsandbugfixes.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. 186-DaemonSwitch.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 -* Generic - New monitoring stack: As of this release, you can run on the new monitoring stack. For more information on becoming an early adopter, don't hesitate to get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 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 -* Create - Flow designer: You can now see who/when a resource was changed on a resource view page. 11 -* Design - Solution: You will see a warning in the Solution view on operation if it is not connected to a backend API operation or in "Transformation" mode. 12 -* Create - Flow designer: You can see all related configurations that use a specific resource when viewing the details of the resource. 13 -* Design - API Gateway: Changes in your Gateway messages are reflected directly in your OpenAPI JSON document. 14 -* Model Dashboard - Going to manage from the model dashboard now loads the error message dashboard without having to click on the error messages dashboard explicitly 15 -* Create - Flow testing: The name of the starting point in the flow testing result tab is matched with the component type. 16 -* Deploy - Releases: The automated flow test pop-up can now be closed by pressing "Enter." 17 -* Deploy - Properties: Password-type properties are masked in the unused properties pop-up. 18 -* Deploy - User management: "Generate Keystore" button is renamed "Download Keystore," and the file name contains environment information. 19 -* Create - Flow Testing: Added a button to display the content of a selected trace message in a pop-out. 20 -* Deploy - Properties: You can use enter key to search on the property overview page. 21 -* Create - Flow designer: Increased size of the SpEL expression input field of standard transformer component. 22 -* Create - Flow Designer: Show generated resources toggle is not disabled by default; your preference for showing or hiding generated resources will be saved. 23 -* Administration - Licenses: Added event streaming storage usage of your models. 24 -* Store: Compatibility check is added, which prevents importing G3 store items into G2 flow/integration 25 -* General: Improved help texts explaining options and screens related to the new runtime architecture or the migration towards it. 9 +====Major Changes==== 26 26 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 + 27 27 ====Bug fixes==== 28 -* Deploy - Properties: Improved the layout of the cron trigger generator page 29 -* Deploy - Properties: Generating a password or CRON trigger will not reset the runtime field 30 -* Create - Flow designer: While editing an exit flow, the system message is not editable. 31 -* Design - Integration designer: For event streaming integrations, switching between Design Mapping and Create Transformation sometimes did not work. 32 -* Create - Transformation: For event streaming integrations, the 'Start editing' button sometimes did not work. 33 -* Create - Flow designer: Comparing two flow versions works again. 34 -* Create- Flow Designer: When creating my initial version of a flow, the notification pop-up shows the correct information. 35 -* Create - Flow Designer: All relevant support objects will be highlighted when selecting a support object. 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.