Wiki source code of 194 - Giant Leap

Last modified by Carlijn Kokkeler on 2024/04/18 13:18

Hide last authors
eMagiz 1.1 1 {{container}}
2 {{container layoutStyle="columns"}}(((
3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4
Erik Bakker 93.1 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.
eMagiz 1.1 6
Erik Bakker 89.1 7 == **3rd generation improvements** ==
Erik Bakker 56.1 8
Erik Bakker 93.1 9 //__Better feedback in the error log when a corrupt stylesheet is encountered__//
Erik Bakker 89.1 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.
Erik Bakker 56.1 11
Erik Bakker 89.1 12 //__Better internal error handling to avoid unnecessary alerting and notifications__//
Erik Bakker 93.1 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.
Erik Bakker 58.1 14
Erik Bakker 89.1 15 //__Improved Manage Dashboard__//
Erik Bakker 93.1 16 This release improves what you can see in the Manage Dashboard after you migrate your model to the 3rd generation runtime architecture.
Erik Bakker 81.1 17
Erik Bakker 89.1 18 //__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
Erik Bakker 93.1 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.
Erik Bakker 81.1 20
Erik Bakker 89.1 21 //__Improved process of deploy preparation__//
Erik Bakker 93.1 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.
Erik Bakker 58.1 23
Erik Bakker 89.1 24 //__Improved migration of Streaming container__//
Erik Bakker 93.1 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.
eMagiz 87.1 26
Erik Bakker 89.1 27 //__Add History to Notifications in Manage__//
Erik Bakker 93.1 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.
Erik Bakker 58.1 29
Erik Bakker 89.1 30 //__Improved Manage phase for Event Streaming__//
Erik Bakker 93.1 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.
Erik Bakker 58.1 32
Erik Bakker 89.1 33 //__Improved help text for network volumes__//
Erik Bakker 93.1 34 With this release, we have improved the help text that explains network volumes and how to use them within our solution.
Erik Bakker 58.1 35
Erik Bakker 93.1 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}}
Erik Bakker 84.1 37
Erik Bakker 30.1 38 == **Feedback items ** ==
Erik Bakker 18.1 39
Erik Bakker 92.1 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.
Erik Bakker 18.1 42
Erik Bakker 92.1 43 //__User Roles are sorted alphabetically__//
44 All user roles under User Management are now also sorted alphabetically.
Erik Bakker 77.1 45
Erik Bakker 92.1 46 //__Name of keystore for user management now includes the environment__//
Erik Bakker 93.1 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.
Erik Bakker 18.1 48
Erik Bakker 94.1 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.
51
Erik Bakker 84.1 52 == **Bug fixes ** ==
Erik Bakker 18.1 53
Erik Bakker 92.1 54 //__Consolidated upgrade process cloud template__//
Erik Bakker 93.1 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.
Erik Bakker 43.1 56
Erik Bakker 92.1 57 //__Ensure users can deploy release on environments they have edit rights on__//
Erik Bakker 93.1 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.
Erik Bakker 77.1 59
eMagiz 1.1 60 == **Fancy Forum Answers** ==
61
Erik Bakker 30.1 62 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:
eMagiz 1.1 63
Erik Bakker 92.1 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"]]
eMagiz 1.1 67
68 == **Key takeaways** ==
69
Erik Bakker 30.1 70 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:
eMagiz 1.1 71
Erik Bakker 30.1 72 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
eMagiz 1.1 73 * If you have feedback or ideas for us, talk to the Platypus
74 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
75 * Clear your browser cache (Ctrl + Shift + Del)
Carlijn Kokkeler 95.1 76 * Check out the release notes [[here>>doc:Main.Release Information.Portal.194 - Giant Leap.WebHome||target="blank"]]
eMagiz 1.1 77 * Start thinking about how the license tracker can aid your development
78 * Start thinking about major, minor, and patch
79 * Upgrade to the latest build number
80 * Keep making great integrations
81
82 Let's stay in touch and till next time!
83
84 {{info}}
Erik Bakker 30.1 85 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
eMagiz 1.1 86
87 ~*~* Indicates a GEN3-only feature.
88 {{/info}})))((({{toc/}}))){{/container}}
89 {{/container}}