Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 52.1
edited by Erik Bakker
on 2023/03/03 08:50
Change comment: There is no comment for this version
To version 318.1
edited by Erik Bakker
on 2024/09/10 10:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -193 - Fan Out
1 +229 - XPath Alignment
Content
... ... @@ -1,21 +1,11 @@
1 -The release introduces REST/XML as option for your gateway operations as well as new features for our 3rd generation runtime, a new runtime image, and new cloud templates. Subsequently, we will release several minor feedback points and bug fixes.
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.193 - Fan Out.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.229 - Xpath Alignment||target="blank"]].
4 4  
5 -=====New features=====
6 -* Deploy - Releases: New release properties pop-up that shows all properties in your release, grouped by containers that they are assigned to. This pop-up can be accessed by pressing the wrench shaped icon, which becomes available once a release is set as active.
7 -* Design - Settings: We added XML support to API Management. To enable this feature, change the 'Default message format' in the Design settings section. You can change individual operations by changing the message format of your gateway message. Migrating existing operations requires a reset of the exit flow and a change in the catalog in Design. For more information see the release blog post. (#815)
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)
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.
8 8  
9 -=====Minor changes=====
10 -
11 -* Design - API Gateway: OData API type exclusively selectable for system admin. (#816)
12 -* Design - API Catalog: When you change a path in Design phase, your HTTP inbound gateways that use the changed path will also be updated in Create phase if you have edit rights. (#524)
13 -* Manage - Error messages: Message history is sorted by timestamp descending.
14 -
15 15  ====Bug fixes====
16 -
17 -* Create - Message Definition: Attribute can be declared as JSON array in API Gateway and Event Streaming (#908)
18 -* Create - Migration: We fixed a third generation migration issue, where the legacy error handling flow components were not removed from the asynchronous routing flow.
19 -* Create - Flow designer: when migrating a container’s flows from gen2 to gen 3, “global wire tap” components and their relevant components will be removed.
20 -* Deploy - Release: We fixed an issue that caused images to not be built in specific situations when running in the new runtime generation runtime.
21 -* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish. (#797)
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)