Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 34.1
edited by Erik Bakker
on 2022/12/06 16:05
Change comment: There is no comment for this version
To version 311.1
edited by Erik Bakker
on 2024/09/09 09:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -189 - Private Eye
1 +229 - Xpath Alignment
Content
... ... @@ -1,24 +1,10 @@
1 -The release brings a private store to our community and makes the latest runtime image available for our customers running on the 3rd generation architecture. Furthermore, we introduce several improvements to our 3rd generation runtime and its interaction with the portal.
1 +During our recent sprint cycle, we have done several improvements to keep our model running smoothly. Moreover, we have made some small changes to various XPath related parts of the portal. Please find out all our changes & bug fixes below.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.189 - Private Eye.WebHome||target="blank"]].
4 -=====New features=====
5 -* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Release blog>>Main.Release Information.Runtime Images.V110.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.229 - XPath Alignment||target="blank"]].
6 6  
7 -=====Minor changes=====
5 +====Minor changes====
6 +* Deploy - Deployment plan: We updated the deployment step that temporary disables the triggers in your model. As a result you now have the ability to 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 that 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 prior to deploying. This can be done via the Manage phase.
8 8  
9 -* General: Code mapping is now available for models migrating to the 3rd generation runtime.
10 -* General: Added functionality that allows you to search by pressing "Enter" on various pages across the platform. (#785)
11 -* Store: Renamed several display names across the Store functionality to better clarify what the functionality does for you.
12 -* 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)
13 -** After five times, the runtime will remain in the stopped state.
14 -
15 15  ====Bug fixes====
16 -* Create - Flow designer: Resetting the JMS server sometimes resulted in invalid connection settings for connecting to the failover JMS server. (#717)
17 -* Create - Flow designer: Newly generated flows were configured with incorrect XSD or XLST resource locations under specific circumstances. (#718)
18 -* 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)
19 -* Deploy - Architecture: Prechecks for cloud template upgrades failed unexpectedly under particular circumstances. (#703)
20 -* Manage - Runtime statistics: Data measurements of eMagiz-Mendix Connector runtimes are not missing anymore.
21 -* 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.
22 -
23 -====Remarks====
24 -* Mendix Runtime has been upgraded to Mendix 9.19.0.
9 +* Create - Flow Designer: Improved the helptext of the edit/new header menu in the XPath header enricher component (#727)
10 +* Create - Transformation: Fixed bug that causes the value input field to disappear if you switch from custom xpath to if exists. (#1010)