Changes for page 207 - Aligned State

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

From 40.1 to 41.1 From 84.1 to 85.1

From version 41.1

edited by Erik Bakker
on 2022/11/07 16:35

Change comment: There is no comment for this version

To version 84.1

edited by Erik Bakker
on 2023/02/27 16:23

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 @@
--187 - Integration Sponsor
++193 - Fan Out

Content

@@ -2,142 +2,69 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**Hi there, eMagiz developers!** With this release we will release several impactful features and enablers to our community. Among others the next phase of the eMagiz Store will become publicly available. This means that you can now import data models and transformation on top of system messages in Design and accelerators in Create. Furthermore, we will launch a new Beta functionality through some of our clients that will enable you to restore your flow to a previous version.
++**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.
--== **Store - Next phase** ==
++== **REST XML for API Gateway** ~*~* ==
--This release will introduce the next phase of the Store to our whole community. With this new functionality you can now import data model messages (i.e. CDM, API Gateway Data model or Event Streaming data model) and transformations. This way connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce and others will become even easier.
++{{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}}
--[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
++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.
--{{info}}For more information on the Store please check out this [[course>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]]. As a reminder you can find all documentation on all available Store content published by eMagiz [[here>>doc:Main.eMagiz Store.WebHome||target="blank"]].{{/info}}
++[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-default-setting.png]]
--== **New eMagiz Mendix Connector** ==
++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.
--With this release we introduce a new version of the eMagiz Mendix Connector. This version (6.0.0) will work both with the current runtime architecture and the new runtime architecture making the migration from the current runtime architecture to the new runtime architecture easier. The new version of the eMagiz Mendix Connector can be found in the Mendix Marketplace and in the eMagiz portal.
++[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-change-media-type-setting.png]]
--{{info}}Migrating the runtime from the eMagiz portal works the same as for any other runtime. The migration path to migrate can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}}
++==**Cloud Template R23 - Single Lane** ==
--== **Flow version restore** ~* ==
++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"]]
--On top of that we will also launch a new Beta feature to the community that allows you to restore your flow to a previous version. This way you can quickly undo changes made that were incorrect.
++==**Cloud Template R6 - Single Lane** ==
--[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.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"]]
--{{warning}}Note, that the following restrictions apply when restoring to a previous version:
--  * Changes made on definition and transformation level are **not** restored
--  * You will **not** be able to restore to any flow version that was created before October 17th, 2022
--  * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
--  * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
++==**Cloud Template R6 - Double Lane** ==
--== **Feedback items ** ==
++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 solved other feedback items besides the flow designer's critical updates.
++== **WS-Security on the 3rd generation runtime** ~*~* ==
--//__Redirect to the Manage Dashboard from your model home page__//
--Directly navigating to the Manage phase (of any environment) will automatically redirect you to the error message Dashboard, as that is the landing page of the Manage phase.
++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.
--//__Readable entry of a SpEL expression in a flow component__//
--As of now, the input field for your SpEL expression in certain flow components will dynamically expand when you enter a large SpEL expression. This will improve the readability of your solution and will make it easier to enter and validate your SpEL expressions.
++== **State Generation ~*~* ==
--[[image:Main.Images.Release Blog.WebHome@186-release-blog--spel-expression-readible.png]]
++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.
--//__Keep Create and the Create Phase release in sync__//
--Previously the Create and the Create Phase release might have become out of sync. As a result, comparing a release to the Create Phase release could yield confusing results. With this release, we have made several improvements to prevent this from happening.
++{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}}
--//__Mask password values in the unused properties overview__//
--All property values of the type password can be masked in the properties overview screen. However, this behavior was different when pressing the unused properties overview. With this release, we have corrected this behavior to ensure that passwords are also masked in this overview.
++== **Feedback items ** ==
--//__Press Enter to Search for properties__//
--With this release, we have added functionality that makes it possible to press **Enter** when searching for properties in the property overview.
++//__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.
--//__Styling update on tag selection on integration level__//
--With this release, we have improved the styling of tags displayed on the integration and system level. This way, the tag is better readable, and the icon to remove a selected tag is completely shown to the user instead of partly.
++//__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.
--//__Enter to close automated flow testing pop-up__//
--Upon your requests, we have made the pop-up detailing your automated flow test results to be closable by pressing the Enter key on your keyboard. This saves you the hassle of grabbing your mouse and clicking the button.
++{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
--//__Improved naming of downloaded Event Streaming keystore__//
--When downloading a Keystore that an Event Streaming client needs to access a topic, the name now includes the client name **and** the environment so you can easily discern the difference between the keystores when distributing them to your client.
++== **Bug fixes ** ==
--//__Pop out on the Traces tab within Flow Testing__//
--In line with the improvements we made before within the Flow Testing functionality, we have now added the pop-out functionality to all results shown in the traces tab. This will make it easier to analyze what happens between the start and the end of your flow.
++//__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.
--//__Sorting User Management__//
--As of this release, the user management overview in Deploy for users and roles will be sorted alphabetically to make it easier to find a specific user or role within this overview.
++{{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}}
--//__Improved warning on passthrough API operation__//
--Most users forget to configure a backend API operation or switch to the transformation option when configuring an API operation in Capture and Design before moving to Create. This is then blocked, leaving users confused about what to do next. Therefore we introduce an additional warning in the Design phase that lets you know that your configuration of an API operation is not yet finished. This way, you can correct it **before** trying to move it to Create.
++//__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 update functionality of Swagger file when changing data model__//
--Before, there were specific scenarios in which the Swagger file was not updated according to changes made to your API data model. With this release, we have made a first step in improving this behavior. Then, when you change the order of attributes in your data model, the Swagger file will be updated accordingly.
--
--{{info}}Note that just as with any resource that is changed from the Design phase, a version bump of your flow in Create is still necessary to deploy the changes to your environment(s){{/info}}
--
--//__"Disapprove and go to environment"__//
--Following the "Approve and go to environment" functionality, we have now expanded that by adding the "Disapprove and go to environment" functionality.
--
--//__Improve readability of API Gateway operations in Create and Deploy__//
--When you have a lengthy name for your API Gateway operation, it becomes tough to discern the various API Gateway operations in your landscape. To alleviate this problem, we have added a tooltip functionality that will show the full display name when hovering over the API Gateway operation.
--
--//__Add Topic Storage information to License Tracker__//
--On top of the information already shown in the License Tracker, we have added Storage information for the Event Streaming pattern. This way, you can easily see the amount of GB you have assigned and the amount of GB that was contractually agreed upon between you and eMagiz.
--
--[[image:Main.Images.Release Blog.WebHome@186-release-blog--topic-storage-info.png]]
--
--//__Add Compatibility check when importing store items__//
--We have added a compatibility check to the platform to prevent you from importing store items that do not work on a specific runtime architecture to prevent this from happening.
--
--//__Show dependencies between support objects__//
--As of now, when you click on a support object, all related support objects will also be highlighted in the same overview. This makes it easier to see the relationship between support objects and components and among support objects.
--
--//__Improve rendering of validation definition when using multiple namespaces__//
--With this release, we have improved how we render the validation definition (XSD) when using multiple namespaces. This will prevent you from running into validation errors while everything seems configured correctly on your end.
--
--//__Improved help texts on next-generation runtime functionality across the portal__//
--With this release, we have improved several help texts on functionality related to the next-generation runtime that help you while migrating to the next-generation runtime.
--
--== **Bug Fixes** ==
--
--//__Provide correct feedback when a flow is transferred to Deploy for the first time__//
--With this release, we have made several improvements to what feedback is given to the user when moving a flow from Create to Deploy for the first (upon creating your first definitive version). This will ensure that no confusing pop-ups will be shown that are incorrect and only confuse the user further.
--
--//__Show information in the Exception of error messages overview__//
--With this release, we have resolved the bug plaguing this page. As a result, you will again see information on this page when there is information to show.
--
--//__Improve styling of cron trigger configuration pop-up__//
--The styling of this pop-up made it very hard to configure a cron trigger. We have redesigned the styling to make the pop-up readable again.
--
--//__Prevent flow editing locks in specific situations__//
--There were specific situations when switching between Design and Create that could lead to unexpected behavior in the Create phase. This led to a flow editing lock warning to the user. We have solved this problem in this release.
--
--//__Generate property value empties the runtime selection__//
--With this release, we have fixed the bug that emptied the runtime selection upon generating a property value (i.e., password).
--
--//__Make sure nothing of a system message is editable from your exit__//
--Before, you could change part of your system message from your exit (but not everything). This led to confusion. As a result, we have now made sure you cannot edit anything on the system message level from your exit to keep it consistent with our design choices.
--
--//__Prevent users without view rights from seeing a weird screen in those phases__//
--With this release, we have introduced a consistent approach towards what we show a user that has no view rights on a complete phase. This means that you will always see the same information consistently.
--
--//__Name of starting point of the flow test is incorrect__//
--With this release, we have ensured that the name of the starting point of your flow test you see in the "Results" tab is correct.
--
--//__Audit Trail on User Management could break__//
--When performing many changes to user management in Deploy at once, there was a chance the audit trail functionality would give an error blocking you from continuing your update. With this release, we have solved that issue.
--
--//__Progress bar in the license tracker is shown twice__//
--With this release, we have fixed a bug that showed the progress bar twice in the license tracker.
--
--//__Compare flows with support objects in the new flow designer__//
--We have fixed a bug related to support objects that prevented you from comparing two flows when one was built in the latest, and the difference was constructed in the old flow designer.
--
  == **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:
--* [[How to translate CDATA>>https://my.emagiz.com/p/question/172825635703158962||target="blank"]]
--* [[SwaggerUI not found>>https://my.emagiz.com/p/question/172825635703171813||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** ==

Changes for page 207 - Aligned State

Summary

Details

Navigation