Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 328.1
edited by Carlijn Kokkeler
on 2024/10/07 15:08
Change comment: There is no comment for this version
To version 321.2
edited by Carlijn Kokkeler
on 2024/09/23 13:36
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -231 - Microscopic Madness
1 +230 - Petite Peaks
Content
... ... @@ -1,18 +1,12 @@
1 -During our recent sprint cycle, we have improved the search options for flow testing logs and monitoring logs. Next to this, we fixed the unused properties overview and improved the deletion functionality of router containers.
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.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.231 - Microscopic Madness||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.229 - Xpath Alignment||target="blank"]].
4 4  
5 -
6 6  ====Minor changes====
7 -* Create - Flow Testing: Search options for flow testing logs have been improved.
8 -** Improved search options for flow test logs. You can now search for 'logger' and 'message', search for 'timestamp from' and 'to' have been removed.
9 -** Unified the UI with Manage phase logging of G3) for a more streamlined experience
10 -* Manage - Monitoring: Search options for monitoring logs have been improved.
11 -** Unified the UI with flow testing log interface, showing the message and stack trace (if available) in 2 different tabs
12 -** Added the 'logger' column that shows the last part of the logger name.
13 -** Added a search field for ‘logger’
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)
7 +* Create - Flow Designer: SFTP (caching) session factories now have an additional option to specify the authentication methods that should be used, and in which order. Note that the latest [[runtime image>>Main.Release Information.Runtime Images.V313||target="blank"]] is needed to make the functionality work in eMagiz.
14 14  
15 -
16 16  ====Bug fixes====
17 -* Deploy - Architecture: Router containers that were deleted from the Deploy Architecture, are now cleaned up completely from the environment.
18 -* Deploy - Releases: We fixed an issue where used properties defined in Deploy Architecture were shown incorrectly in the missing properties overview and the unused properties overview. (#1442)
10 +* 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)
11 +* Create - Transformation: Fixed a bug that caused the value input field to disappear if you switch from “custom xpath“ to “if it exists“. (#1010)
12 +* Create - Flow designer: We fixed an issue related to the legacy property “web service-URL “ of an exit connector flow to a Mendix (connector) system. In your Mendix application, you can download and start them as you are used to.