Changes for page 256 - Power Up

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-256 - Power Up
	1	+196 - Last Post

Content

...	...	@@ -1,15 +1,38 @@
1		-This release features various updates to our platform, with a user-centric focus, as we work on improved functionality for our new event streaming broker and API Gateway. All those improvements will be shared in the future once everything is ready. Additionally, we want to raise awareness that several new **[[environment templates>>> Main.Release Information.Cloud Templates.WebHome||target="blank"]]** have been released that need to be updated before **December, 14th**. So if you have yet to update please take the necessary actions.
	1	+Here's our first release of this quarter. We have delivered additional small (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 improvements in the way of work for nextGen environments.
2	2
3		-Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.256 - Power Up.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		-==== Bug fixes ====
	5	+=====New features=====
6	6
7		-* Design - System Message: Improved performance of saving entities whith a large number of attributes. (#1731)
8		-* Design - Store: Two fixes on importing store items for synchronous messages. (#1579)
9		-** From store functionality for API Gateway is restored.
10		-** Additionally, users can import store item to synchronous system message - response message.
11		-* Design - Create - System Message (API integrations) - The request system message correctly displays the message definition (#1713)
12		-* Create - Add Integrations: We have fixed a bug where some Mendix systems could face an error when trying to add an event streaming integration in Create.
13		-* Deploy - Containers: Debug icon has on hover text (#1725)
14		-* Manage - Alerting: Partial words from an alert's description can be searched and still return accurate results. (#1726)
	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.
15	15
	9	+=====Minor changes=====
	10	+
	11	+* Deploy - Architecture: The topics are now ordered alphabetically and the runtimes will now get the same order as design architecture (after ‘apply to environment’)
	12	+* 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.
	13	+* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are ran.
	14	+* Administration-User management: Company contact can edit permissions of models that fall under child companies
	15	+* Administration: Contracts page removed
	16	+* Create-Flow designer: Model resources tab removed on resources page when adding an resource to a validating filter.
	17	+* 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.
	18	+* Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible.
	19	+* 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.
	20	+* 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.
	21	+* 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.
	22	+* 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.
	23	+* 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.
	24	+* 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.
	25	+* 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.
	26	+* 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
	27	+* Create - Flow designer: Improve responsiveness of resources tab at right panel
	28	+* Manage - Explore: New button to delete queue is added and only visible for Expert Service (Admin)
	29	+
	30	+====Bug fixes====
	31	+
	32	+* 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.
	33	+* 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.
	34	+* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs.
	35	+* 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.
	36	+
	37	+====Remarks====
	38	+