Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 1.1
edited by eMagiz
on 2022/10/12 10:29
Change comment: There is no comment for this version
To version 129.1
edited by Erik Bakker
on 2023/07/17 15:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -185 - To determine
1 +201 - Be Informed
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Content
... ... @@ -2,60 +2,63 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that big development, we have finished our work on the Flow Designer which is the major part of this release. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one.
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.
6 6  
7 -==**Flow Designer V3**==
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]].
8 8  
9 -The new Flow Designer used in Create is released! This is a significant improvement in our iPaaS Portal that implements feedback of our users and helps to improve the overall experience. After several iterations of internal validations and testing sessions with end-users, we are releasing this feature to all users. Below are some key notes that are important to know and to consider.
10 -
11 -=== **Improvements** ===
12 -The new Flow Designer implements an approach whereby components can be dragged into the canvas without any configuration setting changed. The right hand panel contains a new section called Alerts that helps users to remove all alerts from the flow created. Such as missing configurations, channels or mismatches. All of these alerts need to be resolved so that a valid flow can be pushed to Deploy.
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.
13 13  
14 -[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 1.png]]
13 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
15 15  
16 -Furthermore, there is now a right hand panel to brings a few configuration more forward for users. In that panel you will find the following 4 tabs as described below. Furthermore, you can collapse the right hand panel to have more space to view/edit your flow.
17 -
18 -[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 2.png]]
19 -
20 -* **Alerts**
21 -In this section, all alerts are displayed organized by component. Alert text should be clear to understand the issue and the component can be opened from that same location.
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 -* **Resources**
24 -In this section, all resources are displayed used by the flow. Resources can be added and deleted from this section, as well as download and viewed. Generated resources such as transformations and definition are also vieweable from here. Use the option Show generated resources to explore these.
25 -
26 -* **Support objects**
27 -The support objects are no longer stored on the canvas, but displayed as a list in this tab. The interaction to add new support objects is also moved to this tab. Support objects can be edited from this tab as well. Please note that the interaction with the main canvas remains - selecting a support object will highlight the components in the canvas to illustrate where that support object is used.
18 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
28 28  
29 -* **Properties**
30 -The properties tab is also visible now and has been improved so that the values in Deploy can also be viewed. All values of all environments can be viewed - container level properties replicated are condensed into a single entry.
31 -
32 -=== **User interaction changes** ===
33 -There are some small changes to consider compared to the old flow designer. Please take a moment to read these:
34 -
35 -* Multiple select. This option is still available, but you have to click the shift button while drawing the rectangle that holds the objects to select
36 -* Live preview. When moving components around, a live preview of the flow is displayed so that alignment becomes easier
20 +== **Feedback Items** ==
37 37  
38 -
39 -== **Feedback items ** ==
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.
40 40  
41 -We have also solved other feedback items besides the key updates around functionality.
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.
42 42  
43 -//__Set runtime field as first selected field on property level__//
44 -With this change, the runtime is the first field selected when copying a property. This way it is easier to select another runtime and propagate that property to that runtime as well.
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.
45 45  
46 -[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 3.png]]
47 -
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.
48 48  
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 +
37 +== **Bug Fixes** ==
38 +
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.
41 +
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.
44 +
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.
47 +
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 +
49 49  == **Fancy Forum Answers** ==
50 50  
51 -As always, a gentle reminder to all 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:
53 +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:
52 52  
53 -* [[Excel Attachment in Mail to File>>https://my.emagiz.com/p/question/172825635703120756||target="blank"]]
54 -* [[Importing datapipeline store component Mendix to AWS Redshift failed>>https://my.emagiz.com/p/question/172825635703120551||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"]]
55 55  
56 56  == **Key takeaways** ==
57 57  
58 -Thanks to all that help build, 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:
59 59  
60 60  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
61 61  * If you have feedback or ideas for us, talk to the Platypus
... ... @@ -66,12 +66,11 @@
66 66  * Start thinking about major, minor, and patch
67 67  * Upgrade to the latest build number
68 68  * Keep making great integrations
69 -* Check out the new documentation portal.
70 70  
71 71  Let's stay in touch and till next time!
72 72  
73 73  {{info}}
74 -~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
76 +~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
75 75  
76 76  ~*~* Indicates a GEN3-only feature.
77 77  {{/info}})))((({{toc/}}))){{/container}}