Skip to Content

Changes for page 237.1 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
From version 112.1
edited by Erik Bakker
on 2023/09/27 18:53
Change comment: There is no comment for this version
To version 29.1
edited by Erik Bakker
on 2022/11/24 11:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Wrap Up
1 +188 - Close Encounters
Content
... ... @@ -1,15 +1,22 @@
1 -This release signifies our efforts to wrap up our quarter. It consists of several must-needed functionalities for specific use cases regarding the next-generation architecture.
1 +The release brings several improvements to our 3rd generation runtime and its interaction with the portal. On top of that, we have several feedback items and bug fixes.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.206 - Wrap Up.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.188 - Close Encounters.WebHome||target="blank"]].
4 4  
5 5  =====Minor changes=====
6 6  
7 -* Deploy - Releases: The related unused images in the on-premises machines will also be removed when the release is removed.
8 -* Create - Transfer settings from Design: Added a migration step. If the custom error handling is set to false, we set the error channel to “errorChannel” for all inbounds in a flow.
9 -* Create - Transfer settings from Design: Added a check in the migration that validates whether every targetNamespace is filled in when a SOAP web service is migrated and split as part of the migration to the next-generation architecture.
10 -* Create - Transfer settings from Design: Added a check in the migration that validates whether a specific old component, the Jetty server support object, remains in a flow after the migration. If so, the user is notified that they need to take action on this.
7 +* General: Code mapping is now available for models migrating to the 3rd generation runtime.
8 +* General: Added functionality that allows you to search by pressing "Enter" on various pages across the platform. (#785)
9 +* Store: Renamed several display names across the Store functionality to better clarify what the functionality does for you.
10 +* Deploy - Deployment plan: For 3rd generation runtimes we have changed the restart behavior in case of startup problems. This means that when a runtime is being deployed, which is constantly crashing and thereby causing problems, the restart of the runtime is limited to just five times. (#720)
11 +** After five times, the runtime will remain in the stopped state.
11 11  
12 -=====Infra and image changes=====
13 +====Bug fixes====
14 +* Create - Flow designer: Resetting the JMS server sometimes resulted in invalid connection settings for connecting to the failover JMS server. (#717)
15 +* Create - Flow designer: Newly generated flows were configured with incorrect XSD or XLST resource locations under specific circumstances. (#718)
16 +* Deploy - Deployment plan: Before when you tried to deploy a Release via the Deploy functionality the widget could crash randomly. With this fix we ensured the widget will always load correctly. (#362)
17 +* Deploy - Architecture: Prechecks for cloud template upgrades failed unexpectedly under particular circumstances. (#703)
18 +* Manage - Runtime statistics: Data measurements of eMagiz-Mendix Connector runtimes are not missing anymore.
19 +* Manage - Error Dashboard: Solved a problem that caused a user to see a general error when opening the Manage Dashboard while running a 3rd generation runtime architecture.
13 13  
14 -* New logging feature enabling us to make better choices in deprecating old encryption standards.
15 -* Carwash change to enable our direct connect offering for customers on the next-generation architecture.
21 +====Remarks====
22 +* Mendix Runtime has been upgraded to Mendix 9.19.0.