Changes for page 241 - Wild West
Last modified by Erik Bakker on 2025/03/27 09:08
From version 234.1
edited by Erik Bakker
on 2025/03/24 06:40
on 2025/03/24 06:40
Change comment:
There is no comment for this version
To version 185.1
edited by Carlijn Kokkeler
on 2024/01/15 14:46
on 2024/01/15 14:46
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 -2 41 -WildWest1 +212 - Failover Fiesta - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,31 +1,27 @@ 1 -In the last sprint ,we have released a lot in terms of usabilityimprovements both while working within the various phases of eMagiz as well as when deploying your hard work to the environment of yourchoice. As a result, wehave a series ofimprovements and bug fixes for you to enjoycoming out of the hackathon. On top of that, we releasea new [[runtime image>>doc:Main.ReleaseInformation.RuntimeImages.V330.WebHome||target="blank"]] containing a much needed improvement regarding deployment executions when working with state generation and code mappings on top of various improvements in our underlying code.1 +In the last sprint cycle, we focused on .... 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.2 41 -WildWest.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]]. 4 4 5 -==== MinorChanges====5 +=====New features===== 6 6 7 -* Overall - Q&A Forum: When viewing a question, you can now easily copy the link to the question to your clipboard (#1471) 8 -* Capture - Add Integration: Removed the ‘remarks’ field from the ‘New Integration’ screen in Capture, because this field was not visible enough in the rest of the portal. (#1608) 9 -* Capture / Design: For new systems, message types, machines, tenants and models hyphens are not allowed in the technical name anymore. The technical name can only consist of lower case letters and digits and must start with a letter. This also applies to systems, message types and tenants that have not yet been transferred from design to create. The portal will give an error message while transferring and the hyphen has to be removed manually. 10 -* Create - Flow designer: Display name character limitations are visible in the validation feedback when adding new flow components (#1554) 11 -* Create - Resources: When trying to delete a message definition, the portal shows which transformation(s) use this message definition and should be deleted as well (#1616) 12 -* Deploy - Deployment Plan Execution: We have improved the stability of the deployment plan procedure. 7 +* Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines. 8 +* Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes. 13 13 10 +=====Minor changes===== 11 + 12 +* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 13 +* Deploy - Deployment: The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment. 14 +* Deploy - Architecture: The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'. The risk level is either medium or high. 15 +* Manage - Alerting: You can now add external recipients to your environment directly, like internal users. (#917) 16 +* Manage - Monitoring: It is now possible to select the MQTT broker in the queue metrics dashboards. 17 +* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start. 18 + 14 14 ====Bug fixes==== 15 15 16 -* Capture - Add System: When a user tries to creates a system or edits a system, loading bar is displayed before showing the pop-up. (#1228) 17 -* Capture - Edit System: When editing a system, the validation now takes into account that the name cannot be an empty string. (#1562) 18 -* Design - Message Definition: small improvements are introduced: 19 -** the widget can prevent user multiple message attributes on a message entity for the same attribute in datamodel. 20 -** when adding a new message entity to a current message entity, it doesn’t throw exception when user double click to many times in Save button 21 -* Design - Catalog: When exporting swagger json, in case an operation has example in request, the example will be shown correctly in swagger. (#1597) 22 -* Design - Solution Architecture: When modifying the number of runtimes of a system, the validation will now take into account that the value may not be empty (#1513) 23 -* Create - Add Integrations: Users are able to untransfer a flow even when there is a property attached to the flow. (#1590) 24 -* Create - Add Integrations: Flow, flow versions and the corresponding integration in the Deploy phase is cleaned when an integration is utransferred from the Create phase. 25 -* Create - Components: The browser page now displays the correct page title (#1509) 26 -* Create - Flow designer: When removing a wiretap from a channel, confirmation will only be asked once now. (#1549) 27 -* Create - Flow Designer: The default name of the REST template support object generated in passthrough API gateway operations now matches the (technical) name of the integration. (#1560) 28 -* Deploy - Properties: Fixed a bug where property descriptions were not updated when there was already a property description in place. (#1526) 29 -* Deploy - Environment Template: Fixed a bug where upgrading a fully on-premise environment would incorrectly exclude some machines. 30 -* Manage - Queue Browser: Switching environments when exploring a queue in Manage → Explore now moves the user to the queue browser of the correct environment. (#1408) 31 -* Infra - Runtime Image: The cache used for code mappings is now properly started and stopped with the application. This prevents that flows using code mappings may encounter errors when stopping their runtime and messages were still processed. (#1550) 21 +* Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. 22 +* Deploy - Cloud template: An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks. 23 +* Deploy - Deployment: Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model. 24 +* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by a container. 25 +* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. (#1108) 26 + 27 +