Changes for page 256 - Power Up

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-255 - Fine Form
	1	+196 - Last Post

Author

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

Content

...	...	@@ -1,21 +1,39 @@
1		-This release features various updates to our platform, with a user-centric focus, as we work on wrapping up improved functionality for our new event streaming broker. All those improvements will be shared in the future once everything is ready. Additionally, we will release a new **[[runtime image>>Main.Release Information.Runtime Images.V340.WebHome||target="blank"]]** for selected customers and on our flow testing engine. On top of that, we will release new **[[environment templates>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** to allow specific customers to run on our MAM functionality.
	1	+Here's our first release of this quarter. Key focus remains on Flow testing, additional results of the Hackathon and API Gateway improvements
2	2
3		-Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.255 - Fine Form.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		-==== Minor changes ====
	5	+=====New features=====
6	6
7		-* General - Runtime: A new [[runtime image>>Main.Release Information.Runtime Images.V340.WebHome||target="blank"]], for selected customers, and our flow testing will be made available.
8		-* General: The user can now see the names of deactived users again across the platform (i.e. flow history, Q&A). (#1163)
9		-* Deploy - Releases: We have updated the editing release behaviour for the Event streaming pattern. You now have more flexibility for you to add or remove either Event streaming processor flow(s) or Event streaming Mendix connector flow(s) in the release.
10		-** Additionally, we have also fixed the issue where adding or removing event streaming flow(s) resulted in incorrect flow(s) being included or excluded. This update ensures that the correct Event streaming flow(s) are now properly managed during release editing.
11		-* Create - Add Integrations: Users can un-transfer event streaming integrations that have the default message type messaging by using the ‘Create/Settings/Transfer settings from design/ES Integrations’. (#1485)
	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.
12	12
13		-==== Bug fixes ====
	10	+=====Minor changes=====
14	14
15		-* Design - Model Designer: Changed “align top“ and “align left“ to “align horizontally“ and “align vertically“ to be consistent with similar functionality in the Flow Designer. (#1611)
16		-* Create - Settings: The SOAP settings tab allows syncing the SOAP settings of systems in Design and Create. (#1569)
17		-* Create - Transformation: Updated the pattern used in dateTime transformations for the +HH:mm format. These used to fall back to +HHmm instead (dropping the ':'), this has now been resolved. (#1368)
18		-** Existing transformations are not automatically updated, but if you are using a custom XPath to do the transformation right now, you can now use the default functionality again.
19		-** The updated pattern (using XXX instead of ZZ) does not work on the previous generation runtime. If you are still using the previous generation runtime, and you have edited the specific part of the transformation, you can instead use the custom XPath where you use the pattern that is composed when using the dropdown menus, and replacing the XXX at the end with ZZ
	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)
20	20
	31	+====Bug fixes====
21	21
	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.
	37	+
	38	+====Remarks====
	39	+