Skip to Content

Changes for page 222 - Flee Frustration

Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 467.1
edited by CarlijnKokkeler
on 2024/04/23 10:58
Change comment: There is no comment for this version
To version 109.1
edited by Erik Bakker
on 2023/05/05 10:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -219 - Creation Carousel
1 +196 - The Last Post
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,67 +1,81 @@
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!** In the last few weeks, we have work hard on improving our next generation architecture and introduced the "live" mode within our flow testing functionality. Furthermore there are loads of smaller feedback items and bugs that have been resolved with this release. So without further ado let us dive into all we have to offer.
7 7  
7 +== **"Live" mode on flow testing** ==
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 +With this release we bring an improved version of the flow testing functionality. As of now you will have the option to switch between "live" and "mock" mode will running a flow test. The "mock" mode is the mode you are used to from us. In this mode all external communication is mocked by the system and only the functional process can be tested.
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 +By switching to "live" mode you can not only test the functional process but also the communication to the external system. You can do so by entering the "edit" mode of the flow test and toggle between "mock" and "live" mode. When doing so eMagiz will show you the following pop-up stressing the consequences of your actions.
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.
13 +[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-pop-up.png]]
18 18  
19 -//__Improved OpenAPI import__//
20 -The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
15 +Once confirmed you will see that the user interface now indicates that the endpoint is in "live" mode.
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 +[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-result.png]]
25 25  
26 -//__Volume mapping passwords__//
27 -Passwords for network volumes are hidden on the machine after deployment.
19 +{{info}}* The following restrictions apply for this functionality
20 + ** "Live" mode can only be activated on HTTP outbound gateway components
21 + ** "Live" mode can **not** be active when you want to use the flow test as an "automated" test{{/info}}
28 28  
29 -//__Create integration removal__//
30 -When removing an integration from Create, the Create phase is correctly updated as well.
23 +== **3rd generation improvements** ==
31 31  
32 -//__Legacy statistics__//
33 -Legacy pages are now correctly hidden when running on the current runtime architecture.
25 +//__Event Streaming statistics completion__//
26 +In this release, we have updated the retrieval of data to ensure that for all models, all environments and all topics this data can be shown to the user so they can properly monitor the environment.
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.
28 +//__Deployments on next generation architecture__//
29 +This release fixes several smaller bugs and adds several improvements to the deployment process of the next generation architecture.
37 37  
38 -//__Enumeration values__//
39 -Enumeration values for event processors can now be edited in Create.
31 +//__Clean queues option__//
32 +This release introduces an option for **admins** to clean queues that remained after a migration towards the next generation runtime architecture. This will make the overview of which queues are "problematic" a much more realistic overview.
40 40  
41 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
34 +== **Feedback items ** ==
42 42  
43 -//__SFTP sessions__//
44 -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.
36 +//__On-premise containers are started upon slot wakeup__//
37 +With this release, we have added additional functionality to models running in the next generation runtime architecture. With this improvement all on-premise containers are stopped when the cloud slot goes to sleep and are woken up once the slot is woken up in the morning.
45 45  
39 +//__Resource path is shown to the user__//
40 +You can now, without downloading, see the resource path of a resource by viewing the metadata of the resource. You can do so by pressing the "eye" icon to view this information.
41 +
42 +//__Flow designer improvements__//
43 +With this release various improvements have been made to the flow designer. Among others we have improved the overview of what an "unused resource" is. You now have the option to define certain resources that are used but cannot be auto-detected by eMagiz to be an "used" resource to avoid confusion.
44 +
45 +//__Improved capabilities of a company contact__//
46 +With this release we have improved the capabilities of a company contact. As of now you can also add users to models belonging to subcompanies below your the company to which you are the company contact.
47 +
48 +== **Bug fixes ** ==
49 +
50 +//__Optional API parameters are handled correctly__//
51 +Currently, eMagiz would create the wrong expression for handling optional API parameters. With this release we have improved the expression in such a way that all optional parameters are handled correctly out of the box.
52 +
53 +//__Without CDM rights nothing related to any data model can be edited anymore__//
54 +With this release, we have made sure that nothing related to any data model can be edited without having the proper rights.
55 +
56 +//__Improved sorting of Design and Deploy archticture__//
57 +With this release, we now ensure that both Design and Deploy architecture are sorted in the same manner to avoid confusion when quickly switching between both views.
58 +
46 46  == **Fancy Forum Answers** ==
47 47  
48 48  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:
49 49  
50 -* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
51 -* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
52 -* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
63 +* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
64 +* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]
65 +* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||target="blank"]]
53 53  
54 -== **Key Takeaways** ==
67 +== **Key takeaways** ==
55 55  
56 -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:
69 +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:
57 57  
58 58  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
59 59  * If you have feedback or ideas for us, talk to the Platypus
60 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
73 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
61 61  * Clear your browser cache (Ctrl + Shift + Del)
62 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]]
75 +* Check out the release notes [here]
63 63  * Start thinking about how the license tracker can aid your development
64 64  * Start thinking about major, minor, and patch
78 +* Upgrade to the latest build number
65 65  * Keep making great integrations
66 66  
67 67  Let's stay in touch and till next time!
... ... @@ -69,11 +69,6 @@
69 69  {{info}}
70 70  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
71 71  
72 -{{/info}}
73 -)))
74 -
75 -(((
76 -{{toc/}}
77 -)))
86 +~*~* Indicates a GEN3-only feature.
87 +{{/info}})))((({{toc/}}))){{/container}}
78 78  {{/container}}
79 -{{/container}}