Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 532.1
edited by CarlijnKokkeler
on 2024/05/22 11:23
on 2024/05/22 11:23
Change comment:
There is no comment for this version
To version 42.1
edited by Erik Bakker
on 2022/11/07 16:43
on 2022/11/07 16:43
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 221 -Swift Shift1 +187 - Integration Sponsor - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,67 +1,74 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}} 3 -((( 2 +{{container layoutStyle="columns"}}((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** Inthis release,we improved theuser interfaceformanagingyour failoverandgroupingconfigurations andimprovedthemethod for addingnew attributes to data models.Nextto this, wehave improvedtheEvent Catalog overviewforCatalog users.Usingtheback buttononthe eMagizQ&A now also bringsyoubacktowhereyou werewithyour search query. We alsofixed some previous bugs, resultinginimproveddeletebehaviorfor containers and correctly generated scopeproperties.Lastly, there will notbea warning messageanymorewhen importinganXSDifthereis noselectedrequest or responsemessage definition.5 +**Hi there, eMagiz developers!** With this release we will release several impactful features and enablers to our community. Among others the next phase of the eMagiz Store will become publicly available. This means that you can now import data models and transformation on top of system messages in Design and accelerators in Create. Furthermore, we will launch a new Beta functionality through some of our clients that will enable you to restore your flow to a previous version. 7 7 8 -== **Feedback Items** == 9 -//__Q&A search__// 10 -Search results are now persisted when pressing the back button after opening a question in the community Q & A. 7 +== **Store - Next phase** == 11 11 12 -//__Event catalog__// 13 -For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation. 9 +This release will introduce the next phase of the Store to our whole community. With this new functionality you can now import data model messages (i.e. CDM, API Gateway Data model or Event Streaming data model) and transformations. This way connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce and others will become even easier. 14 14 15 -[[image:Main.Images.Release Blog.WebHome@release- 221-swift-shift-catalog-2.png]]11 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]] 16 16 17 -//__Attribute placements__// 18 -Some improvements regarding the placement of attributes have been done: 19 -* A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add a new attribute. 20 -* For system message definition, moving an attribute in the data model is now directly reflected in the tree structure as well. However for CDM, API Gateway, and EVS Data Model, moving an attribute will not be directly reflected in the tree structure. A pop-up confirmation, as shown below, will appear with respect to the type of message definition (i.e., system message or CDM) that the user is working with. 21 -* The pop-up that appears when rearranging attributes of an entity will result in a pop-up which text is conditional with respect to the messagetype. 13 +{{info}}For more information on the Store please check out this [[course>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]]. As a reminder you can find all documentation on all available Store content published by eMagiz [[here>>doc:Main.eMagiz Store.WebHome||target="blank"]].{{/info}} 22 22 23 - [[image:Main.Images.ReleaseBlog.WebHome@release-221-swift-shift-rearrange-attribute.png]]15 +== **New eMagiz Mendix Connector** == 24 24 25 -//__Failover & grouping__// 26 -Some improvements regarding the widgets for failover and grouping have been done: 27 -* When executing a start/stop action on a group, the description of the step now contains the name of the group. 28 -* When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group". 17 +With this release we introduce a new version of the eMagiz Mendix Connector. This version (6.0.0) will work both with the current runtime architecture and the new runtime architecture making the migration from the current runtime architecture to the new runtime architecture easier. The new version of the eMagiz Mendix Connector can be found in the Mendix Marketplace and in the eMagiz portal. 29 29 30 - [[image:Main.Images.ReleaseBlog.WebHome@release-221-start-stop-flows.png]]19 +{{info}}Migrating the runtime from the eMagiz portal works the same as for any other runtime. The migration path to migrate can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}} 31 31 32 - [[image:Main.Images.ReleaseBlog.WebHome@release-221-stop-groups.png]]21 +== **Flow version restore** ~* == 33 33 34 -== **Bug Fixes** == 35 -//__XSD import__// 36 -When importing an XSD to a new or empty response or request message, you will not receive a warning message anymore to avoid confusion. 23 +On top of that we will also launch a new Beta feature to the community that allows you to restore your flow to a previous version. This way you can quickly undo changes made that were incorrect. 37 37 38 -[[image:Main.Images.Release Blog.WebHome@release- 221-swift-shift-xsd.png]]25 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]] 39 39 40 -//__Container deletion__// 41 -The delete behaviour of containers in the container overview has been improved to allow deletion of unused containers with broken flows. 27 +{{warning}}Note, that the following restrictions apply when restoring to a previous version: 28 + * Changes made on definition and transformation level are **not** restored 29 + * You will **not** be able to restore to any flow version that was created before October 17th, 2022 30 + * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back 31 + * Your restored flow version will **not** be automatically committed to Deploy{{/warning}} 42 42 43 -//__Scope properties__// 44 -We fixed an issue where the generation of scope properties was incorrect for legacy API gateway runtimes using OAuth 2.0 security scheme. 33 +== **Feedback items ** == 45 45 35 +We have also solved other feedback items besides the flow designer's critical updates. 36 + 37 +//__Improved help texts Kafka component__// 38 +TBA 39 + 40 +//__Improved warning message when Message redelivery cannot be properly executed__// 41 +TBA 42 + 43 +//__See Flow Designer errors on the Create overview__// 44 +TBA 45 + 46 +== **Bug Fixes** == 47 + 48 +//__Update Swagger File when changing order of entities in gateway message__// 49 +TBA 50 + 46 46 == **Fancy Forum Answers** == 47 47 48 48 As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers: 49 49 50 -* [[OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]] 51 -* [[HTTP request without reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]] 52 -* [[All-entry API gateway is not starting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]] 55 +* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]] 56 +* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]] 57 +* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]] 58 +* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]] 53 53 54 -== **Key Takeaways** ==60 +== **Key takeaways** == 55 55 56 -Thanks to all whohelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:62 +Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: 57 57 58 58 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 59 59 * If you have feedback or ideas for us, talk to the Platypus 60 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 66 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 61 61 * Clear your browser cache (Ctrl + Shift + Del) 62 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]68 +* Check out the release notes [here] 63 63 * Start thinking about how the license tracker can aid your development 64 64 * Start thinking about major, minor, and patch 71 +* Upgrade to the latest build number 65 65 * Keep making great integrations 66 66 67 67 Let's stay in touch and till next time! ... ... @@ -69,11 +69,6 @@ 69 69 {{info}} 70 70 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 71 71 72 -{{/info}} 73 -))) 74 - 75 -((( 76 -{{toc/}} 77 -))) 79 +~*~* Indicates a GEN3-only feature. 80 +{{/info}})))((({{toc/}}))){{/container}} 78 78 {{/container}} 79 -{{/container}}