Changes for page 232 - Bug Busters
Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 254.1
edited by Carlijn Kokkeler
on 2024/05/22 13:31
on 2024/05/22 13:31
Change comment:
There is no comment for this version
To version 312.1
edited by Erik Bakker
on 2024/09/09 09:54
on 2024/09/09 09:54
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -22 1-SwiftShift1 +229 - Xpath Alignment - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,17 +1,10 @@ 1 - Inthelast sprint cycle, we done several improvementsfortheDesignandDeployphases.Moreover,wehaveimprovedtheEventCatalog overview forCatalog users.Ourbug fixesconcerntheimportof xsds, thedeletionbehaviourofcontainerse,andthegenerationofscope properties.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. 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.22 1-SwiftShift||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 -* Design - CDM/System message: A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add a new attribute. (#151) 7 -* Design - System message: Moving an attribute in the datamodel is now directly shown in the tree structure as well. (#151) 8 -* Design - CDM/API Data model/ES data model and system message: The pop-up that appears when rearranging attributes of an entity will result in a pop-up which text is conditional with respect to the messagetype. (#151) 9 -* Deploy - Deploy release: When executing a start/stop action on a group, the description of the step now contains the name of the group. 10 -* Deploy - Architecture: When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group". 11 -* Q & A: Search results are now persisted when pressing the back button after opening a question in the community Q & A. (#1324) 12 -* Catalog: For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation. 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. 13 13 14 14 ====Bug fixes==== 15 -* Design - System messages: When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion. (#140) 16 -* Deploy - Containers: The delete behaviour of containers in the container overview has been improved. (#1053) 17 -* Deploy - API Gateway: We fixed an issue where the generation of scope properties was incorrect for legacy API gateway runtimes using OAuth 2.0 security scheme. 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)