Changes for page 216 - Hack Heaven

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

From 87.1 to 88.1 From 423.1 to 424.1

From version 88.1

edited by eMagiz
on 2023/02/28 13:18

Change comment: There is no comment for this version

To version 423.1

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

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 @@
--193 - Fan Out
++216 - Hack Heaven

Author

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

Content

@@ -1,87 +1,138 @@
  {{container}}
--{{container layoutStyle="columns"}}(((
++{{container layoutStyle="columns"}}
++(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**Hi there, eMagiz developers!** In the last couple of weeks, we worked hard on API improvements and 3rd generation improvements for you all to see. Amongst the API improvements we now introduce the option to define REST/XML structures in your API gateway for your API callers to call. This brings more options to the user community in setting up the API Gateway structure in accordance with the needs and desires of the client. On top of that we have released several 3rd generation improvements. Amongst these we will add WS-Security functionality to the runtime and improvements on viewing release properties. Furthermore we have released new cloud templates to improve security in our current runtime and improve the auto-healing for 3rd generation runtime cloud slots. Last but not least we release the first adaptation of "State generation" that can be implemented with the help of us in your model. In the upcoming monts we will gather feedback from actual client cases and improve on this functionality.
++**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.
--== **REST XML for API Gateway** ==
++== ** Announcement - TLS versions deprecated** ==
--{{warning}}Note that a decision needs to be made to select XML or JSON as default format for all your operations hosted in your API Gateway.{{/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.WebHome||target="blank"]]** architecture for outgoing connections from eMagiz to external systems as of April 11th, 2024.
--To enhance your options when developing an API gateway that can be called by others we now introduce the option to select XML as the default message format on your API Gateway pattern. You can do this under Design -> Settings -> API Management. In here you can select and edit the settings.
++* TLSv1.0
++* TLSv1.1
--[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-default-setting.png]]
++{{info}}Text{{/info}}
--Every operation made after this decision will default to XML (or JSON which is still the default). Should you want to support JSON on some operations and XML on others you can select a default and manually correct the mediaType for the requests and responses to which it matters.
++== **Announcement - Spring 6** ==
--[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-change-media-type-setting.png]]
++We will release a major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3.WebHome||target="blank"]] base image for all our clients running on the **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3.WebHome||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.
--==**Cloud Template update** ==
++{{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}}
--We have released several new Cloud templates which will be installed via the auto-upgrade settings of your model (or manually in case not set).
--
--====Cloud Template R23 - Single Lane ====
++== **Infra flow selection** ==
--This release introduces a new cloud template for all our customers running in a single-lane setup in the 2nd generation runtime. This cloud template will update some specific security settings on these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
++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.
--====Cloud Template R6 - Single Lane ====
++[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
--This release introduces a new cloud template for all our customers running in a single-lane setup in the 3rd generation runtime. This cloud template will improve the auto-healing functionality of these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
++In edit mode, you can select a new version via the right-click option, which you already use for other flows.
--====Cloud Template R6 - Double Lane====
++[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
--This release introduces a new cloud template for all our customers running in a double-lane setup in the 3rd generation runtime. This cloud template will improve the auto-healing functionality of these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
++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.
--== **WS-Security on the 3rd generation runtime** ~*~* ==
++[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
--To further improve our offering on the 3rd generation runtime we now also have added the necessary functionality to allow you to call SOAP endpoints while utilizing WS-Security as well as securing your hosted SOAP endpoint through WS-Security protocols. Please make sure to create a new release that will trigger the image creation process which will included this feature when necessary.
++== **Multiple environments selection** ==
--== **State Generation ~*~* ==
++{{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}}
--With this release we introduce our first "State Generation" functionality to our user community. After rigorous internal testing and use we have now made a stride to also make it available to the user community on specific use case. In the following months we will gather feedback on this to further improve and release it in a simpler and more user friendly way to the user community.
++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.
--{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}}
++[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
--== **Feedback items ** ==
++== **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.
--//__Removed OData as option for an API Gateway operation__//
--With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform.
++//__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.
--//__Changes in API Gateway operation paths is automatically updated in Create__//
--When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry.
++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.
--{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
++//__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.
--== **Bug fixes ** ==
++//__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.
--//__Prevent endless loop in Deploy -> User Management__//
--With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion.
++//__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.
--{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}}
++//__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.
--//__Update error handling during migration to the 3rd generation runtime__//
--As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration.
++//__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.
++
++//__Alphabetically sorted components in the flow designer__//
++As of this release, we now sort the components alphabetically in the flow designer.
++
++//__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 sorting on catalog overview__//
++As of this release, we now sort the topics in the catalog by name.
++
++//__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:
--* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]
--* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]
--* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]]
++* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||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!
@@ -89,6 +89,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