Skip to Content
Last modified by Carlijn Kokkeler on 2024/04/18 13:11
From version 182.1
edited by Carlijn Kokkeler
on 2023/10/12 16:18
Change comment: There is no comment for this version
To version 93.1
edited by Erik Bakker
on 2023/03/14 08:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Situational Deployment
1 +194 - Big Leap
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -2,120 +2,73 @@
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 done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
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 -== **Release Date Change** ==
8 -As of release 208, released on November 9th, 2023, we will change our release date to Thursday morning starting at 05:00 AM CET (4:00 UTC). We opted for this change as it allows us to control better and manage our releases to uphold the quality standards you have gotten used to from us. Should you have any questions, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
7 +== **3rd generation improvements** ==
9 9  
10 -== **Deployment Plan** ==
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.
11 11  
12 -//__Improved deployment plan to make the process better and more predictable__//
13 -The algorithm for generating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. When stopping a machine, the JMS server is stopped last, and when executing the deployment plan, the JMS server is deployed first. This way, the JMS server is troubled minimally, and all processes are stopped before being deployed again. This provides additional control over the deployment of your release(s) and reduces the likelihood of false-positive logging (and potentially alerting) during and shortly after the deployment.
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.
14 14  
15 -{{info}}The start/stop/restart machine deployment steps work for cloud and on-premises machines.{{/info}}
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.
16 16  
17 -//__Editing release properties__//
18 -With this release, it will be possible to change the description of a property by editing the property.
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.
19 19  
20 -//__Container memory settings__//
21 -A change in memory settings triggers redeployment of the container now.
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.
22 22  
23 -//__Properties tab__//
24 -We have removed the deprecated tab Properties in the Deploy phase.
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.
25 25  
26 -//__Cleanup old images__//
27 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
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.
28 28  
29 -//__Performance improvements for loading releases__//
30 -Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before.
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.
31 31  
32 -== **Store Improvements** ==
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.
33 33  
34 -//__Message definition elements order__//
35 -We fixed an issue that the order of message definition elements was changed after being imported.
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}}
36 36  
37 -//__Importing a store item with synchronous message definitions__//
38 -We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions.
38 +== **Feedback items ** ==
39 39  
40 -//__Importing store items containing static copies__//
41 -We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly.
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.
42 42  
43 -//__Importing store content__//
44 -We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
43 +//__User Roles are sorted alphabetically__//
44 +All user roles under User Management are now also sorted alphabetically.
45 45  
46 -//__Store disclaimer__//
47 -Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message that states that the model owner should accept the disclaimer.
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.
48 48  
49 -== **Feedback Items** ==
49 +== **Bug fixes ** ==
50 50  
51 -//__Alerting manual pause__//
52 -A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
51 +//__Consolidated upgrade process cloud template__//
52 +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.
53 53  
54 -//__Ordering of graphs in Manage__//
55 -The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
54 +//__Ensure users can deploy release on environments they have edit rights on__//
55 +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.
56 56  
57 -//__UTC times in Grafana panels__//
58 -All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
59 -
60 -//__Update flow designer version__//
61 -The framework used in the flow designer has been updated to the latest version.
62 -
63 -//__Carwash track TLS versions in logging__//
64 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
65 -
66 -//__Moving channels in the flow designer__//
67 -Moving already attached channels in the flow designer has been made sligthly easier.
68 -
69 -//__Topic sizes description change__//
70 -In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved.
71 -
72 -//__Password change notification__//
73 -When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action.
74 -
75 -//__Password comparison__//
76 -When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database.
77 -
78 -//__Inactive user alerting__//
79 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
80 -
81 -//__Alphabetical sorting on user level in HTTP statistics__//
82 -Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
83 -
84 -//__SOAP Web services path__//
85 -Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
86 -
87 -== **Bug Fixes** ==
88 -
89 -//__Flow designer styling__//
90 -The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
91 -
92 -//__Partial search for messages__//
93 -It is now possible to search on messages partially in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
94 -
95 -//__Disk usage after cloud template update__//
96 -In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates.
97 -
98 -//__Error handling migration__//
99 -If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
100 -
101 101  == **Fancy Forum Answers** ==
102 102  
103 103  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:
104 104  
105 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
106 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
107 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
108 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
109 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
61 +* [[API Security not updated in all entry flow>>https://my.emagiz.com/p/question/172825635703363718||target="blank"]]
62 +* [[Preventing exceptions triggering on HTTP 400 status code>>https://my.emagiz.com/p/question/172825635703351155||target="blank"]]
63 +* [[Deployment of 3rd gen runtimes to Azure Kubernetes Service (AKS containers)>>https://my.emagiz.com/p/question/172825635703350980||target="blank"]]
110 110  
111 -
112 112  == **Key takeaways** ==
113 113  
114 -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:
67 +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:
115 115  
116 116  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
117 117  * If you have feedback or ideas for us, talk to the Platypus
118 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
71 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
119 119  * Clear your browser cache (Ctrl + Shift + Del)
120 120  * Check out the release notes [here]
121 121  * Start thinking about how the license tracker can aid your development
... ... @@ -128,6 +128,6 @@
128 128  {{info}}
129 129  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
130 130  
131 -~*~* Indicates a next-generation-architecture only feature.
84 +~*~* Indicates a GEN3-only feature.
132 132  {{/info}})))((({{toc/}}))){{/container}}
133 133  {{/container}}