Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 71.1
edited by Erik Bakker
on 2023/01/18 11:11
Change comment: There is no comment for this version
To version 362.1
edited by Carlijn Kokkeler
on 2024/01/29 14:49
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,131 +1,97 @@
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 and some minor enhancements. This release is characterized by the significant steps we took to release several major features on our 3rd generation runtime, including the queue browser and message redelivery functionality.
6 +**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been achieved.
6 6  
7 -== **Queue Browser** ~*~* ==
8 8  
9 -{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
9 +== **Pop-up Improvements** ==
10 +//__Property releases__//
11 +When a new property release is created, this property release can now be viewed and deleted.
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 in Manage. Then, with the help of the queue browser, you can browse your queue as the name suggests.
13 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
12 12  
13 -To do so, we offer two options within this functionality. First, 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 the current data in the queue. Then, when choosing the Wiretap functionality, you automatically wiretap your queue and are presented with copies (on a particular queue) of your actual message that passes through the queue from the moment you press the Wiretap button.
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.
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
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 -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.
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 -* 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 inadvertently put many messages on a queue.
21 -* Clear message from the wiretap queue (Wiretap option)
22 - ** Once you are done with the analysis of a specific 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 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.
29 29  
30 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
25 +== **Formatting & Alignments** ==
31 31  
32 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
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.
33 33  
34 -== **Message Redelivery ** ~*~* ==
30 +//__UI improvements__//
31 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
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 your environment.{{/warning}}
33 +//__Runtime overview image versions__//
34 +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.
37 37  
38 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
36 +//__Component changes reversion__//
37 +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.
39 39  
40 -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 under the "Explore" option in Manage. When selecting the message redelivery option, you will see all messages that currently need to be redelivered (as an error occurred).
39 +//__State generation statistics__//
40 +The state generation graphs will now show the correct number of cache hits and misses.
41 41  
42 -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.
42 +//__Queue browser timestamps__//
43 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
43 43  
44 -On top of that, we have added some additional functionality.
45 +//__Addition and deletion of internal recipients__//
46 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
45 45  
46 -* Search option
47 - ** Original queue name
48 - ** Original message ID (which can be found as a header called jms_messageid in the error message view)
49 -* Save as test message
50 - ** By pressing this button, you can save the message and use it in our flow testing functionality in Create.
51 -* Download
52 - ** By pressing this button, you can download the message and use it outside of the tooling should that be needed.
53 53  
54 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
49 +== **Feedback Items** ==
55 55  
56 -== **3rd generation runtime bolstering** ==
51 +//__Update flows__//
52 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
57 57  
58 -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 +//__Q&A forum search__//
55 +The option to search by pressing the Enter key has been added to the Q&A forum.
59 59  
60 -//__Define memory settings for on-premise runtimes from Deploy Architecture__//
61 -With this release, you can now define the memory settings (and, therefore, the memory limits) of your on-premise runtimes in the same manner as cloud runtimes. In all cases, you can now define and change the memory settings via Deploy Architecture. In contrast to how these values are actualized for cloud runtimes, you need to create a new release and deploy it to actualize the changes on-premise.
57 +//__Memory settings__//
58 +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.
62 62  
63 -//__Empty runtime feedback when deploying a release (or setting the release as active)__//
64 -To prevent you are not being able to deploy a release to your environment due to a mismatch between what is in your release and Deploy Architecture, we have now added a feedback pop-up when deploying a release that notifies you for which runtimes there is a mismatch between your release and Deploy Architecture.
60 +//__Runtime validation__//
61 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
65 65  
66 -//__Auto-fill namespaces for SOAP hosted webservices__//
67 -Based on your configuration in Design, eMagiz will now auto-fill the namespace when you host a SOAP web service. This avoids any potential problems in validating messages.
68 68  
69 -//__Updated H2 database setting__//
70 -As of this release, we have improved the configuration of our H2 databases used within eMagiz. This new setting will ensure the runtime controls when the H2 database is shut down.
64 +== **Bug Fixes** ==
71 71  
72 -{{warning}}If you already migrated your runtime, you should execute a "Reset" action on the infra flow to get these changes in your model{{/warning}}
66 +//__Removal of onramp__//
67 +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).
73 73  
74 -//__Runtime settings option added to context menu on runtime level Deploy Architecture__//
75 -As a replacement for the current HTTP settings context menu, we added a new menu item called runtime settings. On top of being able to configure your HTTP settings (which you need to define for a hosted web service), you now also can define whether the control bus needs to work for this runtime.
69 +//__Runtime statistics details__//
70 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
76 76  
77 -//__Deploy Agent option added to context menu on machine level Deploy Architecture__//
78 -With this release, we have added a context menu item allowing users to deploy the agent needed to run your 3rd generation architecture on-premise. For more information on installing this, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-installguide.WebHome||target="blank"]]
72 +//__Deployment prechecks__//
73 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
79 79  
80 -//__Performance improvement creating a release__//
81 -With this release, we have improved the performance of creating a release.
82 82  
83 -== **Feedback items ** ==
84 -
85 -We have also solved other feedback items besides the flow designer's critical updates.
86 -
87 -//__Sensitive information stored in properties is masked __//
88 -We have made how we display sensitive information across the portal similar for various parts of the portal.
89 -
90 -//__Importing "Private" store content to which you do not have access__//
91 -We have improved the user feedback a user will get when trying to import a "Private" store item unavailable to the user.
92 -
93 -
94 -== **Bug fixes ** ==
95 -
96 -//__Fix the possibility that allowed you to break the system message when dealing with the "Order matters" functionality__//
97 -We have fixed the possibility you had that would break your system message upon validating it in Create when using the "Order matters" functionality.
98 -
99 -//__Synchronization of Event Streaming topic states__//
100 -We fixed synchronization issues that could occur when several changes were executed on a model that uses a fast amount of topics.
101 -
102 -//__Copy and paste default support objects__//
103 -With this release, you can now copy and paste components without worrying that additional support objects already existing in your target flow are copied over and over into the same flow.
104 -
105 -//__Fix editability of properties when importing store items__//
106 -With this release, you can once again change property names upon importing a store item.
107 -
108 108  == **Fancy Forum Answers** ==
109 109  
110 110  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:
111 111  
112 -* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]]
113 -* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]]
114 -* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]]
115 -* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
80 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
81 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
82 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
116 116  
117 -== **Key takeaways** ==
84 +== **Key Takeaways** ==
118 118  
119 -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:
86 +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:
120 120  
121 121  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
122 122  * If you have feedback or ideas for us, talk to the Platypus
123 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
90 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
124 124  * Clear your browser cache (Ctrl + Shift + Del)
125 125  * Check out the release notes [here]
126 126  * Start thinking about how the license tracker can aid your development
127 127  * Start thinking about major, minor, and patch
128 -* Upgrade to the latest build number
129 129  * Keep making great integrations
130 130  
131 131  Let's stay in touch and till next time!
... ... @@ -133,6 +133,11 @@
133 133  {{info}}
134 134  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
135 135  
136 -~*~* Indicates a GEN3-only feature.
137 -{{/info}})))((({{toc/}}))){{/container}}
102 +{{/info}}
103 +)))
104 +
105 +(((
106 +{{toc/}}
107 +)))
138 138  {{/container}}
109 +{{/container}}