Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 2.1
edited by eMagiz
on 2022/10/12 10:50
Change comment: There is no comment for this version
To version 269.1
edited by Carlijn Kokkeler
on 2023/12/04 13:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -185 - To determine
1 +209 - Deployment Delights
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,53 +1,38 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
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, we have made several small updates as this release contained a complete revamp of the Manage phase. 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.
6 +**Hi there, eMagiz developers!** We have...
6 6  
7 -==**Audit trail User Management**==
8 +== **Release Maintenance** ==
8 8  
9 -
10 -==**Next Generation Monitoring & Alerting engine**==
11 -In the recent sprints, we have completed our alerting & monitoring engine for our new runtime architecture. Effectively that means that we are now used State Generation components inside this architecture, and all error messages, runtime metrics and logging are now passing through this engine. All of our regular Manage phase screens have been updated to point to the new storage locations. In the Manage phase we have introduced proper means to toggle between data of the current and the new monitoring stack (transition to the new runtime can be a runtime by runtime approach). We have already released and described the new Manage phase graphs in [[Release blog 183>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Release%20Blogs/Rainbow%20World||target="blank"]]
12 -
13 -=== **Improvements** ===
14 -
15 -* Performance Deployment plan
16 -When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU. This has been improved with this release.
17 -
18 -* Flow Designer updates
19 -We have added an icon to identify a Queued channel which are mostly found in entry flows that use the h2 bridge. Furthermore, the display of wiretaps and annotations can be copied now. Next to that some small UI improvements where made.
20 -
21 -
22 -
23 -
24 -[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 1.png]]
25 25  
26 -
27 -== **Feedback items ** ==
28 28  
29 -We have also solved other feedback items besides the key updates around functionality.
30 30  
31 -//__Set runtime field as first selected field on property level__//
32 -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.
33 33  
34 -[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 3.png]]
35 -
14 +== **Feedback Items** ==
36 36  
16 +//__Harbor port change__//
17 +
18 +
19 +== **Bug Fixes** ==
20 +
21 +
22 +
37 37  == **Fancy Forum Answers** ==
38 38  
39 -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 +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:
40 40  
41 -* [[Start runtime via a delayed start in a Linux environment?>https://my.emagiz.com/p/question/172825635703146181||target="blank"]]
42 -* [[Failed to create sFTP session: Het systeem kan het opgegeven pad niet vinden>>https://my.emagiz.com/p/question/172825635703146327||target="blank"]]
27 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
43 43  
44 44  == **Key takeaways** ==
45 45  
46 -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:
31 +Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
47 47  
48 48  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
49 49  * If you have feedback or ideas for us, talk to the Platypus
50 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
35 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
51 51  * Clear your browser cache (Ctrl + Shift + Del)
52 52  * Check out the release notes [here]
53 53  * Start thinking about how the license tracker can aid your development
... ... @@ -54,13 +54,18 @@
54 54  * Start thinking about major, minor, and patch
55 55  * Upgrade to the latest build number
56 56  * Keep making great integrations
57 -* Check out the new documentation portal.
58 58  
59 59  Let's stay in touch and till next time!
60 60  
61 61  {{info}}
62 -~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
46 +~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
63 63  
64 -~*~* Indicates a GEN3-only feature.
65 -{{/info}})))((({{toc/}}))){{/container}}
48 +~*~* Indicates a next-generation-architecture only feature.
49 +{{/info}}
50 +)))
51 +
52 +(((
53 +{{toc/}}
54 +)))
66 66  {{/container}}
56 +{{/container}}