Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
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 607.1
edited by CarlijnKokkeler
on 2024/07/16 14:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -189 - Private Eye
1 +225 - Pop-up Party
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,85 +1,96 @@
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!** 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.
6 +**Hi there, eMagiz developers!** In this release, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] will be available, including changes to our infinispan cache manager, SMB inbound channel adapter, and heap memory configuration. Moreover, we have made progress on our alerting improvement plans and have improved and added several pop-up screens. Find out all we released below!
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).
8 +== **Feedback Items** ==
9 +//__Alerting notification settings__//
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}}
11 +//__Process containers__//
12 +If a model does not have a license for a pattern, the model contact now has the option to delete the process container of that given pattern.
11 11  
12 -== **3rd generation runtime bolstering** ==
14 +//__Design settings__//
15 +When pressing Apply settings in Design Settings, a confirmation screen will now be shown to present the changes that will be taken into effect for each environment.
13 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.
17 +[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
15 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.
19 +//__Untested images__//
20 + A warning will be shown when a release is activated on **Production** with a new runtime image version which has not been tested on acceptance before.
21 +
22 +[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]]
23 +
24 +{{warn}}
25 +The following restrictions apply to this functionality:
26 +
27 +- The warning is
28 +{{/warn}}
18 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.
30 +//__Infinispan Cache Manager__//
31 +We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
32 +
33 +//__Infinispan Cache Manager error message__//
34 +We improved the error message when configuring an Infinispan Cache Manager with ‘TCP-ping’ transport type, when the list of peer hosts are passed in invalid format. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
21 21  
22 -//__Improved migration for JMS flows__//
23 -This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
36 +//__Flow bump__//
37 +When bumping a new version of the flows that are using a resource, you can specify which version type you want to create, Major, Minor or Patch version. You can also give more information in a description.
38 +
39 +[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]]
24 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}}
41 +//__Unused support objects__//
42 +Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
26 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.
44 +[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]]
45 +
46 +//__Deleting routes__//
47 +For clarity purposes, a confirmation pop-up will be shown when deleting routes.
29 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.
49 +[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
32 32  
33 -== **Feedback items ** ==
51 +//__Debug queue__//
52 +The 'Open debug queue' button in the queue browser enables the user to directly open the debug queue when it exists instead of having to search for it.
53 +
54 +[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]]
55 +
56 +== **Bug Fixes** ==
57 +//__Internal server error__//
58 +The internal server error pop-up is not received anymore when moving to Create in a model which has an Event Streaming license but is not using it.
34 34  
35 -We have also solved other feedback items besides the flow designer's critical updates.
60 +//__Namespace update__//
61 +Editing a namespace used in a message definition automatically updates the message definition & transformations.
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.
63 +//__Error pop-up__//
64 +We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows.
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.
66 +//__SMB inbound channel adapter__//
67 +The SMB inbound channel adapter failed to retrieve files when the remote directory pointed to a path with multiple directories in it, unless they were seperated with '}}' instead of '{{/'. This has been resolved, meaning that remote directories that contain multiple folders in its path can (and should) contain '/' again. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
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
69 +//__Heap memory__//
70 +The initial committed heap memory of runtimes has been lowered to better match actual usage. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
57 57  
58 -== **Bug fixes ** ==
72 +//__Classpath conflicts__//
73 +We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
59 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 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:
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"]]
79 +* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
80 +* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
81 +* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
70 70  
71 -== **Key takeaways** ==
83 +== **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:
85 +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:
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
77 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
89 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
78 78  * Clear your browser cache (Ctrl + Shift + Del)
79 -* Check out the release notes [here]
91 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
80 80  * Start thinking about how the license tracker can aid your development
81 81  * Start thinking about major, minor, and patch
82 -* Upgrade to the latest build number
83 83  * Keep making great integrations
84 84  
85 85  Let's stay in touch and till next time!
... ... @@ -87,6 +87,11 @@
87 87  {{info}}
88 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]]
89 89  
90 -~*~* Indicates a GEN3-only feature.
91 -{{/info}})))((({{toc/}}))){{/container}}
101 +{{/info}}
102 +)))
103 +
104 +(((
105 +{{toc/}}
106 +)))
92 92  {{/container}}
108 +{{/container}}