Changes for page 216 - Hack Heaven

Last modified by CarlijnKokkeler on 2024/04/18 13:04

From 67.1 to 68.1 From 413.1 to 414.1

From version 68.1

edited by Erik Bakker
on 2023/01/18 10:37

Change comment: There is no comment for this version

To version 413.1

edited by Erik Bakker
on 2024/03/11 14:48

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--190 - Fast Forward
++216 - Hack Heaven

Content

@@ -1,131 +1,107 @@
  {{container}}
--{{container layoutStyle="columns"}}(((
++{{container layoutStyle="columns"}}
++(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
++
++**Hi there, eMagiz developers!** As part of our alignment week we also had a hackathon event focusing on a wide array of reported feedback on the portal. The majority of the release blog will be focused on this. On top of that we launch new functionality that makes it easier to transform to JSON, to select infra flows in a release, and makes it possible to deploy multiple agents to a single machine that adheres to specific conditions. Furthermore, several announcements will be made via this release blog (and other channels) to better prepare your model for upcoming major changes.
--**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.
++== ** Announcement - TLS versions deprecated** ==
--== **Queue Browser** ==
++Placeholder for info from Bas
--{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
++{{info}}Text{{/info}}
--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.
++== **Announcement - Spring 6** ==
--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 (on a special queue) of your actual message that pass through the queue from the moment you pressed the Wiretap button.
++Placeholder for info from Jelle
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
++{{warning}}Text{{/warning}}
--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.
++== ** Updated release functionality - Infra flow selection** ==
--* Delete the message from the queue (Explore option)
--  ** 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.
--* Clear message from the wiretap queue (Wiretap option)
--  ** 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
--* Refresh messages list (both options)
--  ** 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
--* Save as test message
--  ** 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.
--* Download
--  ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
++This release will include a major update of our release functionality through which you can configure your release. As of now eMagiz will provide you with the option to visually see changes on infra flow level.
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
++[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
++When you are in edit mode you can select a new version via the right-click option as you were used to for other flows.
--== **Message Redelivery ** ==
++[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
--{{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}}
++On top of that we have added an title to each context menu that specifies the flow type (i.e. exit connector, container infra, connector infra) for additional clarity while constructing your release.
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
++[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
--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).
++== ** Updated deploy functionality on-premise - Multiple environments selection** ==
--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.
++{{warning}}The following is only applicable under the following conditions:
++  * Windows 2022 server
++  * Atleast one port opened (as a consequence of a hosted web service){{/warning}}
--On top of that we have added some additional functionality.
++When configuring your Deploy Agent you now have an additional option that can be activated by the user. With the help of this checkbox you unlock the possibility of stabily running multiple deploy agents on one machine.
--* Search option
--  ** Original queue name
--  ** Original message ID (which can be found as a header called jms_messageid in the error message view)
--* Save as test message
--  ** By pressing this button you can save the message and use it in our flow testing functionality in Create.
--* Download
--  ** By pressing this button you can download the message and use it outside of the tooling should that be needed.
++[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
++== **Feedback Items** ==
++//__Easier component selection in flow designer__//
++The area selector through which you can select one or more components has improved to allow for an easier selection of said components when they are displayed closed to the edge of the canvas. By expanding the area you can select the selection of these components will become much easier.
--== **3rd generation runtime bolstering** ==
++//__Improved handling of optionality in JSON on lists__//
++Previously, eMagiz would always create a JSON array if your data model expected a list. This would lead to unexpected and undesirable behavior of the message as empty arrays are not always accepted by external parties. With this release we have changed the way in which we generate the JSON output should there be an empty list in the output. Consequently the empty list will **not** be part of the output anymore as desired.
--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.
++//__Loading bar when searching for log entries__//
++To indicate to the user that eMagiz is still busy retrieving log entries we have now added a loading bar to the log entry overview upon pressing search.
--//__Define memory settings for on-premise runtimes from Deploy Architecture__//
--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.
++//__Improved feedback when deleting elements from Capture__//
++To better specify to the user which integration or system the user intends to delete we have improved the text in the confirmation pop-up. This way we can provide more information to the user to avoid mistakes.
--//__Empty runtime feedback when deploying a release (or setting the release as active)__//
--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.
++//__Enhanced filter options in Manage__//
++With this release we have added filter options on both the Alerting tab and the Trigger configuration pop-up. This results in being able to filter on Status (Alerting) and Queues, Topics, Recipients, and more (Trigger configuration pop-up) in these places.
--//__Auto-fill namespaces for SOAP hosted webservices__//
--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.
++//__Copy property names from Create__//
++This release unlocks the possibility to easily copy the name of a property placeholder so it can be used whilst deploying.
--//__Updated H2 database setting__//
--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.
++//__Improved feedback during migration to the current-runtime architecture__//
++We have improved the feedback should you try to migrate the JMS before any other runtime under Create -> Settings.
--{{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}}
++//__Block user from making changes to their cloud whilst another upgrade is still in progress__//
++We now block the user from making changes to their cloud configuration when another upgrade is still in progress.
--//__Runtime settings option added to context menu on runtime level Deploy Architecture__//
--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.
++//__Cron trigger validation__//
++We have added a validation check upon saving a cron expression in the Flow Designer to avoid flows not starting due to a misconfigured cron expression.
--//__Deploy Agent option added to context menu on machine level Deploy Architecture__//
--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.expert-solution-architecture-onpremises-installguide.WebHome||target="blank"]]
++== **Bug Fixes** ==
++//__Queue name validation__//
++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.
--//__Performance improvement creating a release__//
--With this release, we have improved the performance of creating a release.
++[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
--== **Feedback items ** ==
++//__Removal of onramp__//
++An issue has been fixed where removing an onramp that was previously linked to a combined entry was impossible in the Create phase.
--We have also solved other feedback items besides the flow designer's critical updates.
++//__eMagiz login__//
++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.
--//__Sensitive information stored in properties is masked __//
--We have made how we display sensitive information across the portal in the same manner for various parts of the portal.
--
--//__Confirmation pop-up displaying whether your topology changes in Deploy Architecture__//
--To give the user additional feedback of what will happen on the cloud slot when the user presses "Apply to environment" we have now added a confirmation pop-up that is shown when you migrate from the current runtime architecture to the 3rd generation runtime.
--
--//__Improved read-only description for "if exists" constructions in Transformations__//
--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.
--
--
--== **Bug fixes ** ==
--
--//__Fix possibility that allowed you to break the system message when dealing with the "Order matters" functionality__//
--We have fixed the possibility you had that would break your system message upon validating it in Create when using the "Order matters" functionality.
--
--//__Synchronization of Event Streaming topic states__//
--We have fixed synchronization issues that could occur when several changes were executed on a model that uses a fast amount of topics.
--
--//__Apply to environment in User Management performance improvement__//
--We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
--
  == **Fancy Forum Answers** ==
  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:
--* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
--* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
--* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
--* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
++* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]]
++* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]]
++* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]]
++* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]]
++* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]]
--== **Key takeaways** ==
++== **Key Takeaways** ==
--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:
++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:
  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
  * If you have feedback or ideas for us, talk to the Platypus
--* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
++* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
  * Clear your browser cache (Ctrl + Shift + Del)
  * Check out the release notes [here]
  * Start thinking about how the license tracker can aid your development
  * Start thinking about major, minor, and patch
--* Upgrade to the latest build number
  * Keep making great integrations
  Let's stay in touch and till next time!
@@ -133,6 +133,11 @@
  {{info}}
  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
--~*~* Indicates a GEN3-only feature.
--{{/info}})))((({{toc/}}))){{/container}}
++{{/info}}
++)))
++
++(((
++{{toc/}}
++)))
  {{/container}}
++{{/container}}

Changes for page 216 - Hack Heaven

Summary

Details

Navigation