Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 45.1
edited by Erik Bakker
on 2023/01/31 14:39
Change comment: There is no comment for this version
To version 332.1
edited by Carlijn Kokkeler
on 2024/10/21 12:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -191 - Fifty Fifty
1 +232 - Bug Busters
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,36 +1,21 @@
1 -The release introduces a lot of small fixes as a result of our "hackathon" efforts. Subsequently we will release several 3rd generation runtime offerings.
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.191 - Fifty Fifty.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.232 - Bug Busters||target="blank"]].
4 4  
5 -=====New features=====
6 -* Manage - Alerting: There are 4 new types of triggers available for Model in G3.
7 -** Error Message is to evaluate the headers of the original message which resulted in an error.
8 -** Log Keyword is to evaluate logging messages. You can provide a one or several words which you expect in your logging events.
9 -** Queue Consumers is to configure for queues where more than 1 consumer is expected.
10 -** Queue Messages is to configure for queues where more than 100 messages on a queue can occur
11 -** Queue Throughput is to monitor issues with your system by setting thresholds for the number of messages that are expected to pass through the flow.
12 12  
13 -=====Major changes=====
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)
14 14  
15 -* Manage - Redelivery: You can explore the message redelivery functionality for the 3rd generation architecture and see more details about it. Besides that, you can also redeliver the message(s) on this page.
16 16  
17 -=====Minor changes=====
18 -
19 -* Design - System message: 'Request' and 'Response' entities are automatically generated and set as root entities for new SOAP web service integrations in 3rd generation runtimes.
20 -* Create - Flow designer: sensitive information stored in property values is masked. (#790)
21 -* Create - Flow Designer: when migrated from Gen2 to Gen3, the flow's JSON will be generated so the user can use it to compare the previous versions.
22 -* Create - Flow Designer: when importing a store item from another partner, an error popup will be shown instead of the default error message.
23 -* Deploy - Releases: The activate release functionality improved performance for 3rd generation models.
24 -* Deploy - Architecture: Before pressing "Apply to environment," we require a confirmation from you if you accept the topology changes suggested by eMagiz that might impact AWS. (#828)
25 -* Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571)
26 -* Deploy - Architecture: "HTTP settings" page changed to "Runtime settings," where you can enable/disable both HTTP and control bus per runtime.
27 -* Deploy - Releases - You will be reminded of empty runtimes when activating a release. Empty runtimes are runtimes without flows in the release, and these runtimes should be removed from your architecture.
28 -
29 29  ====Bug fixes====
30 -* Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508)
31 -* Create - Flow Designer: When copying and pasting, support objects such as "property placeholder," "support.bus-connection-caching," and "support. bus-connection-plain" are not duplicated (#793)
32 -* Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in the setup step.
33 -* Deploy - Containers: We fixed an issue that the container overview does not show the entry flows which should run on that container. (#863)
34 -* Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814)
35 -* Deploy - Architecture: The deploy runtimes option is only visible for admin. A new menu item, "Deploy agent," is added and visible for all users to show the command which can be used to deploy the agent to an on-premises machine.
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)
36 36