Skip to Content

Changes for page 222 - Flee Frustration

Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 486.1
edited by CarlijnKokkeler
on 2024/04/23 15:19
Change comment: There is no comment for this version
To version 130.1
edited by Erik Bakker
on 2023/07/17 15:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -219 - Creation Carousel
1 +201 - Be Informed
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,73 +1,73 @@
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 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!** In the last few weeks, we have worked hard on planning the upcoming Q and finishing up features of the previous Q. More on that later. On top of that, we have several smaller items as a result of our hackathon efforts to present to you.
7 7  
8 -== **Feedback Items** ==
7 +== **Announcement - Release Properties** ==
8 +As of the next release (202), we will introduce a new way of handling properties for all our clients. In the upcoming weeks, we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
9 9  
10 -//__eMagiz Mendix connector__//
11 -We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.
10 +== ** Deploy Architecture - Apply To Environment improvements ** ==
11 +As of this release, we will show you a list of all changes about to be changed once you press "Apply to the environment" in Deploy Architecture. This will make it clearer for users, especially those working in teams, what will change when pressing this button.
12 12  
13 -//__Improved OpenAPI import__//
14 -The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
13 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
15 15  
16 -//__Flow test stack trace__//
17 -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.
15 +== ** Breadcrumb navigation in eMagiz ** ==
16 +This release introduces the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed and impact the Create phase when you check out your transformation or system message on the flow level. Apart from there, the navigation is implemented consistently across the portal for a unified look and feel.
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
18 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
20 20  
21 -{{info}}With the release of Spring 6 in our previous release, some users reported that their filters have begun logging warnings about discarding messages even though the filter is configured to not throw an exception on rejection. For flows that process high numbers of messages (and potentially discard a lot of messages as well) this can significantly disturb the overview of the logs in the manage phase.
20 +== **Feedback Items** ==
22 22  
23 -To mitigate this, you can change the filter that throws the warning so it specifically refers to a discard channel. Given the chosen configuration, we advice to use the nullChannel option. This will silently drop the message without registering a warning in the log. In case you find the warning in the log a nice addition, we suggest to add an explicit discard channel leading to a logging outbound channel adapter. This log component can then be configured to throw a warning.
22 +//__Improved layout of catalog page in Design__//
23 +We have improved the layout of the API Catalog overview in Design for our API Gateway users. Among others, we have introduced a scrollbar to get a better overview of several operations.
24 24  
25 -In the next release, we will aid you by adding a validation check that will force you to select a discard channel when it is currently not selected once you edit the flow to create a new version. More on this in the next release blog. {{/info}}
25 +//__Improved layout of "Edit integration" pop-up for API Gateway integrations__//
26 +Currently, the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration.
26 26  
28 +//__Additional help texts on Design Architecture__//
29 +We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview.
27 27  
28 -== **Bug Fixes** ==
29 -//__Error handling__//
30 -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.
31 +//__Improved Audit Trail on several places__//
32 +In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.
31 31  
32 -//__Volume mapping passwords__//
33 -Passwords for network volumes are hidden on the machine after deployment.
34 +//__Removed the erroneous alert on message mapping when having a passthrough API__//
35 +This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
34 34  
35 -//__Create integration removal__//
36 -When removing an integration from Create, the Create phase is now correctly updated.
37 +== **Bug Fixes** ==
37 37  
38 -//__Legacy statistics__//
39 -Legacy pages are now correctly hidden when running on the current runtime architecture.
39 +//__Avoid clicking on other components while deleting another__//
40 +To avoid unexpected behavior, we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer.
40 40  
41 -//__Unused properties__//
42 -Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore.
42 +//__Improved validation feedback in migrating to the next-generation architecture__//
43 +We have improved the validation feedback when migrating to the next-generation architecture.
43 43  
44 -//__Enumeration values__//
45 -Enumeration values for event processors can now be edited in Create.
45 +//__Make sure that user credentials can be viewed with view rights__//
46 +This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights.
46 46  
47 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
48 +//__Refresh behavior within the deployment plan is fixed__//
49 +This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
48 48  
49 -//__SFTP sessions__//
50 -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.
51 -
52 52  == **Fancy Forum Answers** ==
53 53  
54 54  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:
55 55  
56 -* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
57 -* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
58 -* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
55 +* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
56 +* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
57 +* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]
59 59  
60 -== **Key Takeaways** ==
59 +== **Key takeaways** ==
61 61  
62 -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:
61 +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:
63 63  
64 64  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
65 65  * If you have feedback or ideas for us, talk to the Platypus
66 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
65 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
67 67  * Clear your browser cache (Ctrl + Shift + Del)
68 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
67 +* Check out the release notes [here]
69 69  * Start thinking about how the license tracker can aid your development
70 70  * Start thinking about major, minor, and patch
70 +* Upgrade to the latest build number
71 71  * Keep making great integrations
72 72  
73 73  Let's stay in touch and till next time!
... ... @@ -75,11 +75,6 @@
75 75  {{info}}
76 76  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77 77  
78 -{{/info}}
79 -)))
80 -
81 -(((
82 -{{toc/}}
83 -)))
78 +~*~* Indicates a GEN3-only feature.
79 +{{/info}})))((({{toc/}}))){{/container}}
84 84  {{/container}}
85 -{{/container}}