Skip to Content
Last modified by Carlijn Kokkeler on 2024/04/18 13:14
From version 1.1
edited by eMagiz
on 2022/10/12 10:29
Change comment: There is no comment for this version
To version 105.1
edited by Erik Bakker
on 2023/04/25 13:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -185 - To determine
1 +196 - The Last Post
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Content
... ... @@ -2,60 +2,70 @@
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 work hard on improving our next generation architecture and introduced the "live" mode within our flow testing functionality. Furthermore there are loads of smaller feedback items and bugs that have been resolved with this release. So without further ado let us dive into all we have to offer.
6 6  
7 -==**Flow Designer V3**==
7 +== **"Live" mode on flow testing** ==
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 +With this release we bring an improved version of the flow testing functionality. As of now you will have the option to switch between "live" and "mock" mode will running a flow test. The "mock" mode is the mode you are used to from us. In this mode all external communication is mocked by the system and only the functional process can be tested.
13 13  
14 -[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 1.png]]
11 +By switching to "live" mode you can not only test the functional process but also the communication to the external system. You can do so by entering the "edit" mode of the flow test and toggle between "mock" and "live" mode. When doing so eMagiz will show you the following pop-up stressing the consequences of your actions.
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 +[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-pop-up.png]]
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 +Once confirmed you will see that the user interface now indicates that the endpoint is in "live" mode.
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 +[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-result.png]]
37 37  
38 -
19 +== **3rd generation improvements** ==
20 +
21 +//__Event Streaming statistics completion__//
22 +In this release, we have updated the retrieval of data to ensure that for all models, all environments and all topics this data can be shown to the user so they can properly monitor the environment.
23 +
24 +//__Deployments on next generation architecture__//
25 +This release fixes several smaller bugs and adds several improvements to the deployment process of the next generation architecture.
26 +
27 +//__Clean queues option__//
28 +This release introduces an option for **admins** to clean queues that remained after a migration towards the next generation runtime architecture. This will make the overview of which queues are "problematic" a much more realistic overview.
29 +
39 39  == **Feedback items ** ==
40 40  
41 -We have also solved other feedback items besides the key updates around functionality.
32 +//__On-premise containers are started upon slot wakeup__//
33 +With this release, we have added additional functionality to models running in the next generation runtime architecture. With this improvement all on-premise containers are stopped when the cloud slot goes to sleep and are woken up once the slot is woken up in the morning.
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.
35 +//__See Fixed IP in Deploy Architecture__//
36 +To improve our cloud offerings' we now display the configured fixed IP on your cloud connectors. This will unlock you as the user to easily communicate this value to external parties without involvement on our end.
45 45  
46 -[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 3.png]]
47 -
38 +//__Resource path is shown to the user__//
39 +You can now, without downloading, see the resource path of a resource by viewing the metadata of the resource. You can do so by pressing the "eye" icon to view this information.
48 48  
41 +//__Flow designer improvements__//
42 +With this release various improvements have been made to the flow designer. Among others we have improved the overview of what an "unused resource" is. You now have the option to define certain resources that are used but cannot be auto-detected by eMagiz to be an "used" resource to avoid confusion.
43 +
44 +//__Improved capabilities of a company contact__//
45 +With this release we have improved the capabilities of a company contact. As of now you can also add users to models belonging to subcompanies below your the company to which you are the company contact.
46 +
47 +== **Bug fixes ** ==
48 +
49 +//__Optional API parameters are handled correctly__//
50 +Currently, eMagiz would create the wrong expression for handling optional API parameters. With this release we have improved the expression in such a way that all optional parameters are handled correctly out of the box.
51 +
52 +//__Without CDM rights nothing related to any data model can be edited anymore__//
53 +With this release, we have made sure that nothing related to any data model can be edited without having the proper rights.
54 +
55 +//__Improved sorting of Design and Deploy archticture__//
56 +With this release, we now ensure that both Design and Deploy architecture are sorted in the same manner to avoid confusion when quickly switching between both views.
57 +
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:
60 +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"]]
62 +* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
63 +* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]
64 +* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||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:
68 +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]]
83 +~* 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}}