Changes for page 207 - Aligned State

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

From 37.1 to 38.1 From 125.1 to 126.1

From version 38.1

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

Change comment: There is no comment for this version

To version 125.1

edited by Erik Bakker
on 2023/06/19 14:24

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
++200 - Uncharted Territories

Content

@@ -2,150 +2,52 @@
  {{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 few weeks, we have worked hard on a lot of things that are unfortanetly not quite ready to be released. As a result the ouput of this release is limited. Having said that we still bring some key improvements in the Deploy and Manage phase that would make life much easier.
--== **Store - Next phase** ==
++== **Next generation improvements and bug fixes** ==
--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. 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"]].
++//__Enhanced right-hand view within Deployment Plan context__//
++When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview.
--== **Flow version restore** ~* ==
++{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}}
--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.
++//__Improved timeout settings when deploying__//
++To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur.
--{{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{{/warning}}
++{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
--== **Academy improvements** ==
++//__Detailed HTTP Statistics now show user info in specific additional cases__//
++To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations.
--On top of that, we have added various microlearnings to our academy offering available on docs.emagiz.com related to the new runtime architecture. You can identify these microlearnings by looking at the following icon in front of a microlearning.
++{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
--[[image:Main.Images.Release Blog.WebHome@186-release-blog--gen3-microlearnings-icon.png]]
++//__Improved loading speed of Manage Dashboard__//
++This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase.
--== **Flow Designer Improvements** ==
++== **Store Improvements** ==
--//__See last changed date and changed by on resource level__//
--This release will reinstate the ability to see who changed a resource last and when it was changed for the last time. You can find this information by double-clicking on a resource or viewing its details via the view button.
++//__Importing in Design is improved__//
++We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create.
--[[image:Main.Images.Release Blog.WebHome@186-release-blog--change-info.png]]
--
--//__See on which other flows a resource is used__//
--This release will reinstate the ability to see whether a resource is used in other flows within your model or not. This will help to determine the impact of a specific change.
--
--[[image:Main.Images.Release Blog.WebHome@186-release-blog--resource-used-in-other-configs.png]]
--
--//__Toggle option to see the generated resource by default__//
--Upon request, we have made the toggle for the generated resources in the new flow designer user-dependent. This means that you, as a user, can determine that the toggle should also be on. This means that the generated resources will be shown to you when opening any flow in eMagiz. When you switch the toggle off, this will mean that you will **not** see the generated resources by default.
--
--== **Feedback items ** ==
--
--We have also solved other feedback items besides the flow designer's critical updates.
--
--//__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.
--
--//__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.
--
--[[image:Main.Images.Release Blog.WebHome@186-release-blog--spel-expression-readible.png]]
--
--//__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.
--
--//__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.
--
--//__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.
--
--//__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.
--
--//__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.
--
--//__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.
--
--//__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.
--
--//__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.
--
--//__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.
--
--//__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.
++//__Deprecated reminder pop-up removed__//
++We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems.
--//__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.
++//__Improved selection area in Flow Designer__//
++When working on a large flow you can now select specific areas easily while you are scrolled down furhter down the flow.
--//__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.
++//__Improved Kafka settings_//
++For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them.
--//__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.
++{{info}}We stronly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}}
--//__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"]]
++* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]]
++* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||target="blank"]]
  == **Key takeaways** ==

Changes for page 207 - Aligned State

Summary

Details

Navigation