Changes for page 204 - Found It

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-201 - Be Informed
	1	+196 - The Last Post

Content

...	...	@@ -1,30 +1,35 @@
1		-In the last sprint cycle, we focused on planning ahead, finishing up and working on the Hackathon to fix several smaller items.
	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>>Main.Release Information.Release Blogs.201 - Be Informed.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, the Flow Testing allowed to test eMagiz flows by defining a testing point on the start (and end) point(s), run them and compare the actual and expected messages. In this release, “Live Mode Testing” is introduced, making it possible to test communication with an actual "live" endpoint. As a result a “HTTP outbound gateway” can be set in “Live Mode”. When you do this, the HTTP outbound gateway will send its HTTP request to the actual 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		-* Portal - Menu: the back button is changed to have text so it shows clearer the navigation target. (#949)
8		-* Design-Architecture: Topic Storage detail page contains help text. (#994)
9		-* Design - API Endpoint Specification: Improved UI and added independent scroll functionality. (#832)
10		-* Design - API Gateway: Small styling improvements to the edit integration page. (#954)
11		-* Create - Flow Designer: When deleting one or multiple components, you will not be able to change the selection before confirming or cancelling the delete action. (#969)
12		-* Create - Migrate to 3rd Generation: In the event one or more flows break during migration, a popup will inform the fows containing errors after migration is finished. (#983)
13		-* Deploy-User management: The user that makes a change is recorded in history instead of the user that applies to environment. (#979)
14		-* Deploy-Architecture: Upon pressing the button “Apply to environment”, a confirmation page is shown. Here all changes made in the portal that will have an effect in your running environment are listed. These changes can be applied to environment or reverted. (#828)
15		-** Changes made in Deploy Architecture with an effect to your running environment will only be listed when they are made after this release.
16		-** Changes with a direct effect will not be listed (for example restarting a machine).
	11	+* 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.
	12	+* 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.
	13	+* 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.
	14	+* 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.
	15	+* 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.
	16	+* Create - Flow designer: Model resources tab removed on resources page when adding an resource to a validating filter.
	17	+* Create - Flow designer: Improve responsiveness of resources tab at right panel.
	18	+* Create - 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.
	19	+* 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.
	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 in order to obtain its name
	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’)
	25	+* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are ran.
	26	+* Manage - Explore: A new button to delete queue is added. This button is only visible for authorized personnel.
	27	+* Administration -User management: Company contact can edit permissions of models that fall under child companies.
	28	+* Administration - Overview: Contracts page removed.
17	17
18	18	====Bug fixes====
19	19
20		-* Design - Solutions: We fixed an issue that a message mapping error is displayed despite having a passthrough API gateway. (#935)
21		-* Design - Settings: The full length of the contract number can now be registered. (#958)
22		-* Create - Migrate to 3rd Generation: Components used in Gen 2 flows that can be used in Gen3 will not block migration. (#982)
23		-* Deploy - Deployment plan: We fixed an issue that the list of installing flows did not show in the left pane when you deploy a release version to install/start/stop some flows into you runtimes. (#990)
24		-* Deploy - User Management: As a user with view-only rights in Deploy/User management, you can now double click on a user to open its details. (#972)
25		-* Manage - Manage Dashboards: The screen loading speed is significantly improved for all models. This is most noticeable for larger models. (#964)
26		-
27		-=====Infra and image changes=====
28		-
29		-* Changed the endpoint that is used for sending errormessages to the eMagiz Control Tower.
30		-* Updated the Spring version of the gateway supporting deploy and manage phase operations.
	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	+* 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.
	35	+* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs.