Skip to Content

Changes for page 237.1 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
From version 44.1
edited by Erik Bakker
on 2023/01/23 13:49
Change comment: There is no comment for this version
To version 99.1
edited by Erik Bakker
on 2023/08/01 14:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -190 - Fast Forward
1 +202 - New Equilibrium
Content
... ... @@ -1,32 +1,36 @@
1 -The release finished many new improvements to our 3rd generation runtime offering and fixed various annoying bugs and minor enhancements. Furthermore, we introduce several improvements in the interaction with the portal.
1 +In the last sprint cycle, we focused on finishing our work on the release properties functionality introduced in this release. On top of that, we have some additional smaller feedback items and bug fixes coming out of the Hackathon for you.
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.202 - New Equilibrium.WebHome||target= "blank"]].
4 4  
5 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.V120.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.
8 8  
9 -=====Major changes=====
7 +* Deploy - Releases: We removed two unnecessary release options: “Set release properties” and “Check properties. “ You can quickly update your properties via the Release properties overview.
8 +* Deploy - Releases: Before activating or deploying a new release, you should fill in all properties that relate to your deployment. If there are any properties without value, we will show them to you. Then you can update them and continue your deployment.
9 +* Deploy - Properties: This tab 'Properties' for managing properties is deprecated as of Release 202. As a result, it cannot be used anymore to manage properties. You can manage your properties via the 'Releases' overview. On this overview, you can select the wrench icon on the 'Create phase release' to find the property management overview. For more information about the management of properties and the related features, click on the right-bottom corner on 'Help and check out our documentation.
10 +* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture to host a MQTT broker in a failover (i.e., double lane) architecture. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
10 10  
11 -* 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.
12 -
13 13  =====Minor changes=====
14 14  
15 -* 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.
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 the user can use it to compare the previous versions.
18 -* Create - Flow Designer: when importing a store item from another partner, an error popup will be shown instead of the default error message.
19 -* Deploy - Releases: The activate release functionality improved performance for 3rd generation models.
20 -* 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)
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 - 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.
14 +* Store - Export: "Store exporter" users can test their exported store items immediately without waiting for approval. (#1001)
15 +* Deploy - Releases: The infographic has been updated.
16 +* Deploy - Release Properties: Required properties are checked if they contain nested properties and are not missing values.
17 +* Deploy - Property release: Names of properties can be created/removed/edited.
18 +* Deploy - History: We deprecated the old page History, which displays the property changes in your model. The properties' history is on the Deploy phase's History page.
19 +* Deploy - Architecture: Changes made to AWS Slot settings are recorded in history. (#996)
20 +* Manage - Monitoring: Improved performance of 3rd generation runtime dashboards.
21 +* Infrastructure: Tightened security policies for a more secure infrastructure.
24 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 copying and pasting, 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 the setup step.
29 -* Deploy - Containers: We fixed 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. 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.
32 32  
25 +* Design - Import: Import into design from the store is possible, even if the integration is not in Create yet.
26 +* Create - Flow Designer: Improved validation on XPath header enricher. (#1005)
27 +* Create - Flow Designer: We fixed an issue that your flow fragment metadata disappeared when you canceled your changes of the existing flow fragment in your new version of the store item. (#989)
28 +* Create - Flow Designer: In some cases, when copying/pasting components into a flow, validation alerts would be displayed that did not belong to a component. This problem is now fixed. (#955)
29 +* Create - Flow Designer: We fixed an issue that prevents dragging and dropping an annotation from the left panel after a search from the search box. The speed of creating the dialog to enter the component’s name is also improved.
30 +* Create - Flow Testing: Properties will not disappear from the list when canceling changes on a default property value. (#913)
31 +* Create - Flow Testing: Users with view rights can edit test case names, descriptions, and property values. (#973)
32 +* Deploy - Architecture: The runtimes will display the number of connected flows, not "Zero."
33 +* Deploy - Architecture (Runtime Settings): Moved the delete button to the right side of the page and fixed the bug in the help text.
34 +* Deploy - Releases: We fixed an issue that prevented you from seeing a comparison message when hovering over an exit gate flow of the API pattern if you compare two release versions in Deploy. (#839)
35 +* Deploy - Releases: We improved the loading buttons of releases on the right pane by Order (Ascending).
36 +