Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 315.1
edited by Carlijn Kokkeler
on 2023/12/21 14:40
Change comment: There is no comment for this version
To version 372.1
edited by Carlijn Kokkeler
on 2024/01/31 12:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +213 - Joyful Journeys
Content
... ... @@ -3,79 +3,82 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
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, we have worked on some more feedback items and several more bug fixes have been done.
7 7  
8 -== **TBD** ==
8 +== **Pop-up Improvements** ==
9 9  
10 +//__Property releases__//
11 +When a new property release is created, this property release can now not only be viewed but also release properties can be deleted.
10 10  
13 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
11 11  
12 -== **Feedback Items** ==
15 +//__Runtime deletion__//
16 +When deleting a runtime, the error message is more descriptive. The error message will now include the names of the flows that run on the container.
13 13  
14 -//__Runtime overview__//
15 -We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview.
18 +//__Wiretap & debug error messages__//
19 +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 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
21 +//__Action messages__//
22 +The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
18 18  
19 -//__Missing properties overview__//
20 -The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
24 +== **Formatting & Alignments** ==
21 21  
22 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
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.
23 23  
24 -//__Breaking changes pop-up__//
25 -Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'.
29 +//__UI improvements__//
30 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
26 26  
27 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
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.
28 28  
29 -//__External recipients emailaddress__//
30 -The overview of external recipients has been updated. External recipients are created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
35 +//__State generation statistics__//
36 +The state generation graphs will now show the correct number of cache hits and misses.
31 31  
32 -//__Broker queue metrics dashboards__//
33 -It is now possible to select the MQTT broker in the queue metrics dashboards.
38 +//__Queue browser timestamps__//
39 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
34 34  
35 -//__Runtime image version__//
36 -The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
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.
37 37  
38 -//__Runtime restart or redeploy overview__//
39 -Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
44 +== **Feedback Items** ==
40 40  
41 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
46 +//__Update flows__//
47 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. This is particularly useful when changing a resouce used across multiple flows such as topic message definitions in event processors.
42 42  
43 -== **Bug Fixes** ==
49 +//__Q&A forum search__//
50 +The option to search by pressing the Enter key has been added to the Q&A forum.
44 44  
45 -//__Message throughput__//
46 -The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
52 +//__Memory settings__//
53 +It is now possible to change the memory settings of a newly added container before pressing "Apply to environment".
47 47  
48 -//__Deployment execution error message__//
49 -In some cases when a machine type step in your deployment execution has an error and the portal tries to display this error message, it may give an error in the portal. This case has been fixed by now showing a generic error in the deployment plan and logging the full error to the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new popup.
55 +//__Runtime validation__//
56 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
50 50  
51 -//__Cloud template upgrade unjust rollback__//
52 -An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks on gen3.
58 +//__Runtime overview image versions__//
59 +Insight into intended 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.
53 53  
54 -//__Missing log entries__//
55 -We improved crash handling so that log messages clearly show when and why a container failed to start.
61 +== **Bug Fixes** ==
56 56  
57 -//__Runtime logging__//
58 -We fixed a bug where no new log messages were showing up, even though they were produced by the container.
63 +//__Removal of onramp__//
64 +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).
59 59  
60 -//__Next generation block__//
61 -Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
66 +//__Runtime statistics details__//
67 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
62 62  
63 -//__Feedback deployment plan__//
69 +//__Deployment prechecks__//
70 +During deployments, prechecks can be executed on runtimes level for runtimes that still have to be deployed. These prechecks can be executed via Deploy > Architecture.
64 64  
65 -
66 66  == **Fancy Forum Answers** ==
67 67  
68 68  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:
69 69  
70 -* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
71 -* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
72 -* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
73 -* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
74 -* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
76 +* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]]
77 +* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]]
78 +* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]]
75 75  
80 +== **Key Takeaways** ==
76 76  
77 -== **Key takeaways** ==
78 -
79 79  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:
80 80  
81 81  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -85,7 +85,6 @@
85 85  * Check out the release notes [here]
86 86  * Start thinking about how the license tracker can aid your development
87 87  * Start thinking about major, minor, and patch
88 -* Upgrade to the latest build number
89 89  * Keep making great integrations
90 90  
91 91  Let's stay in touch and till next time!
... ... @@ -93,7 +93,6 @@
93 93  {{info}}
94 94  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
95 95  
96 -~*~* Indicates a next-generation-architecture only feature.
97 97  {{/info}}
98 98  )))
99 99