Changes for page 194 - Giant Leap

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

From 28.1 to 29.1 From 33.1 to 34.1

From version 29.1

edited by Erik Bakker
on 2022/10/24 09:03

Change comment: There is no comment for this version

To version 33.1

edited by Erik Bakker
on 2022/10/24 11:13

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -2,11 +2,11 @@
  {{container layoutStyle="columns"}}(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**Hi there, eMagiz developers!** We have hit the ground running in this quarter by not only focusing on larger features but also spend a substantial chunk of time on focusing with us all on a lot of smaller feedback items and bugs. All these items will be provided to you with this release. Among these are flow designer improvements, navigation improvements, and consistency improvements. On top of that, we have made our new monitoring stack available to a first set of models. So let us dive into all we have to offer this time!
++**Hi there, eMagiz developers!** We have hit the ground running this quarter by focusing on more prominent features and spending a substantial chunk of time focusing with us all on a lot of smaller feedback items and bugs. All these items will be provided to you with this release. Among these are flow designer improvements, navigation improvements, and consistency improvements. On top of that, we have made our new monitoring stack available to the first set of models. So let us dive into all we have to offer this time!
  == **New monitoring stack** ==
--This release will introduce a new monitoring stack that is available for models that run in the new runtime architecture of eMagiz. With the help of this monitoring stack we have redesigned various screens in Manage and restructured our alerting approach. For a sneak preview of what these changes entail please check out the following microlearnings.
++This release will introduce a new monitoring stack available for models that run in the new runtime architecture of eMagiz. With the help of this monitoring stack, we have redesigned various screens in Manage and restructured our alerting approach. For a sneak preview of these changes, please check out the following microlearnings.
  * [[Runtime Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-interpreting-runtime-statistics-gen3.WebHome||target="blank"]]
  * [[Alerting in eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3.WebHome||target="blank"]]
@@ -13,124 +13,143 @@
  * [[Queue Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-interpreting-queue-statistics-gen3.WebHome||target="blank"]]
  * [[HTTP Statistics>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Advanced monitoring.HTTP Statistics.WebHome||target="blank"]]
--{{info}}Note that the new monitoring stack is only available for models that run the new runtime architecture. Should you wish to become an early adopter please contact us at productmanagement@emagiz.com to discuss the possibilities{{/info}}
++{{info}}Note that the new monitoring stack is only available for models that run the new runtime architecture. Should you wish to become an early adopter, don't hesitate to get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] to discuss the possibilities{{/info}}
--== **Transformation Improvements** ==
++== **Academy improvements** ==
--//__Toggle between Design and Create__//
--This release will introduce a toggle that allows you to quickly navigate between the Create Transformation and the Design Message Mapping. In both Create as Design, a new button is added on the transformation level that allows you to open the transformation in Design (or Create) depending on where you are currently. This should make navigating easier when you make a mistake or forget something in Design.
++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.
--//__Improved Transformation options for booleans__//
--On top of that, we will introduce additional functionality to transform "Boolean to enumeration," "enumeration to Boolean," and" Boolean to Boolean." Just as you are used to for the "enumeration to enumeration" transformation, you can now define a value mapping for each combination mentioned above. See below for an example of how this looks.
++[[image:Main.Images.Release Blog.WebHome@186-release-blog--gen3-microlearnings-icon.png]]
--[[image:Main.Images.Release Blog.WebHome@179-release-blog--transformation-options-boolean.png]]
++== **Flow Designer 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.
++
++[[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 ** ==
--Apart from the key updates around functionality, we have also solved other feedback items.
++We have also solved other feedback items besides the flow designer's critical updates.
--//__Correctly define the size of a cloud slot when creating it for the first time__//
--Currently, eMagiz will look to Design when creating the cloud slot for the first time. This is to avoid you having to “create” your solution twice, as there were instances where eMagiz would always create the cloud slot with the smallest size available first, even if this were not what you wanted.
++//__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.
--//__Updated infographic Capture__//
--As of now, we have updated the infographic on the Capture phase to incorporate the new look and feel and explain the updated functionality in Capture.
++//__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.
--//__Updated error feedback in Design__//
--Before, you could see a transformation error in Design even though the transformation was not used in your solution (i.e., “data pipeline” functionality). However, when you now define a specific integration as a data pipeline solution, the error will not be shown.
++[[image:Main.Images.Release Blog.WebHome@186-release-blog--spel-expression-readible.png]]
--//__Improved styling of Topic Storage in Design Architecture__//
--When having a large number of topics in your environment, the topic storage overview in Design Architecture will now be improved as the horizontal scrollbar is gone.
++//__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.
--//__Improved styling of error feedback on User Management in Deploy__//
--With this release we have improved the styling of the feedback pop-up you get in User management after pressing “Apply to environment” and several updates could not be executed.
++//__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.
--//__Show only the ten latest flow versions when selecting a flow version in a Release__//
--To improve the quality and speed of defining a release, we will show only the latest ten versions of a flow in the release widget, as these ten are most likely to be selected by a user. If you need an older version, you can add it via the “Details” option on the release.
++//__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.
--[[image:Main.Images.Release Blog.WebHome@179-release-blog--ten-latest-flow-versions-release.png]]
++//__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.
--//__Optional Client Secret when using the grant_type Password when calling an OAuth2.0 IDP__//
--Before, you needed to define the Client Secret even for the grant_type Password, where it is not always required. We have corrected this behavior to ensure that this is in line with the OAuth 2.0 specification.
++//__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.
--//__Clear API Gateway System message__//
--With this release, we have added the Clear button that you already know from the messaging pattern to the API Gateway system message. This unifies the options between the two patterns in Design on the system message level.
++//__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.
--//__Additional information in Property History__//
--To improve the usability of the property history page in Deploy, we now also show the runtime on which a particular property is changed. This is particularly useful when changing the same property used on different runtimes.
++//__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.
--//__Save Tag when ready__//
--With this release, we have made it explicit that when you want to change the name of a tag, you first need to press the “Save” button before the change is actualized within your model.
++//__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.
--//__View deployment step information when having view rights__//
--With this release, we have made it possible to view not only the deployment steps but also the detailed information of each deployment step when you only have view rights on a specific environment.
++//__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.
--//__Validating external recipients in notification settings__//
--Before pressing save, we will now validate what you entered in the external recipients setting to ensure that what is entered there are valid values.
++//__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.
--//__Automatically link enumeration list to attribute__//
--When you create an enumeration list relevant to a particular attribute, eMagiz will now automatically link the two together without you having to do this manually.
++{{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}}
--//__Approve and go to environment__//
--With this release, we will provide you with the option to approve a release to a specific environment and let eMagiz directly take you to that environment.
++//__"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.
--[[image:Main.Images.Release Blog.WebHome@179-release-blog--approve-and-go-to-environment.png]]
++//__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.
--//__Remove irrelevant information on a runtime in Design Architecture__//
--We have removed all irrelevant information for a user when you enter the details view of a runtime in Design Architecture. The information that is still shown is visualized below.
++//__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@179-release-blog--container-view.png]]
++[[image:Main.Images.Release Blog.WebHome@186-release-blog--topic-storage-info.png]]
--//__Add question about message redelivery in Capture__//
--When you use the message redelivery functionality, and it is relevant to consider whether it will be helpful when sending data to the system, you will now see an additional question in Capture. This question should trigger a thinking process on handling message redelivery for that specific solution.
++//__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.
--//__Prevent pressing “Apply to environment” multiple times leading to conflicts__//
--With this release, we have improved this functionality to verify whether an update is currently being executed. If this is true, all other times, you push the button; you will be notified that the process is still running. This is done to avoid potential conflicts if a user presses the "Apply to environment" button more than once in a short period.
++//__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.
--//__Add “State” to the topic details in Deploy Architecture__//
--Based on your feedback, we have improved the topic details overview to include the “State” of a topic. Each topic can be “Unchanged,” “Changed,” “Deleted,” or “New.” Based on this state, you can determine which topics will be added, changed, deleted, or remain untouched.
++//__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 stability of logging on the Gen3 Architecture__//
--With this release, we have improved the stability of the logging and made sure that the logging is correctly compacted internally.
++//__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** ==
--//__Various updates when importing store items in Design including a transformation__//
--With this release, we have made several improvements for importing store items in Design, including a transformation. This will further bolster our offering on this.
++//__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.
--//__Opening flow testing widget in specific circumstances was not working__//
--With this release, we fixed an issue where you could not open the flow testing functionality in the Create phase when your flow contained a particular construction combined with the “nullChannel.”
++//__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 styling when adding a large message to a flow test__//
--With this release, the styling of the pop-up will not change when you define a large message as input (or expected output) of your flow test. This will ensure that you can still easily specify the flow test message’s name and description after entering the large message.
++//__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.
--//__Errors on the UI do not keep following me__//
--Before, we had some issues: when you navigated away from the API Gateway statistics page, an error pop-up would keep following you throughout the platform. To resolve this issue, you needed to refresh the browser. We have fixed this issue permanently with this release, making the refresh obsolete.
++//__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.
--//__Navigating back to the transformation in Create works again__//
--With this release, we have squashed a bug that annoyed users. Before, it could happen that when you navigated away from the transformation page in your flow in Create and returned later, the transformation was not shown anymore. With this release, we have made sure that regardless of where you come from, the transformation will be visible for you to see.
++//__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).
--//__Remove the qualified name when editing a non-legacy Mendix entry in eMagiz__//
--With this release, we have removed the possibility of changing the obsolete qualified name when editing a non-legacy Mendix entry in eMagiz.
++//__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.
--//__Selecting tags when drawing a line in Capture__//
--We have now made this possible (again). This way, you can directly select the tag(s) you want instead of opening the detailed information on the line after it is already added to Capture.
++//__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.
--//__Remove invalid selection when configuring a cron trigger via the tooling__//
--With this release, we have removed invalid selection options presented to you when you used the configuration option on a property of type cron to let eMagiz define the cron trigger value. This is to avoid unwanted surprises when deploying your solution.
++//__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, a gentle reminder to all 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:
++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:
--* [[Header 'X' with value '0' will not be set since it is not a String and no Converter is>>https://my.emagiz.com/p/question/172825635700363586||target="blank"]]
--* [[Kafka Consumer Mendix String Deserializer is not working>>https://my.emagiz.com/p/question/172825635700363585||target="blank"]]
--* [[Namespace prefix 'xs' has not been declared>>https://my.emagiz.com/p/question/172825635700363685||target="blank"]]
++* [[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"]]
  == **Key takeaways** ==
--Thanks to all that help build, 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
++* 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.
  * Clear your browser cache (Ctrl + Shift + Del)
@@ -143,7 +143,7 @@
  Let's stay in touch and till next time!
  {{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 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}}

Changes for page 194 - Giant Leap

Summary

Details

Navigation