Wiki source code of 272 - Driven Datamodel
Last modified by Erik Bakker on 2026/07/14 13:05
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{container}} | ||
| 2 | {{container layoutStyle="columns"}} | ||
| 3 | ((( | ||
| 4 | [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] | ||
| 5 | |||
| 6 | **Hi there, eMagiz developers!** 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. | ||
| 7 | |||
| 8 | |||
| 9 | == **Managing Data Models - Alternatively** == | ||
| 10 | |||
| 11 | With this release, we introduce a new alternative way to manage your data models in Design, focused on creating relationships between entities in the data model. We have seen that, especially for larger models, managing relationships is time-consuming. As a result, we have developed this alternative way of managing those relationships. | ||
| 12 | |||
| 13 | {{info}} | ||
| 14 | The following applies to this functionality: | ||
| 15 | * 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. This includes the following: | ||
| 16 | ** 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. | ||
| 17 | ** 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. | ||
| 18 | {{/info}} | ||
| 19 | |||
| 20 | [[image:Main.Images.Release Blog.WebHome@release-272-alternative-way-managing-relationships.png]] | ||
| 21 | |||
| 22 | == **Major Runtime Upgrade - Pre-Announcement** == | ||
| 23 | |||
| 24 | We are currently hard at work updating our underlying runtime code to the latest major version, including various changes. On this [[page>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Lifecycle Management.advanced-lifecycle-management-impact-of-upcoming-runtime-image.WebHome||target="blank"]] we will keep you informed starting now on which of these changes will impact you. Please pay attention to this page in the coming weeks to ensure you are ready the moment we introduce this new runtime image. More details will follow! | ||
| 25 | |||
| 26 | == **New Features** == | ||
| 27 | |||
| 28 | //__Deploy - Container level users__// | ||
| 29 | 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. | ||
| 30 | |||
| 31 | == **Minor Changes** == | ||
| 32 | |||
| 33 | //__Create - Flow Designer__// | ||
| 34 | |||
| 35 | * 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. | ||
| 36 | * Various help texts for this component have been updated to provide additional clarity on its functionality and more advanced configurations. | ||
| 37 | |||
| 38 | == **Bug Fixes** == | ||
| 39 | |||
| 40 | //__Design - API Catalog__// | ||
| 41 | A user can define an HTTP range as the HTTP Status Code for an operation's response, as suggested by the help text. | ||
| 42 | |||
| 43 | //__Create - Overview__// | ||
| 44 | The number of errors in the transformation is reflected correctly in the offramp flow. | ||
| 45 | |||
| 46 | //__Create - Flow Designer__// | ||
| 47 | Ensured that the correct help text is shown for the Temporary remote directory configuration option. | ||
| 48 | |||
| 49 | //__Deploy - Releases__// | ||
| 50 | Nested emagiz properties are removed from the missing properties page. | ||
| 51 | |||
| 52 | == **Fancy Forum Answers** == | ||
| 53 | |||
| 54 | As always, this is a gentle reminder to ask questions via the Q&A forum in the eMagiz iPaaS portal. This way, we can all benefit from the community's knowledge. | ||
| 55 | |||
| 56 | == **Key Takeaways** == | ||
| 57 | |||
| 58 | Thanks to all who helped build the product and those who tested and provided feedback to improve it. To end this post, here are some key takeaways for you: | ||
| 59 | |||
| 60 | * If you have questions surrounding our roadmap, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 61 | * If you have feedback or ideas for us, talk to the Platypus | ||
| 62 | * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. | ||
| 63 | * Clear your browser cache (Ctrl + Shift + Del) | ||
| 64 | * Check out the release notes [[here>>doc:Main.Release Information.Portal.272 - Driven Datamodel.WebHome||target="blank"]] | ||
| 65 | * Don't forget to update your environment template before the deadline | ||
| 66 | * Keep making great integrations | ||
| 67 | |||
| 68 | Let's stay in touch and till next time! | ||
| 69 | |||
| 70 | {{info}} | ||
| 71 | ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| 72 | |||
| 73 | {{/info}} | ||
| 74 | ))) | ||
| 75 | |||
| 76 | ((( | ||
| 77 | {{toc/}} | ||
| 78 | ))) | ||
| 79 | {{/container}} | ||
| 80 | {{/container}} |