Changes for page 232 - Bug Busters
Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 311.1
edited by Erik Bakker
on 2024/09/09 09:52
on 2024/09/09 09:52
Change comment:
There is no comment for this version
To version 102.1
edited by Erik Bakker
on 2023/08/15 12:23
on 2023/08/15 12:23
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 29-XpathAlignment1 +203 - Fast Paced - Content
-
... ... @@ -1,10 +1,19 @@ 1 - Duringour recent sprint cycle, wehaveeveralmprovementstokeepourmodel runningsmoothly.Moreover, wehavemadeome smallchangesto various XPathrelatedpartsoftheportal. Pleasefind out all ourchanges& bug fixes below.1 +In the last sprint cycle, we focused on the scalability and stability of our infrastructure. On top of that, we will release several minor changes with a potentially significant impact. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.2 29-XPathAlignment||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.203 - Fast Paced.WebHome||target= "blank"]]. 4 4 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. 5 +=====Minor changes===== 7 7 7 +* Create - Integrations: Improved the performance of adding or removing API gateway integrations for split entry configurations. (#1023) 8 +* Manage - Alerting: Identifiers of triggers are now visible in the edit screen. 9 + 8 8 ====Bug fixes==== 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) 11 + 12 +* Create - Flows: Fixed an issue where removing some split entry flows from Create phase was not possible after splitting your all entry/combined entry flow. (#1016) 13 +* Deploy - Releases: We fixed an issue that your release contains a JMS server flow twice with different build version numbers when adding another flow to your release. (#597) 14 +* Deploy properties: When a user activates a release containing nested properties and the property is not created, we show it now as missing. On top of that, we add the property placeholder after the user tries to activate the release. 15 + 16 +=====Infra and image changes===== 17 + 18 +* Infrastructure: Tightened security policies for a more secure infrastructure. 19 +* Infrastructure: Added and improved auto-scaling behavior for the eMagiz Control Tower