Skip to Content

Changes for page 201 - Be Informed

Last modified by Carlijn Kokkeler on 2024/04/18 13:13
From version 119.1
edited by Erik Bakker
on 2023/06/05 14:27
Change comment: There is no comment for this version
To version 110.1
edited by Erik Bakker
on 2023/05/05 10:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -199 - Home Improvements
1 +196 - The Last Post
Content
... ... @@ -2,44 +2,67 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.
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.
6 6  
7 -== **Next generation improvements and bug fixes** ==
7 +== **"Live" mode on flow testing** ==
8 8  
9 -//__Enhanced overview of the HTTP Statistics__//
10 -As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort.
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.
11 11  
12 -//__Reason why runtime cannot start is now in the vast majority of cases reported back__//
13 -In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup.
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.
14 14  
15 -{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
13 +[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-pop-up.png]]
16 16  
17 -//__Forced congestion control__//
18 -To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform.
15 +Once confirmed you will see that the user interface now indicates that the endpoint is in "live" mode.
19 19  
17 +[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-result.png]]
20 20  
21 -//__Improved validation errors on the invalid configuration of HTTP outbound components__//
22 -This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
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}}
23 23  
24 -//__Improved migration behavior__//
25 -This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
26 -A smoother migration of your JMS (and backup JMS) process.
27 -Shortening of names that otherwise would be too long, additional feedback given to the user.
28 -Feedback when the migration process is finished.
23 +== **3rd generation improvements** ==
29 29  
30 -//__Additional checks when deploying__//
31 -This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
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.
32 32  
33 -== **Store Improvements** ==
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.
34 34  
35 -== **Event Streaming - Certificate Management** ==
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.
36 36  
34 +== **Feedback items ** ==
35 +
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.
38 +
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 +
37 37  == **Fancy Forum Answers** ==
38 38  
39 39  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:
40 40  
41 -* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
42 -* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||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"]]
43 43  
44 44  == **Key takeaways** ==
45 45