Changes for page 245 - Limited Exposure

Last modified by Erik Bakker on 2025/05/21 09:01

From version 133.1
edited by Carlijn Kokkeler
on 2023/10/23 16:27
Change comment: There is no comment for this version
To version 249.1
edited by Erik Bakker
on 2025/05/07 15:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +244 - Forgotten Frontiers
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,44 +1,22 @@
1 -In the last sprint cycle, we focused on delivering state generation components. On top of that, we made several improvements regarding the alignment of components, and did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
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.207 - Aligned State .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 5  
6 -=====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)
7 7  
8 -* Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier. (#845)
9 -* Create - Framework: The framework used in the flow designer has been updated, improving performance.
10 -* Deploy - Architecture: The description users see when adapting the topic retention size has been changed to be less confusing.
11 -* Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. (#1009)
12 -* Deploy - Deployment plan: A change in the memory settings of a container triggers a redeployment of the container. (#993)
13 -* Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.
14 -* Deploy - Release properties: The description of a property can be changed by editing the property. (#1064)
15 -* Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines.
16 -* Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well.
17 -* Deploy - Release: Performance improvements have been implemented for loading releases in Deploy.
18 -* Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment. (#1024)
19 -* Manage - Alerting: Inactivated users should be removed from all alert settings (including “disabled“ settings) to avoid undesirable notifications.
20 -* Manage - Monitoring: Graphs showing problematic runtimes, queues and requests have been updated to be sorted by “Process CPU usage”, “Messages in queue” and “Unsuccessful requests” by default respectively for 3rd generation runtimes. (#1069)
21 -* Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default. (#1070)
22 -* Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063)
23 -* Administration - My account: When an account password change request is made, even when this fails, a mail is sent to the account owner to inform on the action.
24 -* Administration - My account: When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password is found in a database.
9 +====Major Changes====
25 25  
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.
26 26  
27 -
28 28  ====Bug fixes====
29 29  
30 -* Design - Store: We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
31 -* Design - Store: We fixed an issue that the orders of message definition elements were changed after being imported.
32 -* Design - Store: We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should be the same with the exported message definitions.
33 -* Design - Store: We fixed an issue that static copies were missing when importing store items. (#888)
34 -* Design - Store: Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message. (#1027)
35 -* Create - Errors - We fixed an issue that, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow.
36 -* Create - Styling: The styling of the left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
37 -* Deploy - Cloud Template: An issue with disk performance in the last cloud template update has been resolved in this release. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates||target="blank"]] for more information.
38 -* Manage - Monitoring: It is now possible to search on messages using partial search words in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
39 -
40 -
41 -
42 -=====Infra and image changes=====
43 -
44 -* Infra: New logging feature enabling us to make better choices in deprecating old encryption standards.
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.