Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 533.1
edited by CarlijnKokkeler
on 2024/05/29 10:51
on 2024/05/29 10:51
Change comment:
There is no comment for this version
To version 129.1
edited by Erik Bakker
on 2023/07/17 15:10
on 2023/07/17 15:10
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 -2 21 -SwiftShift1 +201 - Be Informed - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,67 +1,73 @@ 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!** In th is release,weimprovetheuserinterfaceformanagingyour failoverand groupingconfigurationsand improved the method for addingnewattributestodata models. Nexttothis, wehave improvedthe Event Catalogoverview for Catalog users.Usingthe back buttononthe eMagiz Q&A now also brings you backtowhereyou werewith yoursearch query. Wealsofixedsomepreviousbugs,resultingin improved delete behaviorforcontainersandcorrectly generated scopeproperties.Lastly, there will notbe a warning messageanymore when importingan XSD ifthere is noselected requestor response message definition.5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on planning the upcoming Q and finishing up features of the last Q. More on that later. On top of that we have several smaller items as a result of our hackathon efforts to present to you. 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 +== **Announcement - Release Properties** == 8 +As of the next release (202) we will introduce a completely new way of handling properties for all our clients. In the upcoming weeks we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance please contact us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 11 11 12 - //__Eventcatalog__//13 - ForCatalogusers,we havesignificantlyimprovedtheEventCatalog overviewbyintroducingamuch simplerlayout for easier navigation.10 +== ** Deploy Architecture - Apply To Environment improvements ** == 11 +As of this release we will show you a list of all change that are about to be changed once you press "Apply to environment" in Deploy Architecture. This will ensure that it becomes clearer for users, especially those working together in teams, what will change when pressing this button. 14 14 15 -[[image:Main.Images.Release Blog.WebHome@release- 221-swift-shift-catalog-2.png]]13 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.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. 15 +== ** Breadcrumb navigation in eMagiz ** == 16 +With this release we introduce the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed, and have impact, in the Create phase when you are checking out your transformation or system message on flow level. Apart from there the navigation is implemented consistently across the portal for a unified look and feel. 22 22 23 -[[image:Main.Images.Release Blog.WebHome@release- 221-swift-shift-rearrange-attribute.png]]18 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]] 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". 20 +== **Feedback Items** == 29 29 30 -[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]] 22 +//__Improved layout of catalog page in Design__// 23 +We have improved the layout of the API Catalog overview in Design for our API Gateway users. Among others, we have introduced a scrollbar to get a better overview when having several operations. 31 31 32 -[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]] 25 +//__Improved layout of "Edit integration" pop-up for API Gateway integrations__// 26 +As of now the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration. 33 33 28 +//__Additional help texts on Design Architecture__// 29 +We have improved the help texts in Design Archicture in relation to the Event Streaming topic storage overview. 30 + 31 +//__Improved Audit Trail on several places__// 32 +In several places in the portal we have improved the audit trail to better specify who changed what at which point in time. 33 + 34 +//__Removed the erroneous alert on message mapping when having a passthrough API__// 35 +This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API. 36 + 34 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. 37 37 38 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]] 39 +//__Avoid clicking on other components while deleting another__// 40 +To avoid unexpected behavior we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer. 39 39 40 -//__ Containerdeletion__//41 - Thedelete behaviourofcontainersin thecontaineroverview hasbeenimproved toallow deletion ofunusedcontainerswith broken flows.42 +//__Improved validation feedback in migrating to the next-generation architecture__// 43 +We have improved several things with regards to the validation feedback when migrating to the next-generation architecture. 42 42 43 -//__ Scopeproperties__//44 - We fixedanissuewherethegeneration ofscopepropertieswasincorrectforlegacyAPI gateway runtimesusingOAuth2.0 securityscheme.45 +//__Make sure that user credentials can be viewed with view rights__// 46 +This release makes sure that the user credentials in Deploy can be viewed with view rights and not only when having edit rights. 45 45 48 +//__Refresh behavior within the deployment plan is fixed__// 49 +This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute. 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 -* [[ OAuth2.0,403Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]]51 -* [[ HTTPrequestwithout reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]]52 -* [[ All-entryAPIgatewayis not starting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]]55 +* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]] 56 +* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]] 57 +* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]] 53 53 54 -== **Key Takeaways** ==59 +== **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:61 +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. 65 +* 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"]]67 +* 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 70 +* 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 -))) 78 +~*~* Indicates a GEN3-only feature. 79 +{{/info}})))((({{toc/}}))){{/container}} 78 78 {{/container}} 79 -{{/container}}