Changes for page 216 - Hack Heaven

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

From 27.1 to 28.1 From 415.1 to 416.1

From version 28.1

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

Change comment: There is no comment for this version

To version 415.1

edited by Erik Bakker
on 2024/03/11 15:13

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 @@
--186 - Daemon Switch
++216 - Hack Heaven

Content

@@ -1,150 +1,136 @@
  {{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, 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.
--**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!
++== ** Announcement - TLS versions deprecated** ==
--== **New monitoring stack** ==
++Placeholder for info from Bas
--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.
++{{info}}Text{{/info}}
--* [[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-interpreting-runtime-statistics-gen3.WebHome||target="blank"]]
--* [[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"]]
++== **Announcement - Spring 6** ==
--{{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}}
++Placeholder for info from Jelle
--== **Transformation Improvements** ==
++{{warning}}Text{{/warning}}
--//__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.
++== **Infra flow selection** ==
--//__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.
++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.
--[[image:Main.Images.Release Blog.WebHome@179-release-blog--transformation-options-boolean.png]]
++[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
--== **Feedback items ** ==
++In edit mode, you can select a new version via the right-click option, which you already use for other flows.
--Apart from the key updates around functionality, we have also solved other feedback items.
++[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
--//__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.
++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.
--//__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.
++[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
--//__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.
++== **Multiple environments selection** ==
--//__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.
++{{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}}
--//__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.
++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.
--//__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.
++[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]]
--[[image:Main.Images.Release Blog.WebHome@179-release-blog--ten-latest-flow-versions-release.png]]
++== **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.
--//__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.
++//__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.
--//__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.
++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.
--//__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.
++//__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.
--//__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.
++//__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.
--//__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.
++//__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.
--//__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.
++//__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.
--//__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.
++//__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.
--//__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.
++//__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.
--[[image:Main.Images.Release Blog.WebHome@179-release-blog--approve-and-go-to-environment.png]]
++//__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.
--//__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.
--
--[[image:Main.Images.Release Blog.WebHome@179-release-blog--container-view.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.
--
--//__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.
--
--//__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.
--
--//__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.
--
  == **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.
--//__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.
++//__Property configuration pop-up resized__//
++We have resized the property configuration overviews to make the property value better readable.
--//__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.”
++//__Alphabetically sorted components in the flow designer__//
++As of this release, we now sort the components alphabetically in the flow designer.
--//__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.
++//__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.
--//__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.
++//__Improved sorting on catalog overview__//
++As of this release, we now sort the topics in the catalog by name.
--//__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.
++//__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.
--//__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.
++//__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."
--//__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.
++//__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.
--//__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.
++//__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, 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"]]
++* [[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 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 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
++* 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!
  {{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}}
++{{/info}}
++)))
++
++(((
++{{toc/}}
++)))
  {{/container}}
++{{/container}}

Changes for page 216 - Hack Heaven

Summary

Details

Navigation