Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 262.11
edited by Danniar Firdausy
on 2024/07/02 14:00
Change comment: There is no comment for this version
To version 45.1
edited by Erik Bakker
on 2023/01/31 14:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -224 - Summer Sonata
1 +191 - Fifty Fifty
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.ebakker
Content
... ... @@ -1,23 +1,36 @@
1 -During the recent sprint cycle, our focus has been on enhancing flow testing performance, resulting in up to threefold faster execution times. Additionally, we've refined platform usability based on community feedback, which includes enhancements to help text functionality, various pop-up pages, and the user interface for debugging integration flows. Find out all features and fixes below.
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.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.224 - Summer Sonata||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.191 - Fifty Fifty.WebHome||target="blank"]].
4 4  
5 -====New features====
6 -* Create - Flow designer : Users can now perform flow testing more quickly, as the execution of the flow testing functionality is now faster by up to three times.
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.
7 7  
8 -====Minor Fixes====
9 -* Capture - Specify integration requirements: The questions under the Connectivity/Security tab now correctly asks for the required retention duration and bytes for the integration/topic, instead of retention size and bytes (#1184)
10 -* Capture - Specify integration requirements: Clicking the "?" icon on the top right corner of the pop-up page now correctly hides the help text pane. (#1362)
11 -* Capture - Specify integration requirements: Clicking add or remove a tag in this pop-up page now works correctly and no longer displays a 'blocked' icon. (#1343)
12 -* Design - Message definition : The pop-up page shown when you press the 'Add Attribute' button on the right panel of your System Message, CDM, API Data Model, or Event Streaming Data Model now uses scrolling instead of pagination. Thus, selecting multiple attributes there now does not risk losing the already selected ones. (#1332)
13 -* Design - Architecture: Spelling mistakes in the steps to be executed within the pop-up page when applying to environment in Design architecture are now fixed. (#1390)
14 -* Create - Flow designer : The pop-up page displaying flow properties with non-editable input fields containing long text now shows the entire content without any text being cut off at the edge of the page. (#1301)
15 -* Create - Flow designer : In the pop-up page displaying flow properties, copying password properties now copies the actual password value instead of the encoded value.
16 -* Create - Flow Designer : A new "Save and Add New" button has been added for adding enumeration values to attributes with an Enumeration data type when editing a message definition.
17 -* Create - Flow Designer : The help text for the HTTP method field in the HTTP outbound gateway and HTTP outbound channel adapter flow components now provides more elaborate descriptions of different HTTP methods. Additionally, a validation check is also implemented to these components to prevent selecting the HTTP method 'PATCH' if an Apache HttpComponents REST template is not provided.
18 -* Create - Flow Designer : Clicking links to external documentation in the eMagiz portal is now configured to always open the links in a new tab, rather than replacing your current tab. (#1340)
19 -* Deploy - Containers : A new "Queue Browser" button is now added in the pop-up page after activating the debugging functionality that navigates users to Manage - Explore - Queue Browser page.
20 -* Manage - Explore : The name and description of test messages saved when debugging and wiretapping integrations are now improved.
13 +=====Major changes=====
21 21  
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 +
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 +
22 22  ====Bug fixes====
23 -* Create - Flow Designer : When creating a new event processor for models that were migrated from the legacy runtime architecture to the current generation architecture, the keystore and trustore locations of Kafka message listener container and Kafka template support objects are now correctly generated.
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.
36 +