Changes for page 272 - Driven Datamodel

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-196 - The Last Post
	1	+272 - Driven Datamodel

Content

...	...	@@ -1,35 +1,22 @@
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.
	1	+This release includes improvements to managing relationships at the data model level in Design. On top of that, various other user improvements are introduced. Furthermore, new users are created at the container level in preparation for our upcoming feature development.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.196 - The Last Post.WebHome||target= "blank"]].
	3	+Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.272 - Driven Datamodel.WebHome||target="blank"]].
4	4
5		-=====New features=====
	5	+==== New Features ====
	6	+* Design - Data model: On the data model level, we introduce two new context menu items allowing the user to add and manage relationships between entities. This option is available for all data model levels in Design.
	7	+** A new **Manage relationships** option is added to the context menu in the data model editor. When editing a data model, right-clicking an entity displays the **Manage relationships** action, which opens a pop-up to manage the relationships associated with the selected entity. The dialog allows relationships to be added, edited, or deleted.
	8	+** A new **Add relationship** option is added to the context menu in the data model editor. When editing a data model, right-clicking an entity displays the **Add relationship** action, which opens a pop-up to add a relationship to the selected entity.
	9	+* Deploy: A container-level user is introduced for each container in the deploy phase. This user will allow us to connect to other parts of our eMagiz infrastructure via a more fine-grained authorization procedure.
6	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.
	11	+==== Minor Changes ====
8	8
9		-=====Minor changes=====
	13	+* Create - Flow Designer: When saving a flow version, we determine whether related eMagiz resources (i.e., your message definition and transformation) require an update. If not, we do not regenerate them. As a result, saving flow versions has become faster, especially when you do not make changes to those resources. (#1645)
	14	+* Create - Flow Designer (OAuth Interceptor): Various help texts for this component have been updated to provide additional clarity on its functionality and more advanced configurations. (#1761)
10	10
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.
29	29
30		-====Bug fixes====
	17	+==== Bug fixes ====
31	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		-* 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.
	19	+* Design - API Catalog (Operation - Response): A user can define an HTTP range as the HTTP Status Code for an operation's response, as suggested by the help text. (#1764)
	20	+* Create - Overview: Number of errors in transformation is reflected correctly in offramp flow.
	21	+* Create - Flow Designer (SFTP/FTP Outbound Channel Adapters): Ensured that the correct help text is shown for the Temporary remote directory configuration option. (#1754)
	22	+* Deploy - Releases (Missing Properties): Nested emagiz properties are removed from the missing properties page. (#1803)