Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 292.1
edited by Carlijn Kokkeler
on 2023/12/18 12:20
Change comment: There is no comment for this version
To version 366.1
edited by Carlijn Kokkeler
on 2024/01/29 15:02
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,60 +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 be viewed and 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 that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container.
13 13  
14 -//__Missing properties overview__//
15 -The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
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 -ADD FIGURE
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 -//__Container version overview__//
20 -Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.
24 +== **Formatting & Alignments** ==
21 21  
22 -[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-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 -//__Improved deployment process__//
25 -The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.
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 -//__Rebuilding of images__//
28 -Changing the list of flows that should run on a container will now trigger the rebuilding of images.
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.
29 29  
30 -== **Bug Fixes** ==
35 +//__State generation statistics__//
36 +The state generation graphs will now show the correct number of cache hits and misses.
31 31  
32 -//__Runtime metrics processing__//
33 -The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
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 -//__Deployment plan__//
36 -We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
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 -//__View all store items__//
39 -An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
44 +== **Feedback Items** ==
40 40  
41 -//__Out of memory behavior__//
42 -We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
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.
43 43  
44 -//__Max fetch size__//
45 -In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.
49 +//__Q&A forum search__//
50 +The option to search by pressing the Enter key has been added to the Q&A forum.
46 46  
52 +//__Memory settings__//
53 +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.
54 +
55 +//__Runtime validation__//
56 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
57 +
58 +//__Runtime overview image versions__//
59 +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.
60 +
61 +== **Bug Fixes** ==
62 +
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).
65 +
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.
68 +
69 +//__Deployment prechecks__//
70 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
71 +
47 47  == **Fancy Forum Answers** ==
48 48  
49 49  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:
50 50  
51 -* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
52 -* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
53 -* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
54 -* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
55 -* [[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"]]
56 56  
80 +== **Key Takeaways** ==
57 57  
58 -== **Key takeaways** ==
59 -
60 60  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:
61 61  
62 62  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -66,7 +66,6 @@
66 66  * Check out the release notes [here]
67 67  * Start thinking about how the license tracker can aid your development
68 68  * Start thinking about major, minor, and patch
69 -* Upgrade to the latest build number
70 70  * Keep making great integrations
71 71  
72 72  Let's stay in touch and till next time!
... ... @@ -74,7 +74,6 @@
74 74  {{info}}
75 75  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
76 76  
77 -~*~* Indicates a next-generation-architecture only feature.
78 78  {{/info}}
79 79  )))
80 80