Skip to Content

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
Change comment: There is no comment for this version
To version 93.1
edited by Erik Bakker
on 2023/06/22 13:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -191 - Fifty Fifty
1 +200 - Uncharted Territories
Content
... ... @@ -1,36 +1,27 @@
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 +In the last sprint cycle, we focused on improving various aspects of the portal functionality. Among others, we focused on the next-generation architecture and others.
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.200 - Uncharted Territories.WebHome||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.
5 +=====Minor changes=====
12 12  
13 -=====Major changes=====
7 +* Create - Flow Designer: it is possible to select multiple components by area selection on the area with a scrollbar.
8 +* Create - Flow designer: The new best practices have updated Kafka components' default values. Updated values are:
9 +** For Kafka templates:
10 +*** Batch size: 200000
11 +*** Linger: 300
12 +** For Kafka message listener containers
13 +*** Fetch min. amount: 100000
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.
15 +{{warning}}The existing Kafka components in your flows will automatically be updated with the new best practice values. To make deploying these changes more effortless for you, we will create a new version of your flows after updating the values (versions will be created in the name of model contacts) and transfer them to the Deploy phase. You can then create and deploy a new release with updated flow versions.{{/warning}}
16 16  
17 -=====Minor changes=====
17 +* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
18 +* Deploy - Architecture: We removed the deprecated reminder popup to update your cloud slot template. The automated upgrade feature replaces it alongside the "Upgrade" functionality in Deploy - Architecture.
19 +* Deploy - Deployment plan: We updated the right pane of the deployment plan to make it more compatible with the new runtime generation. Now, you can see all related logs regarding your deployment. By default, we only show some necessary logs, such as error logs, warning logs, and started runtime information logs. You can use the filter logs icons at the top of the list to show more information.
20 +* Deploy - Deployment plan: We updated the logic within our deployment plan functionality. The deployment step that disables all enabled triggers from the Manage phase disables triggers till you exit the deployment plan overview. That means that those triggers will be re-enabled after you move away from the deployment process or close the browser. Furthermore, there is no deployment step configuration to "enable" triggers anymore.
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.
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  
24 +* Deploy - Architecture: We improved timeout settings to give Stop, Restart, and Reset runtime actions enough time to execute. (#957)
25 +* Design - Store: Importing into "Design" from the store is possible, even if the integration is not in Create yet.
26 +* Manage - Monitoring: Detailed HTTP statistics will now show the correct user in case of API key authorization in more cases. Note that this functionality requires a newly deployed release. (#956)
27 +* Manage - Manage Dashboards: The screen loading speed is significantly improved for all models. This is most noticeable for larger models. (#964)