Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 1.1
edited by eMagiz
on 2022/10/12 10:29
Change comment: There is no comment for this version
To version 46.1
edited by Erik Bakker
on 2022/11/21 12:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -185 - To determine
1 +188 - Close Encounters
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Content
... ... @@ -2,60 +2,76 @@
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!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all the interactions with it. Furthermore, some smalller fixes and beta features will be released to the community.
6 6  
7 -==**Flow Designer V3**==
7 +== **3rd generation runtime bolstering** ==
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.
9 +This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy improvements we made to the 3rd generation runtime and the interaction with it.
13 13  
14 -[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 1.png]]
11 +//__Migration of JMS backup configuration improved__//
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.
13 +//__Prechecks on Upgrade option made available for 3rd generation runtime__//
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.
15 +//__Autogenerated exits can be deployed at once__//
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
17 +//__Code mapping functionality available on 3rd generation runtime__//
37 37  
38 -
19 +//__Improved the performance of deploying or activating a release__//
20 +
21 +//__Failing runtimes won't be restarted indefinetly anymore__//
22 +
23 +== **Exportable Release Audit** ~* ==
24 +
25 +On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
26 +
27 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
28 +
29 +{{warning}}Note that the following restrictions apply when exporting an audit document:
30 + * Changes made on definition and transformation level are **not** restored
31 + * You will **not** be able to restore to any flow version that was created before October 17th, 2022
32 + * 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
33 + * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
34 +
39 39  == **Feedback items ** ==
40 40  
41 -We have also solved other feedback items besides the key updates around functionality.
37 +We have also solved other feedback items besides the flow designer's critical updates.
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.
39 +//__Data Sink Refactor__//
40 +We have made some infrastructural changes to how data sink messages are stored and can be retrieved from the portal. Should there be changes needed on your end we will contact your seperately.
45 45  
46 -[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 3.png]]
47 -
42 +//__Improved naming convention on Store related pages__//
43 +We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
48 48  
45 +//__Press "Enter" to search on multiple pages__//
46 +In our Daemon Switch release we added functionality that allowed you to press **Enter** to search on the property overview page. With this release we have added this functionality to many more pages across the portal. The complete list is as follows
47 +
48 +* Deploy → Deployment Plan
49 +* Deploy → Properties → History
50 +* Deploy → User Management → Roles
51 +* Manage → Error Messages → Error Messages
52 +* Manage → Error Messages → Flows with Error Messages
53 +* Manage → Error Messages → Exceptions of Error Messages
54 +* Manage → Log Entries
55 +* Manage → Alerts
56 +* Manage → Triggers
57 +* Manage → Tags – Cant find (only Gen2)
58 +* Manage → Notifications
59 +* Manage → Notification Settings
60 +* Manage → Data Usage → History
61 +* Manage → Code mappings → All tabs
62 +
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:
65 +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"]]
67 +* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
68 +* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
69 +* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
70 +* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||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:
74 +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]]
89 +~* 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}}