Changes for page 237 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52

From version 42.1
edited by Erik Bakker
on 2023/01/18 11:32
Change comment: There is no comment for this version
To version 223.1
edited by Erik Bakker
on 2025/01/31 11:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -190 - Fast Forward
1 +237 - Fabulous Flow
Content
... ... @@ -1,32 +1,23 @@
1 -The release finishes up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs and some minor enhancements. Furthermore, we introduce several improvements in the interaction with the portal.
1 +In the last sprint, we focused on improving the flow back and forth between the various phases in eMagiz by solving several feedback items related to Design, Create, and Deploy and the interaction between these three phases. We have also improved the memory calculation for all runtimes running on a Windows machine. Moreover, we have updated the styling of our graphs in the Manage phase.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.190 - Fast Forward.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.237 - Fabulous Flow||target="blank"]].
4 4  
5 -=====New features=====
6 -* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V110.WebHome||target="blank"]].
7 -* Manage - Explore: The Queue browser is a new feature that enables you to explore the queues on your jms-server and view (and delete) the message on them. It is only available if you migrated your JMS server to the 3rd generation runtime.
5 +====Minor Changes====
8 8  
9 -=====Major changes=====
7 +* Create - Flow Designer: Validation feedback and help text updates for the following components: SMB outbound gateway, SMB session factory, and SMB composite list filter. (#1461)
8 +* Create - Flow Designer: Styling of the following components has been updated. (#1544)
9 +** XML to EDI transformer
10 +** EDI to XML transformer
11 +** XML to UN/EDIFACT transformer
12 +** UN/EDIFACT to XML transformer
13 +* Deploy - Architecture: To prevent out-of-memory events, the calculation of each runtime's memory limit is updated for all runtimes deployed on a Windows machine.
14 +* Manage - Statistics: We have updated our monitoring graph technology, including minor styling updates across the different current-generation monitoring dashboards.
10 10  
11 -* Manage - Redelivery: You are able to explore the message redelivery functionality for the 3rd generation architecture and see more details about it. Beside that, you are also able to redeliver the message(s) in this page.
12 -
13 -=====Minor changes=====
14 -
15 -* Design - System message: 'Request' and 'Response' entities are generated and set as root entities automatically for new SOAP web service integrations in 3rd generation runtimes.
16 -* Create - Flow designer: sensitive information stored in property values is masked. (#790)
17 -* Create - Flow Designer: when migrated from Gen2 to Gen3, the flow's JSON will be generated so user can use it to compare with the previous versions.
18 -* Create - Flow Designer: when importing store item from another partner, a error popup will be shown instead of default error message.
19 -* Deploy - Releases: The activate release functionality gained a performance improvement for gen 3 models.
20 -* Deploy - Architecture: Before apply to environment, we require a confirmation from you if those are some breaking changes that may cause issues in AWS. (#828)
21 -* Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571)
22 -* Deploy - Architecture: "HTTP settings" page changed to "Runtime settings", where you can enable/disable both HTTP and control bus per runtime.
23 -* Deploy - Releases - When activating a release you will be reminded of empty runtimes. Empty runtimes are runtimes without flows in the release. These runtimes should be removed from your architecture.
24 -
25 25  ====Bug fixes====
26 -* Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508)
27 -* Create - Flow Designer: When copy and paste, support objects such as "property placeholder", "support.bus-connection-caching" and "support.bus-connection-plain" are not duplicated (#793)
28 -* Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in setup step.
29 -* Deploy - Containers: We fix an issue that the container overview does not show the entry flows which should run on that container. (#863)
30 -* Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814)
31 -* Deploy - Architecture: The deploy runtimes option is only visible for admin. New menu item "Deploy agent" is added and visible for all users to show the command which can be uses to deploy agent on premises machine.
32 32  
18 +* Design - Message (CDM) Definition: The possibility of importing anything from the store in Design is now blocked when the system has no technical name yet. (#1456)
19 +* Create - Add Integrations: When removing the last integration from a system in create, the container infra flows are also removed from the create phase release. (#1559)
20 +* Create - Flow Testing: Users can navigate to all pages for the logs in their flow test. (#1532)
21 +* Deploy - Releases: The flow version for the Create release on the Deploy phase is synced for that specific flow automatically when the user resets the flow in the Create phase. (#1523)
22 +* Deploy - Architecture: Searching in the start/stop flows overview, and the queue browser can now be done from any page in the overviews. (#1511)
23 +* Manage - Alerting: If the message in a log or error contained a Windows line break (\r\n), and a log or error alert was configured that matched it, an alert would be generated, but no email would be sent out.