Skip to Content

Changes for page 213 - Joyful Journeys

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -190 - Fast Forward
1 +213 - Joyful Journeys
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,123 +1,94 @@
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!** It has been a while since our last deployment on the 9th of December. As a result we have finished up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs as well as some small improvements. This release is characterized by the major steps we took to release several major features on our 3rd generation runtime among which are the queue browser and message redelivery functionality.
6 +**Hi there, eMagiz developers!** This release ....
6 6  
7 -== **Queue Browser** ==
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 -{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
12 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
10 10  
11 -To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture we have added a new feature to our Manage phase called the "Queue browser". You can access this functionality via the "Explore" menu option in Manage. With the help of the queue browser you can, as the name suggests, browse your queue.
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.
12 12  
13 -To do so, we offer two options within this functionality. We have the Explore function and we have the Wiretap function. When selecting a queue and opting for the Explore option you get a live view of what data is currently present on the queue. When selecting the Wiretap functionality you automatically wiretap your queue and are presented with copies of your actual message that pass through the queue from the moment you pressed the Wiretap button.
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.
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
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.
16 16  
17 -After selecting the queue and choosing the option eMagiz will show you the list of messages (oldest first) that are currently on the queue (Explore option) or that passed the queue since the moment you activate the option (Wiretap option). For each message you have various options at your disposal.
23 +== **Formatting & Alignments** ==
18 18  
19 -* Delete the message from the queue (Explore option)
20 - ** This means throwing away live data which can be helpful in a test or acceptance environment where you inadvertedly put a lot of messages on a queue.
21 -* Clear message from the wiretap queue (Wiretap option)
22 - ** Once you are done with the analysis of a certain message in the wiretap functionality you can clear it from the overview so it does not clutter the view anymore
23 -* Refresh messages list (both options)
24 - ** By pressing this button you can refresh the list of messages that are displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first
25 -* Save as test message
26 - ** By pressing this button you can save the message and use it in our flow testing functionality in Create. Note that we link the message to the corresponding flow if we can. Should we not be able to do so we link the message to your model so you can still use it in the flow testing functionality.
27 -* Download
28 - ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
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.
29 29  
30 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
28 +//__UI improvements__//
29 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
31 31  
32 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
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 33  
34 -== **Message Redelivery ** ==
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.
35 35  
36 -{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime and the functionality is enabled for you environment.{{/warning}}
37 +//__State generation statistics__//
38 +The state generation graphs will now show the correct number of cache hits and misses.
37 37  
38 -Just as with our current offering we now offer our message redelivery functionality for our 3rd generation architecture. To enhance the user experience we have placed this functionality as well under the "Explore" option in Manage. When selecting the message redelivery option you will see all messages that are currently in need to be redelivered (as an error occurred).
40 +//__Queue browser timestamps__//
41 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
39 39  
40 -Just as in the current functionality you can select a specific message and retry (or delete) it. The same can be done for all messages at once. Following that you can still see the linked error message as you could before.
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.
41 41  
42 -On top of that we have added some additional functionality.
46 +== **Feedback Items** ==
43 43  
44 -* Search option
45 - ** Original queue name
46 - ** Original message ID (which can be found as a header called jms_messageid in the error message view)
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.
47 47  
48 -== **3rd generation runtime bolstering** ==
51 +//__Q&A forum search__//
52 +The option to search by pressing the Enter key has been added to the Q&A forum.
49 49  
50 -This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
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.
51 51  
52 -//__SOAP and REST web services migration, including splitting them__//
53 -With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime. At the same time, you can directly split the all-entry to eliminate that construction. A specific migration path for this will be published in the documentation portal.
57 +//__Runtime validation__//
58 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
54 54  
55 -//__Changing SSL settings for 3rd generation runtime models works__//
56 -As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
57 57  
58 -//__Improved migration for JMS flows__//
59 -This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
61 +== **Bug Fixes** ==
60 60  
61 -{{warning}}If you already migrated your JMS flow, you should execute a "Reset" action on the JMS level to get these changes in your model{{/warning}}
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).
62 62  
63 -//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
64 -As of this release, you can no longer add debug components on a flow already migrated to the 3rd generation runtime. This functionality will not work in the 3rd generation runtime and would break your flow.
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.
65 65  
66 -//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
67 -We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
69 +//__Deployment prechecks__//
70 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
68 68  
69 -//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
70 -With this release, the properties generated for Event Streaming flows running in the 3rd generation runtime are configured correctly to mimic the ones in the image.
71 71  
72 -//__Added "Reset" functionality__//
73 -With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime.
74 -
75 -== **Feedback items ** ==
76 -
77 -We have also solved other feedback items besides the flow designer's critical updates.
78 -
79 -//__Improved naming convention on Store related pages__//
80 -We have improved various display names using the merge functionality within our store offering.
81 -
82 -//__Update security protocols for our internal architecture__//
83 -Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
84 -
85 -//__Improved read-only description for "if exists" constructions in Transformations__//
86 -To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does.
87 -
88 -
89 -== **Bug fixes ** ==
90 -
91 -//__Decent validation feedback when not filling in the property value__//
92 -We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
93 -
94 -//__Incorrect resource locations__//
95 -We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
96 -
97 -//__Apply to environment in User Management performance improvement__//
98 -We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
99 -
100 100  == **Fancy Forum Answers** ==
101 101  
102 102  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:
103 103  
104 -* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
105 -* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
106 -* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
107 -* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
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"]]
108 108  
109 -== **Key takeaways** ==
81 +== **Key Takeaways** ==
110 110  
111 -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:
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:
112 112  
113 113  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
114 114  * If you have feedback or ideas for us, talk to the Platypus
115 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
87 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
116 116  * Clear your browser cache (Ctrl + Shift + Del)
117 117  * Check out the release notes [here]
118 118  * Start thinking about how the license tracker can aid your development
119 119  * Start thinking about major, minor, and patch
120 -* Upgrade to the latest build number
121 121  * Keep making great integrations
122 122  
123 123  Let's stay in touch and till next time!
... ... @@ -125,6 +125,11 @@
125 125  {{info}}
126 126  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
127 127  
128 -~*~* Indicates a GEN3-only feature.
129 -{{/info}})))((({{toc/}}))){{/container}}
99 +{{/info}}
100 +)))
101 +
102 +(((
103 +{{toc/}}
104 +)))
130 130  {{/container}}
106 +{{/container}}