Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 57.1
edited by Erik Bakker
on 2022/12/06 15:57
Change comment: There is no comment for this version
To version 603.1
edited by Erik Bakker
on 2024/07/16 14:38
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
Content
... ... @@ -1,87 +1,90 @@
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 (LINK) 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. At the same time, you can directly split the all-entry to eliminate that construction. 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]]
18 18  
19 -//__Changing SSL settings for 3rd generation runtime models works__//
20 -As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
24 +//__Infinispan Cache Manager__//
25 +We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK is available.
26 +
27 +//__Infinispan Cache Manager error message__//
28 +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 LINK 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.
30 +//__Flow bump__//
31 +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.
32 +
33 +[[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 the JMS level to get these changes in your model{{/warning}}
35 +//__Unused support objects__//
36 +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 can no longer add debug components on a flow already migrated to the 3rd generation runtime. This functionality will not work in the 3rd generation runtime and would break your flow.
38 +[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]]
39 +
40 +//__Deleting routes__//
41 +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.
43 +[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
32 32  
33 -//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
34 -With this release, the properties generated for Event Streaming flows running in the 3rd generation runtime are configured correctly to mimic the ones in the image.
45 +//__Debug queue__//
46 +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.
47 +
48 +[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]]
49 +
50 +== **Bug Fixes** ==
51 +//__Internal server error__//
52 +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.
35 35  
36 -//__Added "Reset" functionality__//
37 -With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime.
54 +//__Namespace update__//
55 +Editing a namespace used in a message definition automatically updates the message definition & transformations.
38 38  
39 -== **Feedback items ** ==
57 +//__Error pop-up__//
58 +We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows.
40 40  
41 -We have also solved other feedback items besides the flow designer's critical updates.
60 +//__SMB inbound channel adapter__//
61 +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 LINK is available.
42 42  
43 -//__Improved naming convention on Store related pages__//
44 -We have improved various display names using the merge functionality within our store offering.
63 +//__Heap memory__//
64 +The initial committed heap memory of runtimes has been lowered to better match actual usage. For this, a new runtime image LINK is available.
45 45  
46 -//__Update security protocols for our internal architecture__//
47 -Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
66 +//__Classpath conflicts__//
67 +We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images.
48 48  
49 -//__Improved read-only description for "if exists" constructions in Transformations__//
50 -To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does.
51 -
52 -
53 -== **Bug fixes ** ==
54 -
55 -//__Decent validation feedback when not filling in the property value__//
56 -We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
57 -
58 -//__Incorrect resource locations__//
59 -We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
60 -
61 -//__Apply to environment in User Management performance improvement__//
62 -We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
63 -
64 64  == **Fancy Forum Answers** ==
65 65  
66 66  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:
67 67  
68 -* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
69 -* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
70 -* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
71 -* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
73 +* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
74 +* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
75 +* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
72 72  
73 -== **Key takeaways** ==
77 +== **Key Takeaways** ==
74 74  
75 -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:
79 +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:
76 76  
77 77  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
78 78  * If you have feedback or ideas for us, talk to the Platypus
79 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
83 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
80 80  * Clear your browser cache (Ctrl + Shift + Del)
81 -* Check out the release notes [here]
85 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
82 82  * Start thinking about how the license tracker can aid your development
83 83  * Start thinking about major, minor, and patch
84 -* Upgrade to the latest build number
85 85  * Keep making great integrations
86 86  
87 87  Let's stay in touch and till next time!
... ... @@ -89,6 +89,11 @@
89 89  {{info}}
90 90  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
91 91  
92 -~*~* Indicates a GEN3-only feature.
93 -{{/info}})))((({{toc/}}))){{/container}}
95 +{{/info}}
96 +)))
97 +
98 +(((
99 +{{toc/}}
100 +)))
94 94  {{/container}}
102 +{{/container}}