Skip to Content

Changes for page 236 - Another Agent

Last modified by Erik Bakker on 2025/01/13 09:32
From version 175.1
edited by Carlijn Kokkeler
on 2023/12/21 16:27
Change comment: There is no comment for this version
To version 76.2
edited by Erik Bakker
on 2023/05/09 13:47
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +197 - Pay Attention
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,28 +1,35 @@
1 -In the last sprint cycle, we focused on improving several aspects related overviews and logging. It is now possible to see an overview of all runtimes on running machines, see runtimes and flow versions in the missing properties overview, and see which runtimes will be restarted or redeployed in a pop-up displayed when starting the deployment plan. Moreover, crash handling has been improved, as well as runtime logging and the display of the deployment execution error message. Lastly, several other minor changes and bug fixes have been done, mainly relating to the Deploy and Manage phase.
1 +Here is our first release of this quarter. We have delivered additional minor (bug) fixes in this release and released the Live Flow testing feature. The last is a real improvement during the development process of a flow. 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.211 - Log Luminary||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.196 - The Last Post.WebHome||target= "blank"]].
4 4  
5 5  =====New features=====
6 6  
7 -* Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview.
8 -* Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
7 +* Create - Flow Testing: Till now, Flow Testing allowed to test eMagiz flows by defining a testing point on the start (and end) point(s), running them, and comparing the actual and expected messages. In this release, "Live Mode Testing" is introduced, making testing communication with an actual "live" endpoint possible. As a result, an "HTTP outbound gateway" can be set in "Live Mode." When you do this, the HTTP outbound gateway will send its request to the endpoint. Consequently, the response will be handled by the flow in the flow test so you can determine whether the actual endpoint behaves as expected.
9 9  
10 10  =====Minor changes=====
11 11  
12 -* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
13 -* Deploy - Deployment: The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
14 -* Deploy - Architecture: Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'.
15 -* Manage - Alerting: You can now add external recipients to your environment directly, like internal users.
16 -* Manage - Monitoring: It is now possible to select the MQTT broker in the queue metrics dashboards.
17 -* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
11 +* Design - Store: You can encounter a warning message when you import a transformation from the store because your imported transformation requires information from the related store fragment. To avoid a non-functional transformation in the Create phase, you should include that store fragment. Afterward, we will update your default flow component transformer to make it work correctly.
12 +* Design - Store: We updated importing to help you avoid an error while importing store items that will break your message definition in some cases.
13 +* Design - Store: We fixed an issue that you import the message definition(s), and a specialized DataType of imported message definition(s) is not matched with the exported message definition(s). Now, they are matched, and your transformation won't get issues.
14 +* Create - Store: We automatically excluded resources that are not good enough from the exporting wizard. Then you will find it easy to recognize a problem and avoid creating unusable store items.
15 +* Create - Flow designer: CDM edit right is applied to the message definition in Create phase. You can only change the CDM message definition, Gateway message definition, or even Event streaming message definition with the proper rights. (#690)
16 +* Create - Flow designer: Model resources tab removed on the resources page when adding a resource to a validating filter. (#921)
17 +* Create - Flow designer: Improve the responsiveness of the resources tab on the right panel.
18 +* Create - Flow Designer: Resources in the "Unused resources" section can be marked as used when components refer to the resources through property placeholders or in custom SPeL expressions.
19 +* Create - API Gateway: We fixed an issue where an optional query parameter would cause failed requests if that parameter was not supplied, so please reset your entry flow to apply the fix.
20 +* Create - API Gateway: We fixed an issue where API-Key secured requests would fail with error code 500 instead of code 401 if no API-Key was supplied. Please reset your entry flow to apply the fix.
21 +* Create - Resources: When viewing a resource, its full name will be shown, removing the need to download the resource to obtain its name. (#922)
22 +* Deploy - Releases: We reduced the time it takes to prepare a release before it can be deployed. The process of building runtime images has been optimized.
23 +* Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible.
24 +* Deploy - Architecture: The topics are now ordered alphabetically, and the runtimes will now get the same order as design architecture (after 'apply to environment') (#543)
25 +* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are run.
26 +* Manage - Explore: A new queue delete button is added. This button is only visible to authorized personnel.
27 +* Administration -User management: Company contact can edit permissions of models that fall under child companies. (#895)
28 +* Administration - Overview: Contracts page removed. (#907)
18 18  
19 19  ====Bug fixes====
20 20  
21 -* Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history.
22 -* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by the container.
23 -* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal.
24 -* Deploy - Cloud templates: An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks.
25 -* Deploy - Deployment: Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
26 -
27 -
28 -
32 +* Create - Flow designer: Improved help texts of various flow components related to key-/truststores and their usage. They better explain what you need them for and mention essential security considerations.
33 +* Create - Flow designer: Various minor (cosmetic) fixes and changes in the edit pages of some flow components to make them more consistent with similar pages.
34 +* Deploy - Releases: We fixed an issue where after removing containers from a machine, during the execution of the deployment plan, the removed containers are not recognized as change, causing the 'Deploy machine' step to be skipped. (#514)
35 +* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs. (#940)