Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 465.1
edited by CarlijnKokkeler
on 2024/04/23 10:46
Change comment: There is no comment for this version
To version 44.1
edited by Erik Bakker
on 2022/11/08 10:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -219 - Creation Carousel
1 +187 - Integration Sponsor
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,66 +1,78 @@
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!**
5 +**Hi there, eMagiz developers!** This release will release several impactful features and enablers to our community. Among others, the next phase of the eMagiz Store will become publicly available. This means that you can now import data models and transformation on top of system messages in Design and accelerators in Create. Furthermore, we will launch a new Beta functionality through some of our clients, enabling you to restore your flow to a previous version.
7 7  
7 +== **Store - Next phase** ==
8 8  
9 -== **Feedback Items** ==
10 -//__Machine agents__//
11 -We have added functionality that allows the user to (auto-) update their external (on-premise) machine agents from the portal. Please find out more HERE.
9 +This release will introduce the next phase of the Store to our whole community. With this new functionality, you can import data model messages (i.e., CDM, API Gateway Data model, or Event Streaming data model) and transformations. Connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce, and others will become even more accessible.
12 12  
13 -//__Custom webhook__//
14 -We removed a deprecated functionality that sends a custom webhook when upgrading the environment. Please find out more HERE.
11 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
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.4
13 +{{info}}For more information on the Store please check out this [[course>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]]. As a reminder, you can find all documentation on all available Store content published by eMagiz [[here>>doc:Main.eMagiz Store.WebHome||target="blank"]].{{/info}}
18 18  
19 -//__Improved OpenAPI import__//
20 -The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
15 +== **New eMagiz Mendix Connector** ==
21 21  
22 -== **Bug Fixes** ==
23 -//__Error handling__//
24 -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.
17 +This release introduces a new version of the eMagiz Mendix Connector. This version (6.0.0) will work with the current runtime architecture and the new runtime architecture making the migration from the existing runtime architecture to the new runtime architecture easier. The latest version of the eMagiz Mendix Connector can be found in the Mendix Marketplace and the eMagiz portal.
25 25  
26 -//__Volume mapping passwords__//
27 -Passwords for network volumes are hidden on the machine after deployment.
19 +{{info}}Migrating the runtime from the eMagiz portal works the same as for any other runtime. The migration path can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}}
28 28  
29 -//__Create integration removal__//
30 -When removing an integration from Create, the Create phase is correctly updated as well.
21 +== **Flow version restore** ~* ==
31 31  
32 -//__Legacy statistics__//
33 -Legacy pages are now correctly hidden when running on the current runtime architecture.
23 +On top of that, we will also launch a new Beta feature to the community that allows you to restore your flow to a previous version. This way, you can quickly undo changes made that were incorrect.
34 34  
35 -//__Unused properties__//
36 -Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore.
25 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
37 37  
38 -//__Enumeration values__//
39 -Enumeration values for event processors can now be edited in Create.
27 +{{warning}}Note that the following restrictions apply when restoring to a previous version:
28 + * Changes made on definition and transformation level are **not** restored
29 + * You will **not** be able to restore to any flow version that was created before October 17th, 2022
30 + * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
31 + * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
40 40  
41 -//__SFTP sessions__//
42 -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. Please find out more HERE.
33 +== **Feedback items ** ==
43 43  
35 +We have also solved other feedback items besides the flow designer's critical updates.
36 +
37 +//__Improved help texts Kafka component__//
38 +The help texts on various configuration options and the general help text on multiple Kafka components have been updated to clarify how they work and how you ought to configure them to achieve the best possible result when sending and receiving messages to and from topics within eMagiz.
39 +
40 +//__Improved warning message when Message redelivery cannot be adequately executed__//
41 +We have improved the warning you get when you cannot retrieve the messages waiting to be redelivered. This helps clarify what is going wrong when a user sees this warning.
42 +
43 +//__See Flow Designer errors on the Create overview__//
44 +To improve our offering surrounding the new Flow Designer functionality, we now show on the Create overview which of the flows you still have alerts due to a misconfiguration of the flow. This will help to identify ongoing work much more manageable.
45 +
46 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--alert-visualized-in-create-overview.png]]
47 +
48 +{{info}}Note that you need to open flows that are currently triggering alerts to show the alert on the Create overview{{/info}}
49 +
50 +== **Bug Fixes** ==
51 +
52 +//__Update Swagger File when changing the order of entities in gateway message__//
53 +In our previous release, we improved how the Swagger file is generated when changing the order of attributes of your gateway message. To make this functionality work for entities, we have made several additional changes to the platform supporting this.
54 +
44 44  == **Fancy Forum Answers** ==
45 45  
46 46  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:
47 47  
48 -* [[Model Dashboard - Manage - color explanation>>https://my.emagiz.com/p/question/172825635703786144||target="blank"]]
49 -* [[Error handling within XSLT extension gateway>>https://my.emagiz.com/p/question/172825635700354385||target="blank"]]
50 -* [[Requesting Azure token not working because of form-data structure>>https://my.emagiz.com/p/question/172825635703799013||target="blank"]]
51 -* [[PGP Signing and Encryption>>https://my.emagiz.com/p/question/172825635703799061||target="blank"]]
59 +* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
60 +* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
61 +* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
62 +* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]]
52 52  
53 -== **Key Takeaways** ==
64 +== **Key takeaways** ==
54 54  
55 -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:
66 +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:
56 56  
57 57  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
58 58  * If you have feedback or ideas for us, talk to the Platypus
59 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
70 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
60 60  * Clear your browser cache (Ctrl + Shift + Del)
61 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]]
72 +* Check out the release notes [here]
62 62  * Start thinking about how the license tracker can aid your development
63 63  * Start thinking about major, minor, and patch
75 +* Upgrade to the latest build number
64 64  * Keep making great integrations
65 65  
66 66  Let's stay in touch and till next time!
... ... @@ -68,11 +68,6 @@
68 68  {{info}}
69 69  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
70 70  
71 -{{/info}}
72 -)))
73 -
74 -(((
75 -{{toc/}}
76 -)))
83 +~*~* Indicates a GEN3-only feature.
84 +{{/info}})))((({{toc/}}))){{/container}}
77 77  {{/container}}
78 -{{/container}}