Changes for page 216 - Hack Heaven

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

From 88.1 to 87.1 From 411.1 to 410.1

From version 410.1

edited by Erik Bakker
on 2024/03/11 14:39

Change comment: There is no comment for this version

To version 88.1

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

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
++193 - Fan Out

Author

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

Content

@@ -1,99 +1,87 @@
  {{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, to select infra flows in a release, and makes it possible to deploy multiple agents to a single machine that adheres to specific conditions. Furthermore, several announcements will be made via this release blog (and other channels) to better prepare your model for upcoming major changes.
--== ** Announcement - TLS 1.0 and 1.1 deprecated** ==
++**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.
--Placeholder for info from Bas
++== **REST XML for API Gateway** ==
--{{info}}{{/info}}
++{{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}}
--== **Announcement - Spring 6** ==
++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.
--Placeholder for info from Jelle
++[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-default-setting.png]]
--{{warning}}{{/warning}}
++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.
--== ** Updated release functionality - Infra flow selection** ==
++[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-change-media-type-setting.png]]
--This release will include a major update of our release functionality through which you can configure your release. As of now eMagiz will provide you with the option to visually see changes on infra flow level.
++==**Cloud Template update** ==
--[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
++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 ====
--When you are in edit mode you can select a new version via the right-click option as you were used to for other flows.
++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"]]
--[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
++====Cloud Template R6 - Single Lane ====
--On top of that we have added an title to each context menu that specifies the flow type (i.e. exit connector, container infra, connector infra) for additional clarity while constructing your release.
++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"]]
--[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
++====Cloud Template R6 - Double Lane====
--== ** Updated deploy functionality on-premise - Multiple environments selection** ==
++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"]]
--{{warning}}The following is only applicable under the following conditions:
--  * Windows 2022 server
--  * Atleast one port opened (as a consequence of a hosted web service){{/warning}}
++== **WS-Security on the 3rd generation runtime** ~*~* ==
--When configuring your Deploy Agent you now have an additional option that can be activated by the user. With the help of this checkbox you unlock the possibility of stabily running multiple deploy agents on one machine.
++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.
--[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
++== **State Generation ~*~* ==
--== **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 they are displayed closed to the edge of the canvas. By expanding the area you can select the selection of these components will become much easier.
++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.
--//__Improved handling of optionality in JSON on lists__//
--Previously, eMagiz would always create a JSON array if your data model expected a list. This would lead to unexpected and undesirable behavior of the message as empty arrays are not always accepted by external parties. With this release we have changed the way in which we generate the JSON output should there be an empty list in the output. Consequently the empty list will **not** be part of the output anymore as desired.
++{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}}
--//__Loading bar when searching for log entries__//
--To indicate to the user that eMagiz is still busy retrieving log entries we have now added a loading bar to the log entry overview upon pressing search.
++== **Feedback items ** ==
--//__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.
++//__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.
--//__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 results in being able to filter on Status (Alerting) and Queues, Topics, Recipients, and more (Trigger configuration pop-up) in these places.
++//__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.
--//__Copy property names from Create__//
--This release unlocks the possibility to easily copy the name of a property placeholder so it can be used whilst deploying.
++{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
++== **Bug fixes ** ==
--== **Bug Fixes** ==
--//__Queue name validation__//
--The validation regarding undesired spaces for components that use a queue name has been improved. Specifically, users are now prevented from creating a queue name with a space in the queue name when editing this in the Create phase in the Flow Designer.
++//__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.
--[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
++{{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}}
--//__Removal of onramp__//
--An issue has been fixed where removing an onramp that was previously linked to a combined entry was impossible in the Create phase.
++//__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.
--//__eMagiz login__//
--In the login screen, users can now press "enter" to log in when the username field is selected. Previously, this was only the case for the password field.
--
  == **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:
--* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]]
--* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]]
--* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]]
--* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]]
--* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]]
++* [[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"]]
--== **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!
@@ -101,11 +101,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