Changes for page 216 - Hack Heaven

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

From 39.1 to 40.1 From 412.1 to 413.1

From version 40.1

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

Change comment: There is no comment for this version

To version 412.1

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

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
++216 - Hack Heaven

Content

@@ -1,177 +1,107 @@
  {{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.
--**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.
++== ** Announcement - TLS 1.0 and 1.1 deprecated** ==
--== **Store - Next phase** ==
++Placeholder for info from Bas
--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.
++{{info}}Text{{/info}}
--[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
++== **Announcement - Spring 6** ==
--{{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}}
++Placeholder for info from Jelle
--== **New eMagiz Mendix Connector** ==
++{{warning}}Text{{/warning}}
--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.
++== ** Updated release functionality - Infra flow selection** ==
--{{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}}
++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.
--== **Flow version restore** ~* ==
++[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]
--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.
++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.
--[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
++[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]]
--{{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}}
++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.
--== **Academy improvements** ==
++[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]]
--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.
++== ** Updated deploy functionality on-premise - Multiple environments selection** ==
--[[image:Main.Images.Release Blog.WebHome@186-release-blog--gen3-microlearnings-icon.png]]
++{{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}}
--== **Flow Designer Improvements** ==
++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.
--//__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@release-216-hack-heaven--multiple-environments.png]]
--[[image:Main.Images.Release Blog.WebHome@186-release-blog--change-info.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 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.
--//__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.
++//__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.
--[[image:Main.Images.Release Blog.WebHome@186-release-blog--resource-used-in-other-configs.png]]
++//__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.
--//__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.
++//__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.
--== **Feedback items ** ==
++//__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.
--We have also solved other feedback items besides the flow designer's critical updates.
++//__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.
--//__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.
++//__Improved feedback during migration to the current-runtime architecture__//
++We have improved the feedback should you try to migrate the JMS before any other runtime under Create -> Settings.
--//__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.
++//__Block user from making changes to their cloud whilst another upgrade is still in progress__//
++We now block the user from making changes to their cloud configuration when another upgrade is still in progress.
--[[image:Main.Images.Release Blog.WebHome@186-release-blog--spel-expression-readible.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.
--//__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** ==
++//__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.
--//__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.
++[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
--//__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.
++//__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.
--//__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.
++//__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.
--//__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"]]
++* [[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"]]
--== **Key takeaways** ==
++== **Key Takeaways** ==
--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:
++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 [[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!
@@ -179,6 +179,11 @@
  {{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 GEN3-only feature.
--{{/info}})))((({{toc/}}))){{/container}}
++{{/info}}
++)))
++
++(((
++{{toc/}}
++)))
  {{/container}}
++{{/container}}

Changes for page 216 - Hack Heaven

Summary

Details

Navigation