Changes for page 216 - Hack Heaven

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

From 192.1 to 191.1 From 418.1 to 417.1

From version 417.1

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

Change comment: There is no comment for this version

To version 192.1

edited by CarlijnKokkeler
on 2023/10/23 15:02

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Title

@@ -1,1 +1,1 @@
--216 - Hack Heaven
++207 - Aligned State

Author

@@ -1,1 +1,1 @@
--XWiki.ebakker
++XWiki.CarlijnKokkeler

Content

@@ -1,127 +1,104 @@
  {{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!** We have done much work for state generation, so that you can derive more information from your data! Examples are enrichment, aggregation, change detection and duplicate detection. State generation functionality is only accessible for models with an add-on state generation license. Next to state generation, several improvements regarding the alignment of components have been made. Moreover, performance improvements and bug fixes have been implemented. Lastly, a change in the metrics storage duration has been performed.
--== ** Announcement - TLS versions deprecated** ==
++== **State Generation** ==
--Placeholder for info from Bas
++//__New components__//
++The following components have been added:
++* Aggregator: reverse of the splitter, used to combine multiple messages into a single one.
++* Infinispan metadata outbound channel adapter: used to (temporarily) store metadata, which can be used to enrich messages, or make decisions in filters or scripts.
++* Content enricher: used to add properties to the payload of messages, similar to what the header enricher can do for headers.
++* Duplicate detector: support object used to detect duplicate messages for a certain key on an inbound channel of a flow component. Duplicates can be marked or discarded.
++* Infinispan support objects, supporting the aggregator, metadata outbound channel adapter and content enricher.
--{{info}}Text{{/info}}
++//__SpEL functions & JSON__//
++Added SpEL functions for:
++* Encoding & decoding Base64, Hex and hmac.
++* Date retrieval (currentDateTime, currentEpochMilli, currentEpochSecond).
++* Date conversion (DateTime to Epoch, Epoch to DateTime, DateTime formatter and DateTime parser).
--== **Announcement - Spring 6** ==
++Added support for SpEL property accessors for XML and JSON, meaning that you can read message payloads in SpEL expressions easily. For example, to retrieve the value for 'id' in the following JSON String: `{"id":"123"}`, this SpEL expression suffices: `payload.id`.
--In the next release, we expect to release a major version of our current runtime base image. 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.
++Added support for `#JsonPath` usage in SpEL expressions.
--{{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}}
++//__New image version 2.0.0__//
++The above functionalities are features of the new image version 2.0.0. Important to note is that the library used for Code Mappings has been changed. Changed the library used for Code Mappings. Any customer with Gen3 runtimes and code mappings is required to reset their infra flows prior to deploying on image 2.0.0.
++//__Component pages__//
++Pages to add the new components have been created. Forms have been created nicely with proper help texts. The EHCache cache manager has been removed.
--== **Infra flow selection** ==
--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.
++== **Metrics Storage Duration** ==
++Manage - Monitoring: We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 5, 7 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively.
++
++
--[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
++== **Feedback Items** ==
--In edit mode, you can select a new version via the right-click option, which you already use for other flows.
++//__Alerting manual pause__//
++A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
--[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
++//__Ordering of graphs in Manage__//
++The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
--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.
++//__UTC times in Grafana panels__//
++All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
--[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
++//__Update flow designer version__//
++The framework used in the flow designer has been updated, improving performance.
--== **Multiple environments selection** ==
++//__Carwash track TLS versions in logging__//
++A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
--{{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}}
++//__Moving channels in the flow designer__//
++Moving already attached channels in the flow designer has been made sligthly easier.
--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.
++//__Topic sizes description change__//
++In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved.
--[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
++//__Password change notification__//
++When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action.
--== **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.
++//__Password comparison__//
++When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database.
--//__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.
++//__Inactive user alerting__//
++Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
--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.
++//__Alphabetical sorting on user level in HTTP statistics__//
++Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
--//__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.
--//__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.
--
--//__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.
--
--//__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.
--
--//__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.
--
--//__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.
--
--//__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.
--
  == **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.
--//__Property configuration pop-up resized__//
--We have resized the property configuration overviews to make the property value better readable.
++//__Flow designer styling__//
++The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
--//__Alphabetically sorted components in the flow designer__//
--As of this release, we now sort the components alphabetically in the flow designer.
++//__Partial search for messages__//
++It is now possible to search on messages partially in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
--//__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.
++//__Disk usage after cloud template update__//
++In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates.
--//__Improved sorting on catalog overview__//
--As of this release, we now sort the topics in the catalog by name.
++//__Error handling migration__//
++If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
--//__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.
--
--//__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."
--
--//__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.
--
--//__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.
--
--//__Improved helptext__//
--We have improved various help texts across the portal to indicate better what should be filled in for specific fields.
--
  == **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"]]
++* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
++* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
++* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
++* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
++* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||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:
  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
@@ -131,6 +131,7 @@
  * 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 next-generation-architecture only feature.
++{{/info}})))((({{toc/}}))){{/container}}
  {{/container}}
--{{/container}}

Changes for page 216 - Hack Heaven

Summary

Details

Navigation