Changes for page 216 - Hack Heaven
Last modified by CarlijnKokkeler on 2024/04/18 13:04
From version 415.1
edited by Erik Bakker
on 2024/03/11 15:13
on 2024/03/11 15:13
Change comment:
There is no comment for this version
To version 43.1
edited by Erik Bakker
on 2022/11/08 08:19
on 2022/11/08 08:19
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 216-Hack Heaven1 +187 - Integration Sponsor - Content
-
... ... @@ -1,124 +1,78 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}} 3 -((( 2 +{{container layoutStyle="columns"}}((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 - 6 -**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. 7 7 8 - ==**Announcement-TLS versions deprecated**==5 +**Hi there, eMagiz developers!** This release 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, enabling you to restore your flow to a previous version. 9 9 10 - PlaceholderforinfofromBas7 +== **Store - Next phase** == 11 11 12 - {{info}}Text{{/info}}9 +This release will introduce the next phase of the Store to our whole community. With this new functionality, you can import data model messages (i.e., CDM, API Gateway Data model, or Event Streaming data model) and transformations. Connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce, and others will become even more accessible. 13 13 14 - == **Announcement-Spring6** ==11 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]] 15 15 16 - Placeholderfor info fromJelle13 +{{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}} 17 17 18 - {{warning}}Text{{/warning}}15 +== **New eMagiz Mendix Connector** == 19 19 20 - ==**Infra flow selection**==17 +This release introduces a new version of the eMagiz Mendix Connector. This version (6.0.0) will work with the current runtime architecture and the new runtime architecture making the migration from the existing runtime architecture to the new runtime architecture easier. The latest version of the eMagiz Mendix Connector can be found in the Mendix Marketplace and the eMagiz portal. 21 21 22 - Thisrelease will includea significantupdatetoour releasefunctionality,which allowsyoutoconfigureyourrelease.Presently, eMagizwillallow youtosee changesontheinfra-flow levelvisually.19 +{{info}}Migrating the runtime from the eMagiz portal works the same as for any other runtime. The migration path can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}} 23 23 24 - [[image:Main.Images.ReleaseBlog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]]21 +== **Flow version restore** ~* == 25 25 26 - Ineditmode,youcanselecta newversionvia theright-clickoption,whichyou already usefor otherflows.23 +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. 27 27 28 -[[image:Main.Images.Release Blog.WebHome@release- 216-hack-heaven--infra-flow-selection.png]]25 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]] 29 29 30 -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. 27 +{{warning}}Note that the following restrictions apply when restoring to a previous version: 28 + * Changes made on definition and transformation level are **not** restored 29 + * You will **not** be able to restore to any flow version that was created before October 17th, 2022 30 + * 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 31 + * Your restored flow version will **not** be automatically committed to Deploy{{/warning}} 31 31 32 - [[image:Main.Images.ReleaseBlog.WebHome@release-216-hack-heaven--context-menu-title.png]]33 +== **Feedback items ** == 33 33 34 - ==**Multiple environments selection**==35 +We have also solved other feedback items besides the flow designer's critical updates. 35 35 36 -{{warning}}The following is only applicable under the following conditions: 37 - * Windows 2022 server 38 - * At least one port opened (as a consequence of a hosted web service){{/warning}} 37 +//__Improved help texts Kafka component__// 38 +The help texts on various configuration options and the general help text on multiple Kafka components have been updated to clarify how they work and how you ought to configure them to achieve the best possible result when sending and receiving messages to and from topics within eMagiz. 39 39 40 -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. 40 +//__Improved warning message when Message redelivery cannot be adequately executed__// 41 +We have improved the warning you get when you cannot retrieve the messages waiting to be redelivered. This helps clarify what is going wrong when a user sees this warning. 41 41 42 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]] 43 +//__See Flow Designer errors on the Create overview__// 44 +To improve our offering surrounding the new Flow Designer functionality, we now show on the Create overview which of the flows you still have alerts due to a misconfiguration of the flow. This will help to identify ongoing work much more manageable. 43 43 44 -== **Feedback Items** == 45 -//__Easier component selection in flow designer__// 46 -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. 46 +[[image:Main.Images.Release Blog.WebHome@187-release-blog--alert-visualized-in-create-overview.png]] 47 47 48 -//__Improved handling of optionality in JSON on lists__// 49 -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. 48 +{{info}}Note that you need to open flows that are currently triggering alerts to show the alert on the Create overview{{/info}} 50 50 51 -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. 52 - 53 -//__Loading bar when searching for log entries__// 54 -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. 55 - 56 -//__Improved feedback when deleting elements from Capture__// 57 -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. 58 - 59 -//__Enhanced filter options in Manage__// 60 -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. 61 - 62 -//__Copy property names from Create__// 63 -This release unlocks the possibility of easily copying the name of a property placeholder so it can be used while deploying. 64 - 65 -//__Improved feedback during migration to the current runtime architecture__// 66 -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. 67 - 68 -//__Block user from making changes to their cloud while another upgrade is still in progress__// 69 -We now block users from changing their cloud configuration when another upgrade is ongoing. 70 - 71 -//__Cron trigger validation__// 72 -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. 73 - 74 74 == **Bug Fixes** == 75 -//__Making Edit (and View) the default action when configuring parameters__// 76 -We have made the Edit (and View) button the default action when configuring parameters in a transformation. 77 77 78 -//__ Propertyconfigurationpop-upresized__//79 - Wehave resized thepropertyconfigurationoverviewsto make thepropertyvaluebetterreadable.52 +//__Update Swagger File when changing the order of entities in gateway message__// 53 +In our previous release, we improved how the Swagger file is generated when changing the order of attributes of your gateway message. To make this functionality work for entities, we have made several additional changes to the platform supporting this. 80 80 81 -//__Alphabetically sorted components in the flow designer__// 82 -As of this release, we now sort the components alphabetically in the flow designer. 83 - 84 -//__Improved sorting on runtime overview__// 85 -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. 86 - 87 -//__Improved sorting on catalog overview__// 88 -As of this release, we now sort the topics in the catalog by name. 89 - 90 -//__Styling fix on rich text editors__// 91 -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. 92 - 93 -//__Styling fix on release edit__// 94 -As of this release, the correct icon (green) will be shown when wanting to add a second API operation under the same "header." 95 - 96 -//__Removed false-positive alerts on transformations__// 97 -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. 98 - 99 -//__Event Streaming Graphs - view thirty days back__// 100 -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. 101 - 102 -//__Improved helptext__// 103 -We have improved various help texts across the portal to indicate better what should be filled in for specific fields. 104 - 105 105 == **Fancy Forum Answers** == 106 106 107 107 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: 108 108 109 -* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]] 59 +* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]] 60 +* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]] 61 +* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]] 62 +* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]] 110 110 111 -== **Key Takeaways** ==64 +== **Key takeaways** == 112 112 113 -Thanks to all whohelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:66 +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: 114 114 115 115 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 116 116 * If you have feedback or ideas for us, talk to the Platypus 117 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 70 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 118 118 * Clear your browser cache (Ctrl + Shift + Del) 119 119 * Check out the release notes [here] 120 120 * Start thinking about how the license tracker can aid your development 121 121 * Start thinking about major, minor, and patch 75 +* Upgrade to the latest build number 122 122 * Keep making great integrations 123 123 124 124 Let's stay in touch and till next time! ... ... @@ -126,11 +126,6 @@ 126 126 {{info}} 127 127 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 128 128 129 -{{/info}} 130 -))) 131 - 132 -((( 133 -{{toc/}} 134 -))) 83 +~*~* Indicates a GEN3-only feature. 84 +{{/info}})))((({{toc/}}))){{/container}} 135 135 {{/container}} 136 -{{/container}}