Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10

From 46.1 to 45.1 From 73.1 to 72.1

From version 72.1

edited by Erik Bakker
on 2023/01/19 09:02

Change comment: There is no comment for this version

To version 46.1

edited by Erik Bakker
on 2022/11/21 12:31

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
++188 - Close Encounters

Content

@@ -2,123 +2,72 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**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.
++**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all the interactions with it. Furthermore, some smalller fixes and beta features will be released to the community.
--== **Queue Browser** ~*~* ==
++== **3rd generation runtime bolstering** ==
--{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
++This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy improvements we made to the 3rd generation runtime and the interaction with it.
--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.
++//__Migration of JMS backup configuration improved__//
--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.
++//__Prechecks on Upgrade option made available for 3rd generation runtime__//
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
++//__Autogenerated exits can be deployed at once__//
--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.
++//__Code mapping functionality available on 3rd generation runtime__//
--* 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 inadvertently put many messages on a queue.
--* Clear message from the wiretap queue (Wiretap option)
--  ** 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
--* Refresh messages list (both options)
--  ** 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
--* 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.
++//__Improved the performance of deploying or activating a release__//
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
++//__Failing runtimes won't be restarted indefinetly anymore__//
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
++== **Exportable Release Audit** ~* ==
--{{info}}The following restrictions apply to this functionality:
--  * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
--  * The wiretap functionality works for a period of five minutes in which you can use the refresh button to see new messages coming in.
--    ** After five minutes the wiretap functionality will be shutdown automatically under water.
--    ** To see new messages after the five minutes you will have to access the wiretap functionality again from scratch.{{/info}}
++On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
--== **Message Redelivery ** ~*~* ==
++[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.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 your environment.{{/warning}}
++{{warning}}Note that the following restrictions apply when exporting an audit document:
++  * Changes made on definition and transformation level are **not** restored
++  * You will **not** be able to restore to any flow version that was created before October 17th, 2022
++  * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
++  * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
--[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
--
--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).
--
--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.
--
--On top of that, we have added some additional functionality.
--
--* 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@190-release-blog--message-redelivery-detail-overview.png]]
--
--== **3rd generation runtime bolstering** ==
--
--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.
--
--//__Define memory settings for on-premise runtimes from Deploy Architecture__//
--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.
--
--//__Empty runtime feedback when deploying a release (or setting the release as active)__//
--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.
--
--//__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.
--
--//__Updated H2 database setting__//
--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.
--
--{{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}}
--
--//__Runtime settings option added to context menu on runtime level Deploy Architecture__//
--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.
--
--//__Deploy Agent option added to context menu on machine level Deploy Architecture__//
--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"]]
--
--//__Performance improvement creating a release__//
--With this release, we have improved the performance of creating a release.
--
  == **Feedback items ** ==
  We have also solved other feedback items besides the flow designer's critical updates.
--//__Sensitive information stored in properties is masked __//
--We have made how we display sensitive information across the portal similar for various parts of the portal.
++//__Data Sink Refactor__//
++We have made some infrastructural changes to how data sink messages are stored and can be retrieved from the portal. Should there be changes needed on your end we will contact your seperately.
--//__Importing "Private" store content to which you do not have access__//
--We have improved the user feedback a user will get when trying to import a "Private" store item unavailable to the user.
++//__Improved naming convention on Store related pages__//
++We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
++//__Press "Enter" to search on multiple pages__//
++In our Daemon Switch release we added functionality that allowed you to press **Enter** to search on the property overview page. With this release we have added this functionality to many more pages across the portal. The complete list is as follows
--== **Bug fixes ** ==
++* Deploy → Deployment Plan
++* Deploy → Properties → History
++* Deploy → User Management → Roles
++* Manage → Error Messages → Error Messages
++* Manage → Error Messages → Flows with Error Messages
++* Manage → Error Messages → Exceptions of Error Messages
++* Manage → Log Entries
++* Manage → Alerts
++* Manage → Triggers
++* Manage → Tags – Cant find (only Gen2)
++* Manage → Notifications
++* Manage → Notification Settings
++* Manage → Data Usage → History
++* Manage → Code mappings → All tabs
--//__Fix the 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 fixed synchronization issues that could occur when several changes were executed on a model that uses a fast amount of topics.
--
--//__Copy and paste default support objects__//
--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.
--
--//__Fix editability of properties when importing store items__//
--With this release, you can once again change property names upon importing a store item.
--
  == **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:
--* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]]
--* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]]
--* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]]
--* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
++* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
++* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
++* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
++* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]]
  == **Key takeaways** ==

Changes for page 208 - Controlled State

Summary

Details

Navigation