Changes for page 208 - Controlled State

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-208 - Controlled State
	1	+196 - The Last Post

Author

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

Content

...	...	@@ -1,23 +1,35 @@
1		-In the last sprint cycle, we focused on providing users with a monitoring functionality for the state generation components. On top of that, we also made several improvements on the components interfacing the users to improve the user experience aspect of our platform. Moreover, we made some bug fixes and improvements on releases in Deploy and monitoring in Manage.
	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.208 - Controlled State .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	+=====New features=====
	6	+
	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	+
5	5	=====Minor changes=====
6	6
7		-* Design - Message Mapping: The button 'Import from Store' will directly open the store.
8		-* Create - Flow Designer: Input fields for XPath expressions have been made wider and capable of expanding to facilitate longer inputs. (#822)
9		-* Create - Flow Designer: Small styling changes and bugfixes have been implemented for edge-cases during editing channels in the Flow Designer.
10		-* Deploy - Releases: During removing a release, users will be informed about the environments and the runtimes in which the release under deletion is running.(#1060)
11		-* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
12		-* Deploy - Deployment: The preparing step of the release at the begining of the deployment is now faster due to the improved process in building the images.
13		-* Manage - Monitoring: There is a new page called the "State generation statistics" that is located right under the Topic statistics navigation menu, which is only shown and accessible for models that has the add-on license for state generation.
14		-* Manage - Error messages & Log entries: Searching on entries now supports phrase matching, meaning that users can search entries based on phrases containing two or more words and entries with distances of 2 or incomplete search phrase.
15		-* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
16		-* All - Toggles: We updated all instances of the toggle switch in the platform due to the latest eMagiz Design System module implementation in our platform.
17		-* All - Error Channel: Added a migration step in Gen3 migration, we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
	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: We fixed an issue that the deployment plan got stuck or stopped randomly sometimes.
22		-* Deploy - Deployment: We resolved an issue where sometimes older containers get deployed, while eMagiz shows the new containers are deployed.
23		-* Manage - Monitoring: Improved message processing in infra components that should reduce the occurance of log messages failed to be sent in Gen3 models.
	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)