Skip to Content

Changes for page 234 - Alert Adventures

Last modified by Carlijn Kokkeler on 2024/11/18 15:29
From version 335.1
edited by Carlijn Kokkeler
on 2024/11/04 11:29
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 -233 - TBD
1 +191 - Fifty Fifty
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,22 +1,36 @@
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, as well as pop-ups and search functionalities. Find out all 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.232 - Bug Busters||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 -* Login: Our password policy has been updated such that the minimum length is 14 characters, other requirements have remained the same. All users will be required to update their password when logging in. You will not be able to close this popup until your password has been updated successfully.
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 changes====
9 -* Create - Flow Designer: We have added two additional configuration options to the SMB session factory support object.
10 -** Connect as guest: We have added the option to toggle whether the session factory should attempt to connect as a guest if the login attempt with the provided username and password is rejected.
11 -** Force SMB version 2: We have added the option to enforce the usage of SMB version 2. This effectively disables backwards-compatible version negotiation.
12 -* Deploy - Architecture: Several improvements for our failover functionality have been done:
13 -** We have improved the warning message for the balance failover deployment plan step, making it more clear how to solve this issue should it occur during your deployment.
14 -** We have added the option to manually initiate the failover balancing process, saving you from having to execute your deployment. This action can be found in Deploy Architecture, when right clicking on the white canvas.
15 -** We have added a visualization of connector systems that are pending a failover enable or disable in Deploy Architecture. Besides that, you will also see this shown in the pending changes list when you apply your changes to the environment.
13 +=====Major changes=====
16 16  
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 +
17 17  ====Bug fixes====
18 -* Create - Flow Designer: If a component misses a support object, an alert is now shown in the Flow Designer, displaying which support object is missing.
19 -* Create - Flow Designer: The XML to flat file and flat file to XML transformers have been restyled, such that they are similar to all other components.
20 -* Create - Flow Designer: We fixed an issue where the browser page would get frozen when editing a flow component.
21 -* Manage - Explore: When clicking the queue browser button, the user will not be redirected to the home page anymore.
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.
22 22