Skip to Content

Changes for page 214 - System Symphony

Last modified by Carlijn Kokkeler on 2024/04/18 13:06
From version 123.1
edited by Erik Bakker
on 2023/06/08 08:11
Change comment: There is no comment for this version
To version 364.1
edited by Carlijn Kokkeler
on 2024/01/29 14:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -199 - Home Improvements
1 +213 - Joyful Journeys
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,57 +1,95 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
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.
6 +**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been made so that more user friendly messages are shown that reflect actual behaviour. Moreover, formatting and alignment improvements have been made to improve the user journey. Lastly, some more feedback items and bug fixes have been done.
6 6  
7 -== **Next generation improvements and bug fixes** ==
8 +== **Pop-up Improvements** ==
9 +//__Property releases__//
10 +When a new property release is created, this property release can now be viewed and deleted.
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.
12 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
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.
14 +//__Runtime deletion__//
15 +When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container.
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}}
17 +//__Wiretap & debug error messages__//
18 +The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
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.
20 +//__Action messages__//
21 +The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
19 19  
20 -//__Unused images are cleaned up__//
21 -This release improves the way in which images are kept. To avoid a lot of old and unused images on our systems and our systems we now (on default) cleanup old images that are not used anymore. Should you wish to keep the images and manually remove them on your own server you can deactivate this behavior per "Deploy machine" step in your deployment plan.
22 22  
23 -== **Store Improvements** ==
24 +== **Formatting & Alignments** ==
24 24  
25 -//__Improved importing behavior for specific use cases__//
26 -Before, it could happen that a certain placeholder that contained an asterisk were imported incorrectly. This has now been fixed to ensure that the correct import behavior is experienced by our users.
26 +//__Input fields__//
27 +Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.
27 27  
28 -//__Fixed bug in creating a message mapping on top of an imported system message__//
29 -It is now possbile to create a message mapping to an imported system message from the store.
29 +//__UI improvements__//
30 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
30 30  
31 -== **Event Streaming - Certificate Management** ==
32 +//__Component changes reversion__//
33 +In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed.
32 32  
33 -//__Expired certification notification__//
34 -As of now we have functionality in place that will inform you (and us) when a client certificate of an Event Streaming user is going to expire within the upcoming three months. This way you can take action early on and report back that the update was succesfull so we can revoke the expiring client certificate accordingly. If you want specific information on this please reach out to us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
35 +//__State generation statistics__//
36 +The state generation graphs will now show the correct number of cache hits and misses.
35 35  
38 +//__Queue browser timestamps__//
39 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
40 +
41 +//__Addition and deletion of internal recipients__//
42 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
43 +
44 +
45 +== **Feedback Items** ==
46 +
47 +//__Update flows__//
48 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
49 +
50 +//__Q&A forum search__//
51 +The option to search by pressing the Enter key has been added to the Q&A forum.
52 +
53 +//__Memory settings__//
54 +It is now possible to change the memory settings of a container before pressing "Apply to environment". Before, it was only possible to view the memory settings if a container was running on AWS or running on a docker machine.
55 +
56 +//__Runtime validation__//
57 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
58 +
59 +//__Runtime overview image versions__//
60 +Insight into invented and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview.
61 +
62 +== **Bug Fixes** ==
63 +
64 +//__Removal of onramp__//
65 +We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before).
66 +
67 +//__Runtime statistics details__//
68 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
69 +
70 +//__Deployment prechecks__//
71 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
72 +
73 +
36 36  == **Fancy Forum Answers** ==
37 37  
38 38  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:
39 39  
40 -* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]]
41 -* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||target="blank"]]
78 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
79 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
80 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
42 42  
43 -== **Key takeaways** ==
82 +== **Key Takeaways** ==
44 44  
45 -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:
84 +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:
46 46  
47 47  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
48 48  * If you have feedback or ideas for us, talk to the Platypus
49 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
88 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
50 50  * Clear your browser cache (Ctrl + Shift + Del)
51 51  * Check out the release notes [here]
52 52  * Start thinking about how the license tracker can aid your development
53 53  * Start thinking about major, minor, and patch
54 -* Upgrade to the latest build number
55 55  * Keep making great integrations
56 56  
57 57  Let's stay in touch and till next time!
... ... @@ -59,6 +59,11 @@
59 59  {{info}}
60 60  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
61 61  
62 -~*~* Indicates a GEN3-only feature.
63 -{{/info}})))((({{toc/}}))){{/container}}
100 +{{/info}}
101 +)))
102 +
103 +(((
104 +{{toc/}}
105 +)))
64 64  {{/container}}
107 +{{/container}}