Changes for page 216 - Hack Heaven
Last modified by CarlijnKokkeler on 2024/04/18 13:04
From version 64.1
edited by Erik Bakker
on 2023/01/18 10:23
on 2023/01/18 10:23
Change comment:
There is no comment for this version
To version 407.1
edited by CarlijnKokkeler
on 2024/02/27 16:02
on 2024/02/27 16:02
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -1 90-FastForward1 +215 - Tiny Tales - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,131 +1,52 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}}((( 2 +{{container layoutStyle="columns"}} 3 +((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 + 6 +**Hi there, eMagiz developers!** This release blog is small because we have been busy working on items that will be released later. For this release, the event streaming graph has been improved. Moreover, some bug fixes have been done. The validation for queue names with respect to spaces has been improved. Furthermore, it is now possible to remove an onramp that was previously linked to an all-entry. Lastly, it is now possible to log in to eMagiz by pressing enter when the username field is selected. 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. 8 +== **Feedback Items** == 9 +//__Improved event streaming graph__// 10 +The event streaming graph has been improved so that the offset difference of a topic is the sum of the offset differences of each partition in that topic. 6 6 7 - == **Queue Browser** ==12 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-topics.png]] 8 8 9 -{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}} 14 +//__Flow versions auto deletion__// 15 +Previously, the latest ten versions of a flow were not always selectable for a release. This has been improved so that from now on, the latest ten committed versions of each flow are always available. 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. 17 +== **Bug Fixes** == 18 +//__Queue name validation__// 19 +The validation regarding undesired spaces for components that use a queue name has been improved. Specifically, users are now prevented from creating a queue name with a space in the queue name when editing this in the Create phase in the Flow Designer. 12 12 13 - To do so, we offer two options within this functionality. Wehave the Explore functionand we have the Wiretap function.When selectingaqueue and optingfor theExploreoption you get aliveview of what data iscurrentlypresenton the queue.When selecting the Wiretap functionality you automatically wiretap yourqueueand are presented with copies (ona special queue) ofyour actualmessage that pass through thequeuefromthemoment you pressed the Wiretap button.21 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]] 14 14 15 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]] 23 +//__Removal of onramp__// 24 +An issue has been fixed where removing an onramp that was previously linked to a combined entry was impossible in the Create phase. 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. 26 +//__eMagiz login__// 27 +In the login screen, users can now "press enter" to log in when the username field is selected. Previously, this was only the case for the password field. 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. 29 - 30 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]] 31 - 32 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]] 33 - 34 -== **Message Redelivery ** == 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 - 38 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]] 39 - 40 -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). 41 - 42 -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 - 44 -On top of that we have added some additional functionality. 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 - 54 -[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]] 55 - 56 -== **3rd generation runtime bolstering** == 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. 59 - 60 -//__Define memory settings for on-premise runtimes from Deploy Architecture__// 61 -With this release, you are now able to 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. 62 - 63 -//__Empty runtime feedback when deploying a release (or setting the release as active)__// 64 -To prevent that you are not being able to deploy a release to your environment due to a mismatch between what is in your release and in 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. 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 - 69 -//__Updated H2 database setting__// 70 -As of this release, we have improved the configuration of our H2 databases that are used within eMagiz. This new setting will ensure that the runtime controls when the H2 database is shut down. 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}} 73 - 74 -//__Runtime settings option added to context menu on runtime level Deploy Architecture__// 75 -As a replacement of the current HTTP settings context menu we have 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. 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 that allows user to deploy the agent that is needed to run your 3rd generation architecture on-premise. For more information on how to install this please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture Store.On-premises deployment new runtime architecture||target="blank"]] 79 - 80 -//__Added "Reset" functionality__// 81 -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. 82 - 83 -== **Feedback items ** == 84 - 85 -We have also solved other feedback items besides the flow designer's critical updates. 86 - 87 -//__Improved naming convention on Store related pages__// 88 -We have improved various display names using the merge functionality within our store offering. 89 - 90 -//__Update security protocols for our internal architecture__// 91 -Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards. 92 - 93 -//__Improved read-only description for "if exists" constructions in Transformations__// 94 -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. 95 - 96 - 97 -== **Bug fixes ** == 98 - 99 -//__Decent validation feedback when not filling in the property value__// 100 -We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality. 101 - 102 -//__Incorrect resource locations__// 103 -We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime. 104 - 105 -//__Apply to environment in User Management performance improvement__// 106 -We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster. 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 -* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]] 113 -* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]] 114 -* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]] 115 -* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]] 33 +* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]] 34 +* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]] 35 +* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]] 36 +* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]] 37 +* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]] 116 116 117 -== **Key takeaways** ==39 +== **Key Takeaways** == 118 118 119 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:41 +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. 45 +* 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}} 57 +{{/info}} 58 +))) 59 + 60 +((( 61 +{{toc/}} 62 +))) 138 138 {{/container}} 64 +{{/container}}