Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 361.1
edited by Carlijn Kokkeler
on 2024/01/29 14:48
Change comment: There is no comment for this version
To version 144.1
edited by Erik Bakker
on 2023/08/15 10:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -213 - Joyful Journeys
1 +203 - Fast Paced
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,94 +1,46 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release ....
5 +**Hi there, eMagiz developers!** In the last few weeks, we have processed some of the early feedback on the release properties. On top of that we have improved the scalability of our complete solution and solved various smaller feedback items.
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.
7 +== **Release Properties - Early Feedback** ==
8 +The release property functionality was well received by the community. However, there was still room for improvement based on some of the early feedback we received from the community. Some of these early feedback items have been addressed in this release. As a result we have updated the layout of the edit screen of a property and have updated our checks on nested properties to avoid missing properties.
11 11  
12 -[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
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.
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 -== **Formatting & Alignments** ==
24 -
25 -//__Input fields__//
26 -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 -
28 -//__UI improvements__//
29 -UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
30 -
31 -//__Runtime overview image versions__//
32 -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.
33 -
34 -//__Component changes reversion__//
35 -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.
36 -
37 -//__State generation statistics__//
38 -The state generation graphs will now show the correct number of cache hits and misses.
39 -
40 -//__Queue browser timestamps__//
41 -All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
42 -
43 -//__Addition and deletion of internal recipients__//
44 -Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
45 -
46 46  == **Feedback Items** ==
47 47  
48 -//__Update flows__//
49 -In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
12 +//__"All entries" are now cleaned up as part of the migration__//
13 +To avoid problems when removing integrations after the migration towards the next-generation architecture we now clean-up the "all-entries" as part of the migration towards the next-generation architecture.
50 50  
51 -//__Q&A forum search__//
52 -The option to search by pressing the Enter key has been added to the Q&A forum.
15 +//__Trigger ID added to our alerting on the next-generation architecture__//
16 +We have added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and better manageable.
53 53  
54 -//__Memory settings__//
55 -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.
56 -
57 -//__Runtime validation__//
58 -Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
59 -
60 -
61 61  == **Bug Fixes** ==
62 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).
20 +//__Ensure no flow can be in a release twice__//
21 +We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions we fixed this.
65 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.
23 +//__Ensure no flow can be in a release twice__//
24 +We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions we fixed this.
68 68  
69 -//__Deployment prechecks__//
70 -During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
71 -
72 -
73 73  == **Fancy Forum Answers** ==
74 74  
75 75  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:
76 76  
77 -* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
78 -* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
79 -* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
30 +* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
80 80  
81 -== **Key Takeaways** ==
32 +== **Key takeaways** ==
82 82  
83 -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:
34 +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 84  
85 85  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
86 86  * If you have feedback or ideas for us, talk to the Platypus
87 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
38 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
88 88  * Clear your browser cache (Ctrl + Shift + Del)
89 89  * Check out the release notes [here]
90 90  * Start thinking about how the license tracker can aid your development
91 91  * Start thinking about major, minor, and patch
43 +* Upgrade to the latest build number
92 92  * Keep making great integrations
93 93  
94 94  Let's stay in touch and till next time!
... ... @@ -96,11 +96,6 @@
96 96  {{info}}
97 97  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
98 98  
99 -{{/info}}
100 -)))
101 -
102 -(((
103 -{{toc/}}
104 -)))
51 +~*~* Indicates a next-generation-architecture only feature.
52 +{{/info}})))((({{toc/}}))){{/container}}
105 105  {{/container}}
106 -{{/container}}