Changes for page 237.1 - Fabulous Flow
Last modified by Erik Bakker on 2025/01/31 11:52
From version 45.1
edited by Erik Bakker
on 2023/01/31 14:39
on 2023/01/31 14:39
Change comment:
There is no comment for this version
To version 104.1
edited by Erik Bakker
on 2023/09/13 07:16
on 2023/09/13 07:16
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 191-FiftyFifty1 +205 - World Explorers - Content
-
... ... @@ -1,36 +1,27 @@ 1 - Thereleaseintroducesalotofsmallfixesasaresultof our"hackathon"efforts.Subsequentlywe will release several3rdgenerationruntimeofferings.1 +In the last sprint cycle, we focused on what we show in Manage concerning the next-generation architecture. Furthermore, we will release a new cloud template. On top of that, we will release several minor changes with a potentially significant impact. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs. 191-FiftyFifty.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.205 - World Explorers.WebHome||target="blank"]]. 4 4 5 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. 6 +* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture in the mount configuration of our file storage solution used on the model level. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information. 12 12 13 -=====Major changes===== 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 - 17 17 =====Minor changes===== 18 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. 10 +* Create - 3rd Generation runtime migration: Your containers will be validated to function with the 3rd generation structure before you approve the migration. 11 +* Deploy - Architecture: The container calculations are improved. For event streaming containers, these show the number of topic proccessors deployed. Gateway containers represent the amount of operations deployed on a container. For JMS containers, these represent the number of message queues deployed. The other types of containers display the amount of integrations deployed. (#544) (#869) 12 +* Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change, and can be multiply selected. (#1046) 13 +* Manage - Alerting - Triggers: The non-editable trigger for Event streaming topic size has been changed to trigger on 95% of the configured size instead of 80%. 14 +* Manage - Monitoring: Viewing runtime, queue, and HTTP statistics are now limited to 7 days at a time. (3rd generation only) 28 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. 36 36 18 +* Deploy - Architecture: Users with edit rights in deploy can edit certificates. (#1054) 19 +* Deploy - Containers: We fixed an issue that some unconfigured flows are deployed incorrectly in the new generation runtimes. 20 +* Manage - Queue statistics: Models with a vast number of queues will now show all queues. This used to be cut off. (Gen3 only) 21 +* General: In some places, the context menu showed too much horizontal whitespace; this has been fixed. 22 +* Create - Flow Designer: Flow designer styling implementation has been updated as part of a set of measures to solve styling issues. 23 + 24 + 25 +=====Infra and image changes===== 26 + 27 +* Infra: New logging feature enabling us to make better choices in deprecating old encryption standards.