Skip to Content

Changes for page 182 - Tranquil Surface

Last modified by Carlijn Kokkeler on 2024/04/18 13:25
From version 23.1
edited by eMagiz
on 2022/08/18 16:37
Change comment: There is no comment for this version
To version 10.1
edited by Erik Bakker
on 2022/07/05 10:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -182 - Tranquil Surface
1 +179 - Friction Hunters
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Content
... ... @@ -1,36 +1,42 @@
1 -{{container}}
2 -{{container layoutStyle="columns"}}(((
1 +{{container}}{{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!
4 +**Hi there, eMagiz developers!** In the last couple of weeks, we have worked on various main platform features. Sadly they are not yet ready enough to release to you guys. We did, however, improve the platform in different more minor ways. Among these improvements, we have improved the speed of handling error messages and creating models by hand. Furthermore, we have several more minor improvements and bug fixes for you. So let us dive into all that we have to offer this time around!
6 6  
7 -== ** Build 62** ==
8 -This release also 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 as expected, there is no need to upload a custom trust store anymore.
6 +== **Infrastructure Update** ==
7 +
8 +As you might already have seen via the notifications sent from our status page (https://status.emagiz.com), we will update our infrastructure with our upcoming release. This will lay the foundation for more infrastructural changes in our future. For specific information, please check out the notifications via our status page.
9 +
10 +[[image:Main.Images.Release Blog.WebHome@178-release-blog-1.jpg]]
11 +
12 +== **Bug Fixes** ==
13 +
14 +//__Update eMagiz Slot Status does not lead to logging errors__//
15 +With this release, we have made several improvements in retrieving the eMagiz Slot Status when a user executes an action on the eMagiz Cloud. These improvements will resolve logging errors within the platform.
9 9  
10 10  == **Feedback items ** ==
11 11  
12 12  Apart from the key updates around functionality, we have also solved other feedback items.
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.
21 +//__Notify model owner when mails are sent to deactivated users__//
22 +We will notify model owners via mail that their alerting sends emails to deactivated users within the platform with this release. Furthermore, once we encounter a notification setting in which a deactivated user is part of the recipients, we will remove the user from the notifications (if possible).
16 16  
17 -== **Bug Fixes** ==
24 +//__Updated infographic Capture__//
25 +As of now, we have updated the infographic on the Capture phase to incorporate the new look and feel and explain the updated functionality in Capture.
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.
21 -
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"]]
31 +* [[Access to local files>>https://my.emagiz.com/p/question/172825635700363485||target="blank"]]
32 +* [[Oauth database not updated>>https://my.emagiz.com/p/question/172825635700363386||target="blank"]]
33 +* [[Input/Output error>>https://my.emagiz.com/p/question/172825635700363385||target="blank"]]
28 28  
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:
32 32  
33 -* If you have questions surrounding our Program Increment Planning, please get in touch with
39 +* If you have questions surrounding our Program Increment Planning, please get in touch with
34 34  * If you have feedback or ideas for us, talk to the Platypus
35 35  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
36 36  * Clear your browser cache (Ctrl + Shift + Del)
... ... @@ -39,7 +39,6 @@
39 39  * Start thinking about major, minor, and patch
40 40  * Upgrade to the latest build number
41 41  * Keep making great integrations
42 -* Check out the new documentation portal.
43 43  
44 44  Let's stay in touch and till next time!
45 45  
... ... @@ -47,5 +47,4 @@
47 47  ~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
48 48  
49 49  ~*~* Indicates a GEN3-only feature.
50 -{{/info}})))((({{toc/}}))){{/container}}
51 -{{/container}}
55 +{{/info}})))((({{toc/}}))){{/container}}{{/container}}