Skip to Content

Changes for page 217 - Template Tango

Last modified by Carlijn Kokkeler on 2024/05/22 13:34
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 77.1
edited by Erik Bakker
on 2023/05/09 13:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -186 - Daemon Switch
1 +197 - Pay Attention
Content
... ... @@ -1,35 +1,21 @@
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 +Another couple of weeks have passed, so it is time for a new release. We have delivered additional minor (bug) fixes in this release and released the event streaming alerting. The last is a real improvement in managing your event streaming solution. Furthermore, you will find several enhancements in working in nextGen environments.
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.197 - Pay Attention.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 +* 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.
7 +* Manage - Alerting: Added support for providing alerts on event streaming topics: consumer lag, topic approaching maximum size & messages added to the topic under the threshold. Two new alerts are introduced to send alerting messages to the user when messages added to the topic is greater than a threshold or when topic messages consumed is below a threshold. These new alerts are applied for all runtime architectures we support.
7 7  
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.
11 +* Create - Flow Testing: we add some minor UI improvements and validation to prevent a test case from being in live mode and automated.
12 +* Deploy - Deployment plan: If you run the deployment plan to deploy machines and run into issues, your deployment plan will be stopped at the step that gets a warning, and you can see a warning message on the left side. That is easier for you to figure out problems and fix them. Afterward, you can run that step again by selecting "Refresh" and "Execute."
13 +* Deploy - Architecture: We increased the grace period for shutting down runtimes when they run on Docker environments.
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
16 +
17 +* Create - Store: We fixed an issue that you sometimes do not see the list of message definitions or the list of transformations when you export new or update your store item.
18 +* Deploy - Architecture: You can apply your changes to only one or both zones on 3rd generation double-lane models.
19 +* Deploy - Architecture: We fixed an issue where runtimes were not removed from a machine, while this was expected behavior according to the architecture.
20 +* Deploy - Architecture: The gen two karaf container will now exit when an Out-of-memory error occurs for gen three cloud environments. This will cause an auto-healing restart, after which the container can run properly again.
21 +* Design - Message Definitions: "Message format" button is also available in view mode. (#919)