Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 317.1
edited by Erik Bakker
on 2024/09/09 15:19
Change comment: There is no comment for this version
To version 26.1
edited by Erik Bakker
on 2022/11/21 13:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -229 - XPath Alignment
1 +188 - Close Encounters
Content
... ... @@ -1,10 +1,21 @@
1 -During our recent sprint cycle, we made several improvements to keep our model running smoothly. We also made some small changes to various XPath-related parts of the portal and updated our deployment plan. Please find all our changes and bug fixes below.
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.229 - Xpath Alignment||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 -====Minor changes====
6 -* Deploy - Deployment plan: We updated the deployment step that temporarily disables the triggers in your model. As a result, you can now define after which waiting period (determined in minutes) you want eMagiz to take action. When it reaches this point, eMagiz will act according to the selected option. You can opt to "automatically re-enable triggers," "receive a notification mail," or "both." On top of that, we reintroduced the automatic "enable trigger" step, which can be added as the last step of your deployment plan to automatically re-enable triggers. Be aware that you **still** need to enable triggers manually if you have manually disabled them before deploying. This can be done via the Manage phase. (#1367)
5 +=====Minor changes=====
7 7  
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.
9 +* Store: Renamed several display names across the Store functionality to better clarify what the functionality does for you.
10 +* Deploy - Deployment plan: 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.
11 +** After five times, the runtime will remain in the stopped state.
12 +* Deploy - Releases: The activate release functionality performance for models that use the 3rd generation runtime is improved.
13 +
8 8  ====Bug fixes====
9 -* Create - Flow Designer: Improved the help text of the edit/new header menu in the XPath header enricher component, to better inform how a list of results can be handled. (#727)
10 -* Create - Transformation: Fixed a bug that caused the value input field to disappear if you switch from “custom xpath“ to “if it exists“. (#1010)
15 +* Flow designer: Newly generated flows were configured with incorrect XSD or XLST resource locations under specific circumstances. (#718)
16 +* Deploy - Architecture: Prechecks for cloud template upgrades failed unexpectedly under particular circumstances. (#703)
17 +* Manage - Runtime statistics: Data measurements of eMagiz-Mendix Connector runtimes are not missing anymore.
18 +* 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.
19 +
20 +====Remarks====
21 +* Mendix Runtime has been upgraded to Mendix 9.19.0.