Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 56.1
edited by Erik Bakker
on 2022/12/06 14:58
Change comment: There is no comment for this version
To version 2.1
edited by eMagiz
on 2022/10/12 10:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -189 - Private Eye
1 +185 - To determine
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.eMagiz
Content
... ... @@ -2,75 +2,48 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** Our release of the Private store functionality characterizes this release. This functionality allows some users to export content to a private store that is only accessible within the company and could be published to the public store of eMagiz. On top of that, we resolved some of the limitations on the 3rd generation runtime. Furthermore, some minor fixes and beta features will be released to the community.
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 6  
7 -== **Private Store** ==
8 -On top of our general store, in which eMagiz currently publishes Store content relevant to both the Design and Create phases of eMagiz, we have added the private store functionality. This store works precisely the same as the general store. However, only users belonging to the same company as the exporter can import the store content (after it is approved).
7 +==**Audit trail User Management**==
9 9  
10 -{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/warning}}
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]]
11 11  
12 -== **3rd generation runtime bolstering** ==
13 -
14 -This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
15 -
16 -//__SOAP and REST web services migration including splitting them__//
17 -With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime and at the same time you can directly split the all-entry to get rid of that construction alltogether. A specific migration path for this will be published in the documentation portal.
18 -
19 -//__Changing SSL settings for 3rd generation runtime models works__//
20 -As with the current runtime architecture, you can now also change the SSL settings if needed for a model running in the 3rd generation runtime.
21 -
22 -//__Improved migration for JMS flows__//
23 -This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
24 -
25 -{{warning}}If you already migrated your JMS flow you should execute a "Reset" action on JMS level to get these changes in your model{{/warning}}
26 -
27 -//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
28 -As of this release, you cannot add debug components anymore on a flow that is already migrated to the 3rd generation runtime. This is because this functionality will not work in the 3rd generation runtime and would break your flow.
29 -
30 -//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
31 -We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
32 -
26 +
33 33  == **Feedback items ** ==
34 34  
35 -We have also solved other feedback items besides the flow designer's critical updates.
29 +We have also solved other feedback items besides the key updates around functionality.
36 36  
37 -//__Improved naming convention on Store related pages__//
38 -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.
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.
39 39  
40 -//__Press "Enter" to search on multiple pages__//
41 -In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows.
34 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 3.png]]
35 +
42 42  
43 -* Deploy → Deployment Plan
44 -* Deploy → Properties → History
45 -* Deploy → User Management → Roles
46 -* Manage → Error Messages → Error Messages
47 -* Manage → Error Messages → Flows with Error Messages
48 -* Manage → Error Messages → Exceptions of Error Messages
49 -* Manage → Log Entries
50 -* Manage → Alerts
51 -* Manage → Triggers
52 -* Manage → Tags – Cant find (only Gen2)
53 -* Manage → Notifications
54 -* Manage → Notification Settings
55 -* Manage → Data Usage → History
56 -* Manage → Code mappings → All tabs
57 -
58 -== **Bug fixes ** ==
59 -
60 -//__Loading problems of Deployment plan execution overview__//
61 -We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases.
62 -
63 63  == **Fancy Forum Answers** ==
64 64  
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:
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:
66 66  
67 -* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
68 -* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
69 -* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
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"]]
70 70  
71 71  == **Key takeaways** ==
72 72  
73 -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:
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:
74 74  
75 75  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
76 76  * If you have feedback or ideas for us, talk to the Platypus
... ... @@ -81,11 +81,12 @@
81 81  * Start thinking about major, minor, and patch
82 82  * Upgrade to the latest build number
83 83  * Keep making great integrations
57 +* Check out the new documentation portal.
84 84  
85 85  Let's stay in touch and till next time!
86 86  
87 87  {{info}}
88 -~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
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]]
89 89  
90 90  ~*~* Indicates a GEN3-only feature.
91 91  {{/info}})))((({{toc/}}))){{/container}}