Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 360.1
edited by Carlijn Kokkeler
on 2024/01/29 14:41
Change comment: There is no comment for this version
To version 285.1
edited by Carlijn Kokkeler
on 2023/12/04 15:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -213 - Joyful Journeys
1 +210 - Deployment Delights
Content
... ... @@ -3,80 +3,62 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release ....
6 +**Hi there, eMagiz developers!** We have have done much work for the Deploy phase. Moreover, we did several bug fixes, mainly relating to the Deploy phase again, but also several for the Store. Lastly, we made some changes to the alerts that you may be receiving.
7 7  
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 +== **Alerts** ==
11 11  
12 -[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
10 +//__Topic approaching max size alert__//
11 +The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
13 13  
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.
13 +//__Missing metrics alert__//
14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
16 16  
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.
19 -
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.
22 -
23 -== **User Journey** ==
24 -//__Update flows__//
25 -In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
26 -
27 -//__Input fields__//
28 -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.
29 -
30 -//__UI improvements__//
31 -UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
32 -
33 -//__Q&A forum search__//
34 -The option to search by pressing the Enter key has been added to the Q&A forum.
35 -
36 36  == **Feedback Items** ==
37 37  
38 -//__Memory settings__//
39 -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.
18 +//__Container version overview__//
19 +In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
40 40  
41 -//__Runtime validation__//
42 -Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
21 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
43 43  
44 -//__Runtime overview image versions__//
45 -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.
23 +//__Unchanged containers__//
24 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
46 46  
26 +//__Rebuilding of images__//
27 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
28 +
47 47  == **Bug Fixes** ==
48 48  
49 -//__Removal of onramp__//
50 -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).
31 +//__Runtime metrics processing__//
32 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
51 51  
52 -//__Component changes reversion__//
53 -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.
34 +//__Deployment plan__//
35 +We solved a bug where a deployment step in the deployment plan could randomly get stuck.
54 54  
55 -//__State generation statistics__//
56 -The state generation graphs will now show the correct number of cache hits and misses.
37 +//__Store message merging__//
38 +The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
57 57  
58 -//__Runtime statistics details__//
59 -We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
40 +//__View all store items__//
41 +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.
60 60  
61 -//__Queue browser timestamps__//
62 -All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
43 +//__Out of memory behavior__//
44 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
63 63  
64 -//__Deployment prechecks__//
65 -During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
46 +//__Max fetch size__//
47 +We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
66 66  
67 -//__Addition and deletion of internal recipients__//
68 -Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
69 -
70 70  == **Fancy Forum Answers** ==
71 71  
72 72  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:
73 73  
74 -* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
75 -* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
76 -* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
53 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
54 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
55 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
56 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
57 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
77 77  
78 -== **Key Takeaways** ==
79 79  
60 +== **Key takeaways** ==
61 +
80 80  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:
81 81  
82 82  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -86,6 +86,7 @@
86 86  * Check out the release notes [here]
87 87  * Start thinking about how the license tracker can aid your development
88 88  * Start thinking about major, minor, and patch
71 +* 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,6 +93,7 @@
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  
79 +~*~* Indicates a next-generation-architecture only feature.
96 96  {{/info}}
97 97  )))
98 98