Changes for page 216 - Hack Heaven
Last modified by CarlijnKokkeler on 2024/04/18 13:04
From version 42.1
edited by Erik Bakker
on 2022/11/07 16:43
on 2022/11/07 16:43
Change comment:
There is no comment for this version
To 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
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -1 87-IntegrationSponsor1 +216 - Hack Heaven - Content
-
... ... @@ -1,74 +1,124 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}}((( 2 +{{container layoutStyle="columns"}} 3 +((( 3 3 [[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. 4 4 5 - **Hithere, eMagiz developers!**With this release we will release several impactful features and enablers toourcommunity. Among others thenextphaseof the eMagizStorewill become publicly available. This means that you can now import data modelsand transformationon top ofsystemmessages in Design andaccelerators in Create. Furthermore, we will launchanew Beta functionality through someof our clients that will enable you to restore your flow to a previous version.8 +== ** Announcement - TLS versions deprecated** == 6 6 7 - ==**Store-Nextphase** ==10 +Placeholder for info from Bas 8 8 9 - This release will introduce the next phase ofthe 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 ExactOnline, Microsoft Graph, Salesforce and others will become even easier.12 +{{info}}Text{{/info}} 10 10 11 - [[image:Main.Images.ReleaseBlog.WebHome@187-release-blog--current-store-offering.png]]14 +== **Announcement - Spring 6** == 12 12 13 - {{info}}For more information on the Store pleasecheck out this [[course>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagizStore.WebHome||target="blank"]].As a reminder youcanfind all documentationon all availableStore content published by eMagiz [[here>>doc:Main.eMagiz Store.WebHome||target="blank"]].{{/info}}16 +Placeholder for info from Jelle 14 14 15 - == **NeweMagiz Mendix Connector** ==18 +{{warning}}Text{{/warning}} 16 16 17 - Withthis release we introduceanew version ofthe eMagiz Mendix Connector.Thisversion (6.0.0) will work both with thecurrentruntime architecture and the new runtime architecture making the migrationfrom 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.20 +== **Infra flow selection** == 18 18 19 - {{info}}Migrating theruntimefrom theeMagizportalworksthesameas for anyother runtime. Themigrationpathtomigratecan be found[[here>>doc:Main.eMagizSupport.MigrationPaths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}}22 +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. 20 20 21 - ==**Flow versionrestore** ~* ==24 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]] 22 22 23 - On topof that wewill alsolauncha newBetafeatureto thecommunity thatallowsyou to restore your flow to aprevious version.Thiswayyoucan quickly undo changesmade that wereincorrect.26 +In edit mode, you can select a new version via the right-click option, which you already use for other flows. 24 24 25 -[[image:Main.Images.Release Blog.WebHome@ 187-release-blog--flow-version-restore.png]]28 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]] 26 26 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}} 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. 32 32 33 - == **Feedbackitems ** ==32 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]] 34 34 35 - Wehave also solvedotherfeedback itemsbesides the flow designer'scriticalupdates.34 +== **Multiple environments selection** == 36 36 37 -//__Improved help texts Kafka component__// 38 -TBA 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}} 39 39 40 -//__Improved warning message when Message redelivery cannot be properly executed__// 41 -TBA 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. 42 42 43 -//__See Flow Designer errors on the Create overview__// 44 -TBA 42 +[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]] 45 45 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. 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. 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 + 46 46 == **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. 47 47 48 -//__ UpdateSwaggerFile whenchangingorder of entities ingatewaymessage__//49 - TBA78 +//__Property configuration pop-up resized__// 79 +We have resized the property configuration overviews to make the property value better readable. 50 50 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 + 51 51 == **Fancy Forum Answers** == 52 52 53 53 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: 54 54 55 -* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]] 56 -* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]] 57 -* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]] 58 -* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]] 109 +* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]] 59 59 60 -== **Key takeaways** ==111 +== **Key Takeaways** == 61 61 62 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:113 +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: 63 63 64 64 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 65 65 * If you have feedback or ideas for us, talk to the Platypus 66 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 117 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 67 67 * Clear your browser cache (Ctrl + Shift + Del) 68 68 * Check out the release notes [here] 69 69 * Start thinking about how the license tracker can aid your development 70 70 * Start thinking about major, minor, and patch 71 -* Upgrade to the latest build number 72 72 * Keep making great integrations 73 73 74 74 Let's stay in touch and till next time! ... ... @@ -76,6 +76,11 @@ 76 76 {{info}} 77 77 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 78 78 79 -~*~* Indicates a GEN3-only feature. 80 -{{/info}})))((({{toc/}}))){{/container}} 129 +{{/info}} 130 +))) 131 + 132 +((( 133 +{{toc/}} 134 +))) 81 81 {{/container}} 136 +{{/container}}