Skip to Content

Changes for page 197 - Pay Attention

Last modified by Carlijn Kokkeler on 2024/05/22 13:41
From version 16.1
edited by Erik Bakker
on 2022/10/28 16: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 -186 - Daemon Switch
1 +191 - Fifty Fifty
Content
... ... @@ -1,35 +1,36 @@
1 -The release brings the new monitoring stack to fruition and various updates to handling multiple namespaces. On top of that, we have released a slew of smaller feedback items and bug fixes.
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.186 - Daemon Switch.WebHome||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 5  =====New features=====
6 -* Generic - New monitoring stack: As of this release, you can run on the new monitoring stack. For more information on becoming an early adopter, don't hesitate to get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
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  
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 +
8 8  =====Minor changes=====
9 9  
10 -* Design - Solution: You will see a warning in the Solution view on operation if it is not connected to a backend API operation or in "Transformation" mode.
11 -* Design - API Gateway: Changes in your Gateway messages are reflected directly in your OpenAPI JSON document.
12 -* Create - Flow Designer: You can now see who/when a resource was changed on a resource view page.
13 -* Create - Flow Designer: You can see all related configurations that use a specific resource when viewing the details of the resource.
14 -* Create - Flow Designer: Increased size of the SpEL expression input field of standard transformer component.
15 -* Create - Flow Designer: Show generated resources toggle is not disabled by default; your preference for showing or hiding generated resources will be saved.
16 -* Create - Flow Testing: The name of the starting point in the flow testing result tab is matched with the component type.
17 -* Create - Flow Testing: Added a button to display the content of a selected trace message in a pop-out.
18 -* Deploy - Releases: The automated flow test pop-up can now be closed by pressing "Enter."
19 -* Deploy - Properties: Password-type properties are masked in the unused properties pop-up.
20 -* Deploy - Properties: You can use enter key to search on the property overview page.
21 -* Deploy - User Management: "Generate Keystore" button is renamed "Download Keystore," and the file name contains environment information.
22 -* Administration - Licenses: Added event streaming storage usage of your models.
23 -* Model Dashboard - Going to manage from the model dashboard now loads the error message dashboard without having to click on the error messages dashboard explicitly
24 -* Store: Compatibility check is added, which prevents importing G3 store items into G2 flow/integration
25 -* General: Improved help texts explaining options and screens related to the new runtime architecture or the migration towards it.
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.
26 26  
27 27  ====Bug fixes====
28 -* Design - Integration Designer: For event streaming integrations, switching between Design Mapping and Create Transformation sometimes did not work.
29 -* Create - Transformation: For event streaming integrations, the 'Start editing' button sometimes did not work.
30 -* Create - Flow Designer: While editing an exit flow, the system message is not editable.
31 -* Create - Flow Designer: Comparing two flow versions works again.
32 -* Create - Flow Designer: When creating my initial version of a flow, the notification pop-up shows the correct information.
33 -* Create - Flow Designer: All relevant support objects will be highlighted when selecting a support object.
34 -* Deploy - Properties: Improved the layout of the cron trigger generator page
35 -* Deploy - Properties: Generating a password or CRON trigger will not reset the runtime field
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 +