Skip to Content

Changes for page 184 - New Beginnings

Last modified by Carlijn Kokkeler on 2024/04/18 13:23
From version 1.1
edited by eMagiz
on 2022/09/13 12:58
Change comment: There is no comment for this version
To version 4.1
edited by eMagiz
on 2022/09/13 13:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,30 +2,68 @@
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. Unfortunately, as most of them are not yet ready to be shown to the public, we will keep the details under wrap for now. So for now, the surface is tranquil but soon waves of new features and functionality will arrive on shore!
5 +**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. We will release an important part of the Manage phase for this new architecture stack. In this release, all-new graphs and dashboards are released to the community. To use them (part of), your solution needs to run on the new architecture stack. On top of that, we have released a new cloud template for our single-lane environments that will unlock technical improvements in the future. Furthermore, we have several smaller feedback items to share!
6 6  
7 -==**Build 62** ==
8 -This release introduces build number 62 to our platform. This build number fixes the REST Template model component so that the option "Trust All" (in the advanced tab) can be used as expected. Now that this option works is operational, there is no need to upload a custom trust store anymore.
7 +==**Flow Designer V3**==
8 +
9 +The new Flow Designer used in Create is released! This is a significant improvement in our iPaaS Portal with the aim to update our technology stack but moreover to delight our users. After several iterations of internal validations and validation sessions with end-users, we have exposed this feature to all users. Below are some key notes that are important to know and to consider
9 9  
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.
13 +
14 +[[image:Main.Images.Release Blog.WebHome@FlowDesigner releaseblog 1.png]]
15 +
16 +Furthermore, there is now a right hand panel to brings a few configuration 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@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.
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.
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 +
33 +
10 10  == **Feedback items ** ==
11 11  
12 -Apart from the key updates around functionality, we have also solved other feedback items.
36 +We have also solved other feedback items besides the key updates around functionality.
13 13  
14 -//__Deletion prevention releases (GEN3)__//
15 -With this release, we have made several improvements on the deletion prevention of releases when running your GEN3 setup.
38 +//__Prevent creation of deploy package on auto-saved version__//
39 +With the launch of our new flow designer and due to possible issues when doing a complete model upgrade, we will now make sure that flows that have no definitive version, as the last version can never become a deploy package. On top of that, we provide you with the necessary feedback to take action when such an event occurs. Effectively it means that a new version needs to be pushed to Deploy including the updates made to the flow.
16 16  
41 +[[image:Main.Images.Release Blog.WebHome@183-release-blog--prevent-deploy-package-auto-saved-version.png]]
42 +
17 17  == **Bug Fixes** ==
18 18  
19 -//__Making sure that the user always ends up in the flow designer overview when opening a flow__//
20 -With this release, we have fixed a bug that caused you to end up in the wrong place when opening a flow in Create.
45 +//__Various updates when importing store items in Design, including a transformation__//
46 +With this release, we have made several improvements for importing store items in Design, including a transformation. This will further bolster our offering on this.
21 21  
48 +//__Unlock the capability to remove an event processor from Create of which an input or output topic is still used__//
49 +With this release, we have unlocked additional functionality under Create -> Settings that allows you to remove event processors of which an input or output topic is still used. This is on top of the standard delete behavior for event processors when both input and output topics can be removed.
50 +
51 +[[image:Main.Images.Release Blog.WebHome@183-release-blog--remove-event-processor-create-settings.png]]
52 +
53 +{{warning}}The same checks and balances apply when you try to remove such an event processor as before. This means that you first need to properly clean up, Manage and Deploy before being able to remove them correctly.{{/warning}}
54 +
22 22  == **Fancy Forum Answers** ==
23 23  
24 24  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:
25 25  
26 -* [[Max messages per poll SFTP inbound channel remote directory>>https://my.emagiz.com/p/question/172825635700363987||target="blank"]]
27 -* [[Duplicate queues on Production environment>>https://my.emagiz.com/p/question/172825635700364085||target="blank"]]
59 +* [[Can't retrieve message #1 in POP3Message.getContentStream>>https://my.emagiz.com/p/question/172825635703095096||target="blank"]]
60 +* [[html decoding>>https://my.emagiz.com/p/question/172825635703095028||target="blank"]]
61 +* [[pick a file on event>>https://my.emagiz.com/p/question/172825635703107755||target="blank"]]
28 28  
63 +== **Special Announcement** ==
64 +
65 +{{info}}In the upcoming release, a new version of the flow designer will be released to the community, so keep your eyes open.{{/info}}
66 +
29 29  == **Key takeaways** ==
30 30  
31 31  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: