Changes for page 216 - Hack Heaven

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

From 241.1 to 240.1 From 428.1 to 427.1

From version 427.1

edited by Erik Bakker
on 2024/03/12 14:26

Change comment: There is no comment for this version

To version 241.1

edited by Carlijn Kokkeler
on 2023/10/31 09:24

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,129 +1,120 @@
  {{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. 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** ==
++{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
--As eMagiz, we continuously validate our best practices configuration on security to the industry-wide standards in the fields of security to uphold our reputation as a reliable and secure integration platform. As a result of our latest evaluation, we decided to follow the industry-wide standard to **not** support the following TLS versions anymore in our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture for outgoing connections from eMagiz to external systems as of April 11th, 2024.
++== **State Generation~*~*** ==
--* TLSv1.0
--* TLSv1.1
++//__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}}Should you have concerns whether any of the external systems called from your eMagiz model only support the older TLS versions we suggest checking this via either OpenSSL or by calling the endpoint via SOAP UI (version 5.7.0 or higher). {{/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`.
--We will release a major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] base image for all our clients running on the **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture in our release that will be released on April 11th, 2024. 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. With this functionality, you can access your JSON payloads in a similar way as you would access XML payloads using [[xPath>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Create your transformations.advanced-create-your-transformations-xpath-advanced||target="blank"]].
--{{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 changed. 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 essential 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 and Spring versions change, 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.
--** Additionally, the Groovy version has been moved from 3.0.19 to 4.0.18. These changes may affect your scripts as well. [[These release notes >>https://groovy-lang.org/releasenotes/groovy-4.0.html||target="blank"]] will specify the changes in more detail.
--* 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}}
++{{info}}The components are all configurable from the Flow Designer in Create and are accompanied by a help text explaining the use cases and the various technical configurations. Note that to make the components work in your model, a new release containing the latest image (2.0.0) needs to be deployed.{{/info}}
--== **Infra flow selection** ==
++{{warning}}The library used for Code Mappings has been changed. Any customer with next generation architecture runtimes and code mappings is required to reset their container infra flows prior to deploying on image 2.0.0. This has no consequences on a functional level. {{/warning}}
--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. This means that the platform and/or system will color light blue to signify this change in the infra version.
++== **Metrics Storage Duration** ==
++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 7, 14 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]]
++((((% border="3" cellpadding="10" cellspacing="10" style="width:400px" %)
++|=(% style="width: 120px;" %)Future|=(% style="width: 180px;" %)Minute level|=(% style="width: 180px;" %)Hour level
++|(% style="width:120px" %) Production|(% style="width:180px" %) 30 days|(% style="width:180px" %) 1 year
++|(% style="width:120px" %) Acceptance|(% style="width:180px" %) 14 days|(% style="width:180px" %) 6 months
++|(% style="width:120px" %) Test|(% style="width:180px" %) 7 days|(% style="width:180px" %) 3 months
++)))
--In edit mode, you can select a new version via the right-click option, which you already use for other flows.
++== **Feedback Items** ==
--[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
++//__Import from store__//
++The button 'Import from Store' in Design will directly open the store instead of showing a pop up asking whether the store should be opened.
--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.
++//__Save and cancel buttons placement__//
++The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.
--[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
++//__User session times__//
++The user session times for next generation architecture dashboards have been extended, so that the user is not thrown out of the model when using the Manage phase for longer than an hour.
--== **Multiple environments selection** ==
++//__Cancel and next buttons order__//
++The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
--{{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}}
++//__Data sink page__//
++The data sink page has been moved to the “Explore” tab.
--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.
++//__Unused images removal__//
++When a release is removed, the related unused images in the on-premises machines will be removed as well.
--[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
++//__Flow Designer performance__//
++Performance improvements for the Flow Designer have been implemented.
--== **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.
++//__Properties with special characters__//
++When a user would migrate to the next generation architecture and deploy their release containing properties with special characters, certain flows could not find the correct values to properties anymore or could not find the properties altogether. With this release, special characters such as a backslash do not break properties after deployment.
--//__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.
++//__Hidden flow fragements__//
++When importing items from the store, flow fragments that are hidden in design will be listed under the versions in create.
--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.
++//__Resources disappearances__//
++Resources would disappear in the flow designer when pressing Cancel on selecting a new resource. With this release, resources without a name will not trigger error messages when users select components.
--//__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.
++//__Error channel for all inbounds__//
++If there is no custom error handling, next generation migration would set the error channel to “errorChannel” only for the first inbound in an entry flow. We added a migration step, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
--//__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.
++//__Highlighting resources__//
++The performance of highlighting resources of selected components is improved in Read only mode.
--//__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.
++//__Topic and event-processor names__//
++The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable.
--//__Alphabetically sorted components in the flow designer__//
--As of this release, we now sort the components alphabetically in the flow designer.
++//__System alignment__//
++The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. So, systems are aligned regarding positioning across all phases. This will be done for existing systems as well.
--//__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.
++//__Error alerting__//
++The error trigger is now configured to check if an error message contains a certain term, besides checking the error header.
--//__Improved sorting on catalog overview__//
--As of this release, we now sort the topics in the catalog by name.
++//__Alerting__//
++For the next generation architecture models, several adaptations to triggers have been made.
++* For the next generation architecture models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%.
++* For the next generation architecture models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of configured size used to 110%.
++* The next generation architecture configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
--//__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.
++//__Unused containers__//
++Containers are set inactive when they are unused and removed in Design.
--//__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."
++//__Error popups when promoting a release version__//
++We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment.
--//__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.
++{{warning}}There is a new eMagiz Mendix connector available because a memory leak was found, only affecting Mendix connectors that have been migrated to the next generation architecture. It is advised to upgrade to the new eMagiz Mendix connector before fully migrating to the next generation architecture. {{/warning}}
--//__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"]]
++* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
++* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
++* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
++* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||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]]
@@ -133,6 +133,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!
@@ -140,11 +140,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