Changes for page 216 - Hack Heaven

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

From 81.1 to 80.1 From 419.1 to 418.1

From version 418.1

edited by Erik Bakker
on 2024/03/11 15:17

Change comment: There is no comment for this version

To version 81.1

edited by Erik Bakker
on 2023/02/13 14:00

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 @@
--216 - Hack Heaven
++192 - Small Step

Content

@@ -1,136 +1,158 @@
  {{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, select infra flows in a release, and deploy multiple agents to a single machine that adheres to specific conditions. But before we dive into all that has changed, we will publish several announcements via this release blog (and other channels) to prepare your model for upcoming major changes.
++**Hi there, eMagiz developers!** In the last couple of weeks we worked hard on building several major things that will be released later this Q. On top of that we finished an additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the additional features we have the dynamic alerting and the debugger functionality.
--== ** Announcement - TLS versions deprecated** ==
++== **Start/Stop Flows** ~*~* ==
--Placeholder for info from Bas
++{{warning}}Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
--{{info}}Text{{/info}}
++To enhance the options you have when running into problems or when maintaining your solution in a Production environment, we have added a new feature to our Deploy phase called "Start/Stop Flows". You can access this functionality via the "Deploy Architecture" overview in Deploy. On runtime level you can open the context menu and select the option called "Start/Stop Flows".
--== **Announcement - Spring 6** ==
++[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
--In the next release, we expect to release a major version of our current runtime base image for all our clients running on the **current runtime** architecture. This image moves the eMagiz stack from Java 8 to Java 17, and from Spring Framework 5 to Spring Framework 6. Although eMagiz will try to make the transition as smooth as possible, we recommend that you start with the following preparations.
++
++{{info}}Only in "Start Editing" mode you can actually start and stop specific flows{{/info}}
++
++
++  observability of your integration landscape while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Dynamic Alerts." You can access this functionality via the "Alerting" menu in Manage. Then, with the help of the "Trigger" overview, you can view all triggers on your environment. On the top of the list you will see all "static" alerts as defined by eMagiz. Below that you will see all "dynamic" alerts that you and your fellow teammembers (with sufficient rights) can view, edit and delete.
--{{warning}}
--* Make sure that your release is running on the **latest** flow versions. After the release of the new image, eMagiz will push new flow versions of components that have changes. These new flow versions must be included in the subsequent release. Having your release already on the **latest** flow versions makes this less affecting
--* To help you identify which flow versions are especially important here, you can consider all flows that contain any of the following components:
--** Simple job launcher (data pipelines)
--** Job explorer (data pipelines)
--** HTTP components message sender (support object)
--** Web service outbound gateway (with a 'message sender' attribute specified)
--** SFTP session factory (support object)
--** API gateways with OAuth2 as security mechanism.
--* We recommend identifying flows with (advanced) custom Groovy scripts. As our Java version changes and the Spring version changes, this may affect the availability of the libraries on the classpath, and therefore the validity of import statements. You can already test the Groovy script using the flow testing functionality as flow testing is already running on the Java 17 and Spring Framework 6 baseline.
--** In addition, the groovy version used has been moved from version 3.0.19 to 4.0.18. These changes may affect your scripts as well. These release notes outline the major changes
--* The code handling SFTP file transfer has been overhauled completely. Although this should not affect you, we encourage you to test your SFTP integrations before deploying to Production.{{/warning}}
++We offer alerting on five types.
++* Error message
++* Log message
++* Queue consumers
++* Messages in queue
++* Queue throughput
--== **Infra flow selection** ==
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
--This release will include a significant update to our release functionality, which allows you to configure your release. Presently, eMagiz will allow you to see changes on the infra-flow level visually.
++These five options give you the option to configure more or less the same as you are currently used to when configuring triggers. Once you make a choice for a type you can press the "Next" button to fill in the details of the trigger. One example of how this can look is shown below.
--[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
--In edit mode, you can select a new version via the right-click option, which you already use for other flows.
++Once the trigger tab is filled in you can navigate to the "Output" tab to select the recipients for the trigger you are configuring. On top of that you can reduce the number of message at which congestion control is enabled if ten is too high for you.
--[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
--We have also added a title to each context menu that specifies the flow type (e.g., exit connector, container infra, connector infra) for additional clarity while constructing your release.
++== **Debugger ** ~*~* ~* ==
--[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
++{{warning}}Note that this functionality only works when the following criteria are met.
++* Your JMS server is running on the 3rd generation runtime
++* The store item called "3rd generation debugger" is imported in the infra flow of each runtime for which you want the ability to debug
++* A new release is created that includes the flow changes and this release is deployed to the environment(s){{/warning}}
--== **Multiple environments selection** ==
++As with our current offering, we now offer a functionality with which you can debug channels and see them via the eMagiz portal. As stated above to get to this point you need to execute several steps to get your model ready to be "debugged". Once you have done this you can activate the "debug" mode, via Deploy -> Containers for **one** specific flow **per** runtime that is of particular interest to you. Once you have done this you will see a pop-up telling you whether the "debug" mode was indeed activated or not.
--{{warning}}The following is only applicable under the following conditions:
--  * Windows 2022 server
--  * At least one port opened (as a consequence of a hosted web service){{/warning}}
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-success.png]]
--When configuring your Deploy Agent, you now have an additional option that the user can activate. This checkbox unlocks the possibility of stability when running multiple deploy agents on one machine.
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-failure.png]]
--[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
++Assuming it was activated correctly you can navigate to Manage -> Explore -> Queue browser and select the emagiz.debug queue to see the messages coming through.
--== **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 displayed close to the edge of the canvas. Expanding the area allows you to select these components, which will become much easier.
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-output-queue-browser.png]]
--//__Improved handling of optionality in JSON on lists__//
--Previously, eMagiz always created a JSON array if your data model expected a list. This led to unexpected and undesirable behavior of the message, as empty arrays are not always accepted by external parties.
++{{info}}Note the following limitations when working with the debugger.
++  * Your entire model needs to be migrated to the 3rd generation runtime
++  * Only **one** flow **per** runtime can be debugged **per** environment
++  * There is only **one** overview in which **all** debugged messages are shown
++  * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
++  * The debug 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 debug functionality will be shutdown automatically under water.
++    ** To see new messages after the five minutes you will have to access the debug functionality again from scratch.{{/info}}
--With this release, we have changed the way in which we generate the JSON output should there be an empty list. Consequently, the empty list will **not** be part of the output anymore, as desired.
++== **Volume mapping - Network Share** ==
--//__Loading bar when searching for log entries__//
--To indicate to the user that eMagiz is still busy retrieving log entries, we have added a loading bar to the log entry overview upon pressing search.
++This release will introduce an additional functionality within our [[volume mapping>>doc:Main.eMagiz Academy.Microlearnings.Novice.File based connectivity.novice-file-based-connectivity-volume-mapping-on-premise||target="blank"]] offering. With this additional configuration option you can configure a network share and configure it to create a mapping between a network share and a docker volume.
--//__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.
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-overview.png]]
--//__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 allows users to filter on Status (Alerting) and Queues, Topics, Recipients, and more (Trigger configuration pop-up) in these places.
++[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-detail.png]]
--//__Copy property names from Create__//
--This release unlocks the possibility of easily copying the name of a property placeholder so it can be used while deploying.
++== **Feedback items ** ==
--//__Improved feedback during migration to the current runtime architecture__//
--Should you try to migrate the JMS before any other runtime under Create -> Settings, we have improved the feedback. This feedback will tell you why you cannot migrate in this order.
++We have also solved other feedback items besides the flow designer's critical updates.
--//__Block user from making changes to their cloud while another upgrade is still in progress__//
--We now block users from changing their cloud configuration when another upgrade is ongoing.
++//__Show status on machine level under Deploy Architecture__//
++With this release we are now able to show the status of the machine when opening the "Details" overview on machine level in Deploy -> Architecture.
--//__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.
++//__Improved validation feedback on non-supported WSS4J interceptor __//
++We have improved the validation feedback when someone tries to implement a specific WSS4J interceptor implementation.
--== **Bug Fixes** ==
--//__Making Edit (and View) the default action when configuring parameters__//
--We have made the Edit (and View) button the default action when configuring parameters in a transformation.
++//__Improve help text in flow testing on Java classes__//
++We have improved the helptext when you are adding headers to your test message. In this helptext we explain the top five Java classes and how to note them down to make it work in the flow testing functionality and in eMagiz in general.
--//__Property configuration pop-up resized__//
--We have resized the property configuration overviews to make the property value better readable.
++//__Improved readibility of notification when trying to delete a runtime__//
++When you have forgotten one or more steps when deleting a runtime you will be notified by the system on this. With this release we have improved the readibility of the notification.
--//__Alphabetically sorted components in the flow designer__//
--As of this release, we now sort the components alphabetically in the flow designer.
++//__Improved sorting of missing properties overview__//
++We have improved the sorting on the missing properties overview you will encounter when activating the "check properties" option.
--//__Improved sorting on runtime overview__//
--As of this release, we now sort the runtimes in the runtime overview correctly by time. This means that the runtime with a changed status, closest to the current date and time, is shown at the top of the list. This should reduce the chance of overlooking a critical mistake.
++//__Improved notification when error message cannot be found__//
++We have improved the notification when an error message cannot be found from the message redelivery overview in our 3rd generation runtime.
--//__Improved sorting on catalog overview__//
--As of this release, we now sort the topics in the catalog by name.
++//__Additional lifecycle management overview__//
++We have added an additional lifecycle management overview to the portal in which users with enough permissions can get an overview of the lifecycle "state" of all customer models.
--//__Styling fix on rich text editors__//
--Rich text editors are used in various parts of the portal. This release fixes a broken styling configuration that made it difficult to fill in information in these editors.
++//__Improved feedback when memory settings are negative__//
++We have added an additional check that validates whether memory settings on a specific container are of a negative value. In these cases you will be blocked from applying the changes to the environment as this won't lead to a working solution.
--//__Styling fix on release edit__//
--As of this release, the correct icon (green) will be shown when wanting to add a second API operation under the same "header."
++//__Auto upgrade for a cloud template default to "ON"__//
++For each new cloud slot we will toggle the "automtatic cloud template update" to "Yes".
--//__Removed false-positive alerts on transformations__//
--When transforming a string to a non-empty string, eMagiz would also show an alert even if the user made a check to avoid an empty string as output. This behavior is now corrected. This will significantly reduce the number of alerts you will see as a user within the context of your transformation.
++//__Removed an irrelevant refresh button on a flow designer component__//
++We have removed an irrelevant refresh button on the standard filter component.
--//__Event Streaming Graphs - view thirty days back__//
--Just like the other views, we now also provide the user with a default thirty-day window to analyze relevant statistics related to event streaming further.
++//__Notification list shows all notifications on default__//
++When navigating to the Notification overview in Manage under Alerting you will now see all notifications instead of a filtered list on a specific state.
--//__Improved helptext__//
--We have improved various help texts across the portal to indicate better what should be filled in for specific fields.
++== **Bug fixes ** ==
++//__Keep selection when copying properties__//
++We have fixed the bug that prevented you from easily copying properties from one runtime to another based on the runtime list.
++
++//__Check on security header improved for API Gateway__//
++We improved the check in the API Gateway through which we validate whether an API caller is authenticated when using the API Key method to secure the API Gateway.
++
++//__Don't show systems with only "external" flows in Design__//
++We fixed a bug that caused systems to appear in Design in cases where there should be none.
++
++//__Fix styling of mendix login in some occurences__//
++When navigating to a specific URL the default Mendix login page would be shown. With this release we have fixed this behavior.
++
++//__Change timing of wake-up of cloud slots on Friday__//
++To prevent timing issues of waking up cloud slots on the Friday of our deployment we have changed the timing of when the cloud slots are woken up on Friday.
++
++//__Fixed a typo in the Topic statistics overview__//
++We fixed a typo in the topic statistics overview.
++
++//__Fixed a typo in the HTTP statistics overview__//
++We fixed a typo in the HTTP statistics overview.
++
++//__Activatation of release history when executing a deployment__//
++We ensured that the release history is activated when executing a deployment.
++
  == **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:
--* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
++* [[Characters transformed to � when retrieving from DataSink>>https://my.emagiz.com/p/question/172825635703287019||target="blank"]]
++* [[Can I test my API Gateway locally?>>https://my.emagiz.com/p/question/172825635703236592||target="blank"]]
++* [[Deploy stops when updating connector-infra>>https://my.emagiz.com/p/question/172825635703299903||target="blank"]]
--== **Key Takeaways** ==
++== **Key takeaways** ==
--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:
++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:
  * 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!
@@ -138,11 +138,6 @@
  {{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]]
--{{/info}}
--)))
--
--(((
--{{toc/}}
--)))
++~*~* Indicates a GEN3-only feature.
++{{/info}})))((({{toc/}}))){{/container}}
  {{/container}}
--{{/container}}

Changes for page 216 - Hack Heaven

Summary

Details

Navigation