Changes for page 272 - Driven Datamodel

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-272 - Driven Datamodel
	1	+252 - FrostLine

Author

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

Content

...	...	@@ -1,22 +1,16 @@
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.
	1	+This release features numerous updates to our platform, with a user-centric focus. This release, we once again embarked on our traditional Hackathon journey, focused on making the lives of our day-to-day platform users easier.
2	2
3		-Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.272 - Driven Datamodel.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.252 - Frostline 2.WebHome||target="blank"]].
4	4
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.
	5	+==== New features ====
10	10
11		-==== Minor Changes ====
	7	+* We have introduced the ability to move flows to another container, and be able to move their respective properties along side with them. *
12	12
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)
	9	+==== Minor changes ====
15	15
	11	+* Create - Transformation: Option to convert a string value to an enumeration by setting value mapping rules inside the “From string transformer“ attribute operation.
16	16
17	17	==== Bug fixes ====
18	18
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)
	15	+* Users belonging to Mendix systems will no longer be shown in Deploy > User management. All required information for these Mendix systems can be found in Deploy > Mendix connectors.
	16	+* Create - Transfer Integration: in case an integration is not a part of any release, it is possible to removed it from Create phase. (#800)