Skip to Content

Changes for page 201 - Be Informed

Last modified by Carlijn Kokkeler on 2024/04/18 13:13
From version 105.1
edited by Erik Bakker
on 2023/04/25 13:58
Change comment: There is no comment for this version
To version 94.1
edited by Erik Bakker
on 2023/03/17 08:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -196 - The Last Post
1 +194 - Giant Leap
Content
... ... @@ -2,66 +2,68 @@
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 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.
5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked around the clock to release various improvement points within the 3rd generation runtime and elsewhere. We have improved the feedback provided when a flow can't start due to an incorrect transformation, improved when specific logging is triggered, and improved the stability of our internal infrastructure. On top of that, we fixed several bugs surrounding other parts of the platform. So without further ado, let us look at all these improvements.
6 6  
7 -== **"Live" mode on flow testing** ==
7 +== **3rd generation improvements** ==
8 8  
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.
9 +//__Better feedback in the error log when a corrupt stylesheet is encountered__//
10 +We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action.
10 10  
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.
12 +//__Better internal error handling to avoid unnecessary alerting and notifications__//
13 +We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the alerts you receive on this topic when your model runs on the 3rd generation monitoring stack.
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-pop-up.png]]
15 +//__Improved Manage Dashboard__//
16 +This release improves what you can see in the Manage Dashboard after you migrate your model to the 3rd generation runtime architecture.
14 14  
15 -Once confirmed you will see that the user interface now indicates that the endpoint is in "live" mode.
18 +//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
19 +When a slot is put into standby mode, we also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models with this functionality. The opposite happens when the slot wakeup is triggered. As a result, not only the cloud runtimes are started but also all on-premise runtimes.
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-result.png]]
21 +//__Improved process of deploy preparation__//
22 +With this release, we have improved the process through which your deployment action is prepared by eMagiz. As a result, the chances of unexpected behavior occurring in your model are drastically reduced.
18 18  
19 -== **3rd generation improvements** ==
24 +//__Improved migration of Streaming container__//
25 +When migrating your streaming container, we now consider whether "custom error handling" is used within one of the event processors. Based on that determination, additional components are added to ensure that the streaming container will work after migrating without manual intervention.
20 20  
21 -//__Event Streaming statistics completion__//
22 -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.
27 +//__Add History to Notifications in Manage__//
28 +To improve the auditability of our platform, we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way, it is always visible when the notifications were paused and who paused or unpaused the notifications.
23 23  
24 -//__Deployments on next generation architecture__//
25 -This release fixes several smaller bugs and adds several improvements to the deployment process of the next generation architecture.
30 +//__Improved Manage phase for Event Streaming__//
31 +Based on the feedback on our first iteration of the Manage phase for Event Streaming, we have improved the graphs and the calculations that fill the graphs with values. On top of that, we have added help texts to clarify what each chart our table displays to you.
26 26  
27 -//__Clean queues option__//
28 -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.
33 +//__Improved help text for network volumes__//
34 +With this release, we have improved the help text that explains network volumes and how to use them within our solution.
29 29  
36 +{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
37 +
30 30  == **Feedback items ** ==
31 31  
32 -//__On-premise containers are started upon slot wakeup__//
33 -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.
40 +//__Generation of security logic API Gateway in case of API Key as security method is improved__//
41 +With this release, we have improved the generation of security logic within the Create phase related to API Gateways that use the API Key method as their security mechanism.
34 34  
35 -//__See Fixed IP in Deploy Architecture__//
36 -To improve our cloud offerings' we now display the configured fixed IP on your cloud connectors. This will unlock you as the user to easily communicate this value to external parties without involvement on our end.
43 +//__User Roles are sorted alphabetically__//
44 +All user roles under User Management are now also sorted alphabetically.
37 37  
38 -//__Resource path is shown to the user__//
39 -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.
46 +//__Name of keystore for user management now includes the environment__//
47 +To improve the naming of the downloaded keystore that needs to be distributed to external parties, we have added the name of the environment to the filename. You can distinguish between the various environments by looking at the filename.
40 40  
41 -//__Flow designer improvements__//
42 -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.
49 +//__Improved Topic calculations in Design Architecture__//
50 +Following our earlier improvements on the best practice configuration of topics we have now additionally updated the calculations on "Topic Storage" level to ensure that the configuration of a user is related to the total Assigned Size on "Topic Storage" level.
43 43  
44 -//__Improved capabilities of a company contact__//
45 -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.
46 -
47 47  == **Bug fixes ** ==
48 48  
49 -//__Optional API parameters are handled correctly__//
50 -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.
54 +//__Consolidated upgrade process cloud template__//
55 +With this release, we have removed some specific update options that could cause mismatches between what was visually displayed and what was happening in the cloud.
51 51  
52 -//__Without CDM rights nothing related to any data model can be edited anymore__//
53 -With this release, we have made sure that nothing related to any data model can be edited without having the proper rights.
57 +//__Ensure users can deploy release on environments they have edit rights on__//
58 +Currently, users with limited rights in Deploy, for example, only edit rights in Test, can now activate and deploy releases ready for other environments but need to be deployed on the environment for which they have the rights to do so.
54 54  
55 -//__Improved sorting of Design and Deploy archticture__//
56 -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.
57 -
58 58  == **Fancy Forum Answers** ==
59 59  
60 60  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:
61 61  
62 -* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
63 -* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]
64 -* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||target="blank"]]
64 +* [[API Security not updated in all entry flow>>https://my.emagiz.com/p/question/172825635703363718||target="blank"]]
65 +* [[Preventing exceptions triggering on HTTP 400 status code>>https://my.emagiz.com/p/question/172825635703351155||target="blank"]]
66 +* [[Deployment of 3rd gen runtimes to Azure Kubernetes Service (AKS containers)>>https://my.emagiz.com/p/question/172825635703350980||target="blank"]]
65 65  
66 66  == **Key takeaways** ==
67 67