Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 477.1
edited by CarlijnKokkeler
on 2024/04/23 13:21
Change comment: There is no comment for this version
To version 57.1
edited by Erik Bakker
on 2022/12/06 15:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -219 - Creation Carousel
1 +189 - Private Eye
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,72 +1,87 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release, we introduce new environment templates for Docker single and double lane. Moreover, we have a new version of our eMagiz Mendix connector available, that will support Mendix version 10 and higher. Furthermore, the path length in OpenAPI spec imports has been increased to a maximum of 300 characters. Lastly, we have done many bug fixes, one of which will ensure that SFTP sessions will be closed again after completion. For this fix, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been published.
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.
7 7  
8 -== **Environment Template R13 Docker - Single Lane** ==
9 -This release introduces a new non-service affecting environment template for all our customers running in a single-lane setup. This environment template updates the on-premise machine agents. The complete release notes on the environment template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Single Lane.WebHome||target="blank"]].
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).
10 10  
11 -== **Environment Template R15 Docker - Double Lane** ==
12 -This release introduces a new non-service affecting environment template for all our customers running in a double-lane setup. This environment template updates the on-premise machine agents. The complete release notes on the environment template can be found [[here>>doc:Main.Release Information.Cloud Templates.R15 Docker - Double Lane.WebHome||target="blank"]].
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}}
13 13  
14 -== **Feedback Items** ==
12 +== **3rd generation runtime bolstering** ==
15 15  
16 -//__eMagiz Mendix connector__//
17 -We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.
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.
18 18  
19 -//__Improved OpenAPI import__//
20 -The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
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.
21 21  
22 -//__Flow test stack trace__//
23 -If a flow test creates a log line with level ‘Warning’ or ‘Error’ and there is a stack trace created, then we show the stack trace inside the log message on a separate tab.
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 24  
25 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
22 +//__Improved migration for JMS flows__//
23 +This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
26 26  
27 -== **Bug Fixes** ==
28 -//__Error handling__//
29 -When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this.
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}}
30 30  
31 -//__Volume mapping passwords__//
32 -Passwords for network volumes are hidden on the machine after deployment.
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.
33 33  
34 -//__Create integration removal__//
35 -When removing an integration from Create, the Create phase is now correctly updated.
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.
36 36  
37 -//__Legacy statistics__//
38 -Legacy pages are now correctly hidden when running on the current runtime architecture.
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.
39 39  
40 -//__Unused properties__//
41 -Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore.
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.
42 42  
43 -//__Enumeration values__//
44 -Enumeration values for event processors can now be edited in Create.
39 +== **Feedback items ** ==
45 45  
46 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
41 +We have also solved other feedback items besides the flow designer's critical updates.
47 47  
48 -//__SFTP sessions__//
49 -SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been released.
43 +//__Improved naming convention on Store related pages__//
44 +We have improved various display names using the merge functionality within our store offering.
50 50  
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.
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 +
51 51  == **Fancy Forum Answers** ==
52 52  
53 53  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:
54 54  
55 -* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
56 -* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
57 -* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
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"]]
58 58  
59 -== **Key Takeaways** ==
73 +== **Key takeaways** ==
60 60  
61 -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:
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:
62 62  
63 63  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
64 64  * If you have feedback or ideas for us, talk to the Platypus
65 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
79 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
66 66  * Clear your browser cache (Ctrl + Shift + Del)
67 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]]
81 +* Check out the release notes [here]
68 68  * Start thinking about how the license tracker can aid your development
69 69  * Start thinking about major, minor, and patch
84 +* Upgrade to the latest build number
70 70  * Keep making great integrations
71 71  
72 72  Let's stay in touch and till next time!
... ... @@ -74,11 +74,6 @@
74 74  {{info}}
75 75  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
76 76  
77 -{{/info}}
78 -)))
79 -
80 -(((
81 -{{toc/}}
82 -)))
92 +~*~* Indicates a GEN3-only feature.
93 +{{/info}})))((({{toc/}}))){{/container}}
83 83  {{/container}}
84 -{{/container}}