Changes for page 220 - Patch Parade

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-196 - Last Post
	1	+211 - Log Luminary

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.eMagiz
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -1,39 +1,28 @@
1		-Here's our first release of this quarter. Key focus remains on Flow testing, additional results of the Hackathon and API Gateway improvements
	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.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.196 - The Last Post.WebHome||target= "blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.211 - Log Luminary||target="blank"]].
4	4
5	5	=====New features=====
6	6
7		-* Create - Flow Testing: so far, the Flow Testing allows test eMagiz flows by defining the testing point on the starts and the end points and comparing the actual and expected messages. In this release, “Live Mode Testing” is introduced, making it possible to test communication with real endpoint. That means that an “http output gateway” can be marked in “Live Mode”, if so, the http output gateway will send its http request to the real endpoint and received the result so we can go further with testing.
8		-* Deploy - Architecture: You can now find the Static IP address of connector machines when you update to the new cloud template.
	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.
9	9
10	10	=====Minor changes=====
11	11
12		-* Deploy - Architecture: The topics are now ordered alphabetically and the runtimes will now get the same order as design architecture (after ‘apply to environment’)
13		-* Create - Flow designer: CDM edit right is applied to the message definition in Create phase. You can not change CDM message definition, Gateway message definition, even Event streaming message definition without the proper right.
14		-* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are ran.
15		-* Administration-User management: Company contact can edit permissions of models that fall under child companies
16		-* Administration: Contracts page removed
17		-* Create-Flow designer: Model resources tab removed on resources page when adding an resource to a validating filter.
18		-* 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.
19		-* Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible.
20		-* Design - Store: You are able to see some warning messages when you import a transformation from store. Because your imported transformation is required some information from the related store fragment. You should include that store fragment to avoid a breaking transformation in Create phase after importing. Afterward, we will update your existing flow component transformer to make it work correctly.
21		-* Design - Store: We updated importing to help you avoiding an error during importing store item that will break your message definition in some special cases.
22		-* Create - Store: We excluded automatically resources that are not good enough from the exporting wizard. Then you will easy to recognize a problem and avoid creating unusable store item.
23		-* Flow Designer: Resources in "Unused resources" section can be marked as used for the case that the resources are referred by components through property placeholders or in custom spel expressions.
24		-* Create - API Gateway: We fixed an issue where an optional query parameter would cause failed requests, if that parameter was not supplied. Please reset your entry flow to apply the fix.
25		-* 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.
26		-* Design - Store: We fixed an issue that you import the message definition(s) and a specialized DataType of imported message definition(s) are not matched with the exported message definition(s). Now, they are matched and your transformation won't get issues.
27		-* Create-Resources: When viewing a resource, its full name will be shown, removing the need to download the resource in order to obtain its name
28		-* Create - Flow designer: Improve responsiveness of resources tab at right panel
29		-* Manage - Explore: New button to delete queue is added and only visible for Expert Service (Admin)
	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.
30	30
31	31	====Bug fixes====
32	32
33		-* Create - Flow designer: Improved help texts of various flow components related to key-/truststores and their usage. They now better explain what you need them for and mention important security considerations.
34		-* Create - Flow designer: Various small (cosmetic) fixes and changes in the edit pages of some flow components to make them more consistent with similar pages.
35		-* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs.
36		-* Deploy - Releases: We fixed an issue, where after removing containers from a machine, during execution of the deployment plan, the removed containers are not recognized as change, causing the ‘Deploy machine’ step to be skipped.
	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.
37	37
38		-====Remarks====
39	39
	28	+