Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 185.1
edited by Carlijn Kokkeler
on 2024/01/15 14:46
Change comment: There is no comment for this version
To version 331.1
edited by Carlijn Kokkeler
on 2024/10/21 12:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -212 - Failover Fiesta
1 +232 - TBD
Content
... ... @@ -1,27 +1,21 @@
1 -In the last sprint cycle, we focused on ....
1 +During our recent sprint cycle, We did a hackathon again so we have a lot of bug fixes! The visibility of several buttons has been improved, search functionalities have been improved, and pop-ups have been corrected. Find out all below!
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.231 - Microscopic Madness||target="blank"]].
4 4  
5 -=====New features=====
6 6  
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.
6 +====Minor changes====
7 +* Deploy - Releases: When creating a new property name for a new property value, it wil automatically be selected for the new property value. (#1433)
9 9  
10 -=====Minor changes=====
11 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 -
19 19  ====Bug fixes====
11 +* Design - Architecture: It is no longer possible anymore to create machines with the same technical name. (#1457)
12 +* Design - Architecture: When enabling or disabling our failover feature for a system, its connector container will no longer be moved to another machine if not required.
13 +* Create - Flow Designer: The tooltip in the Flow Designer now zooms in/out correctly. (#1496)
14 +* Create - Flow Designer: The conditional visiblity of filtering operations of SMB, SFTP & FTP outbound gateways when using the 'remove' and 'get' operations has been improved. (#1439)
15 +* Create - Transformation: Source filters will now display the attribute filter statement correctly. (#1353)
16 +* Deploy - Architecture: The pop-up that is shown after pressing 'apply to environment' in Deploy Architecture will only show the current changes, irrelevant information has been removed. (#1104)
17 +* Deploy - Containers: The 'Delete' button in the Containers overview is no longer visible for users without the required permissions. (#1464)
18 +* Deploy - Releases: We updated the user rights in a model such that in order to deploy a release in Deploy, you should have both edit rights in Deploy and Manage. (#1495)
19 +* Manage - Code Mappings: When searching in the code mappings overview and pressing enter in a search field, search results would get duplicated. This has been fixed. (#1105)
20 +* Manage - Explore: The 'Explore' button will no longer be hidden if there are no results when searching on a queue name in the queue browser. (#1409)
20 20  
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 -