Changes for page 204 - Found It

Summary

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

Details

Page properties

Content

...	...	@@ -1,21 +1,35 @@
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.
	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.197 - Pay Attention.WebHome||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		-* 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.
8	8
	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.
	8	+
9	9	=====Minor changes=====
10	10
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.
	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)
14	14
15	15	====Bug fixes====
16	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)
	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)