Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 313.1
edited by Erik Bakker
on 2024/09/09 10:17
Change comment: There is no comment for this version
To version 192.1
edited by Carlijn Kokkeler
on 2024/01/29 15:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -229 - Xpath Alignment
1 +213 - Joyful Journeys
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,10 +1,31 @@
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 +In the last sprint cycle, we focused on improving pop-up messages to improve the user experience. Moreover, we did several alignment & formatting improvements. Lastly, some more feedback items have been solved, and several more bug fixes have been done.
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.213 - Joyful Journeys||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.
5 +=====New features=====
7 7  
7 +* Home - Q&A: The option to search by pressing the Enter key has been added.
8 +
9 +=====Minor changes=====
10 +
11 +* All - Input fields: Multiple input fields have been updated to expand when the amount of characters exceeds the default size. (#822)
12 +* Design - Message: The tooltip for the optional/required toggle has been improved. (#1172)
13 +* Create - Transformation: UI improvements for static input components have been done. (#1172)
14 +* Create - Resources: A button "Update flows" has been added to update versions of all flows in which a resource is used. (#1129)
15 +* Deploy - Releases: When a new property release is created, this property release can now not only be viewed but also release properties can be deleted. (#1031)
16 +* Deploy - Containers: The error message that is displayed when deleting a runtime is now more descriptive. (#1053)
17 +* Deploy - Runtime overview: Insight into intended and actual deployments has been improved.
18 +* Deploy - Architecture: It is now possible to change the memory settings of a new container before pressing "Apply to environment". (#968)
19 +* Deploy - Architecture: Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. (#977)
20 +* Deploy - Architecture: The formatting of action messages regarding changes in retention bytes/hours has been improved.
21 +* Manage - Explore: The error messages that may be displayed when using wiretaps and the debugger have been improved.
22 +
8 8  ====Bug fixes====
9 -* Create - Flow Designer: Improved the help text 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 it exists. (#1010)
24 +
25 +* Create - Flow Designer: We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before). (#1021)
26 +* Create - Flow Designer: A bug has been fixed where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. (#1030)
27 +* Deploy - Architecture: During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
28 +* Manage - Monitoring: The correct number of cache hits and misses are now shown in the state generation statistics. (#1161)
29 +* Manage - Monitoring: We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
30 +* Manage - Explorer: We aligned all timestamp formatting to yyyy-MM-dd HH:mm:ss.SSS. (#1151)
31 +* Manage - Notification settings: Internal recipients are now added correctly.