Changes for page 216 - Hack Heaven
Last modified by CarlijnKokkeler on 2024/04/18 13:04
From version 416.1
edited by Erik Bakker
on 2024/03/11 15:15
on 2024/03/11 15:15
Change comment:
There is no comment for this version
To version 129.1
edited by Erik Bakker
on 2023/07/17 15:10
on 2023/07/17 15:10
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 -21 6-Hack Heaven1 +201 - Be Informed - Content
-
... ... @@ -1,130 +1,73 @@ 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 5 6 -**Hi there, eMagiz developers!** Aspartofour alignmentweek, we also hada hackathoneventfocusingonawidearray ofreportedfeedback onthe portal. Themajority of thereleaseblogwill be focusedon this. On top of that,welaunchnew functionality that makesit easier to transform to JSON, select infraflowsin a release,and deploy multipleagentstoasinglemachinethat adherestospecificconditions. But beforewe dive into all that haschanged, we will publishseveral announcementsviathisreleaseblog (and otherchannels)toprepareyour model for upcoming major changes.5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on planning the upcoming Q and finishing up features of the last Q. More on that later. On top of that we have several smaller items as a result of our hackathon efforts to present to you. 7 7 8 -== ** Announcement - TLS versions deprecated** == 7 +== **Announcement - Release Properties** == 8 +As of the next release (202) we will introduce a completely new way of handling properties for all our clients. In the upcoming weeks we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance please contact us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 9 9 10 -Placeholder for info from Bas 10 +== ** Deploy Architecture - Apply To Environment improvements ** == 11 +As of this release we will show you a list of all change that are about to be changed once you press "Apply to environment" in Deploy Architecture. This will ensure that it becomes clearer for users, especially those working together in teams, what will change when pressing this button. 11 11 12 - {{info}}Text{{/info}}13 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]] 13 13 14 -== **Announcement - Spring 6** == 15 +== ** Breadcrumb navigation in eMagiz ** == 16 +With this release we introduce the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed, and have impact, in the Create phase when you are checking out your transformation or system message on flow level. Apart from there the navigation is implemented consistently across the portal for a unified look and feel. 15 15 16 - In the next release, we expect to release a major version of our current runtime base image. This imagemovestheeMagizstackfrom Java 8 to Java 17, and from SpringFramework 5 to Spring Framework 6. AlthougheMagiz will try to makethe transition as smooth as possible, werecommend that you startwith the followingpreparations.18 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]] 17 17 18 -{{warning}} 19 -* Make sure that your release is running on the latest flow versions. After the release of the new image, eMagiz will push new flow versions of components that have changes. These new flow versions must be included in the subsequent release. Having your release already on the latest flow versions makes this less affecting 20 -* To help you identify which flow versions are especially important here, you can consider all flows that contain any of the following components: Simple job launcher (data pipelines), Job explorer (data pipelines), HTTP components message sender (support object), Web service outbound gateway (with a 'message sender' attribute specified), SFTP session factory (support object), API gateways with OAuth2 as security mechanism. 21 -* We recommend identifying flows with (advanced) custom Groovy scripts. As our Java version changes and the Spring version changes, this may affect the availability of the libraries on the classpath, and therefore the validity of import statements. You can already test the Groovy script using the flow testing functionality as flow testing is already running on the Java 17 and Spring Framework 6 baseline. 22 -* In addition, the groovy version used has been moved from version 3.0.19 to 4.0.18. These changes may affect your scripts as well. These release notes outline the major changes 23 -The code handling SFTP file transfer has been overhauled completely. Although this should not affect you, we encourage you to test your SFTP integrations before deploying to Production.{{/warning}} 24 - 25 - 26 -== **Infra flow selection** == 27 - 28 -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. 29 - 30 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-comparison.png]] 31 - 32 -In edit mode, you can select a new version via the right-click option, which you already use for other flows. 33 - 34 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--infra-flow-selection.png]] 35 - 36 -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. 37 - 38 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--context-menu-title.png]] 39 - 40 -== **Multiple environments selection** == 41 - 42 -{{warning}}The following is only applicable under the following conditions: 43 - * Windows 2022 server 44 - * At least one port opened (as a consequence of a hosted web service){{/warning}} 45 - 46 -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. 47 - 48 -[[image:Main.Images.Release Blog.WebHome@release-216-hack-heaven--multiple-environments.png]] 49 - 50 50 == **Feedback Items** == 51 -//__Easier component selection in flow designer__// 52 -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. 53 53 54 -//__Improved handlingofoptionalityinJSON on lists__//55 - Previously,eMagizalwayscreatedaJSONarrayifyourdata modelexpected a list.Thisledtounexpected andundesirablebehavior ofthe message,asempty arraysare notalwaysaccepted by external parties.22 +//__Improved layout of catalog page in Design__// 23 +We have improved the layout of the API Catalog overview in Design for our API Gateway users. Among others, we have introduced a scrollbar to get a better overview when having several operations. 56 56 57 -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. 25 +//__Improved layout of "Edit integration" pop-up for API Gateway integrations__// 26 +As of now the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration. 58 58 59 -//__ Loading barwhensearchingforlog entries__//60 - Toindicateto theuserthateMagizisstillbusyretrievinglog entries,wehaveaddedaloadingbarto the logentryoverviewupon pressing search.28 +//__Additional help texts on Design Architecture__// 29 +We have improved the help texts in Design Archicture in relation to the Event Streaming topic storage overview. 61 61 62 -//__Improved feedbackwhendeleting elements from Capture__//63 - Tobetterspecify to theuserwhich integrationor system theuserintends to delete,we have improved thetextintheconfirmationpop-up.Thisway,wecanprovidemore informationtotheuser toavoidmistakes.31 +//__Improved Audit Trail on several places__// 32 +In several places in the portal we have improved the audit trail to better specify who changed what at which point in time. 64 64 65 -//__ Enhancedfilter options inManage__//66 - Withthis release,wehaveadded filter optionson boththeAlerting tab and the Trigger configuration pop-up. This allows userstofilteron Status (Alerting)andQueues, Topics,Recipients,andmore(Triggerconfigurationpop-up)intheseplaces.34 +//__Removed the erroneous alert on message mapping when having a passthrough API__// 35 +This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API. 67 67 68 -//__Copy property names from Create__// 69 -This release unlocks the possibility of easily copying the name of a property placeholder so it can be used while deploying. 70 - 71 -//__Improved feedback during migration to the current runtime architecture__// 72 -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. 73 - 74 -//__Block user from making changes to their cloud while another upgrade is still in progress__// 75 -We now block users from changing their cloud configuration when another upgrade is ongoing. 76 - 77 -//__Cron trigger validation__// 78 -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. 79 - 80 80 == **Bug Fixes** == 81 -//__Making Edit (and View) the default action when configuring parameters__// 82 -We have made the Edit (and View) button the default action when configuring parameters in a transformation. 83 83 84 -//__ Propertyconfigurationpop-upresized__//85 - Wehaveresizedthepropertyconfigurationoverviewstomake the propertyvaluebetterreadable.39 +//__Avoid clicking on other components while deleting another__// 40 +To avoid unexpected behavior we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer. 86 86 87 -//__ Alphabetically sortedcomponentsin theflow designer__//88 - Asofthis release,we nowsortthecomponentsalphabeticallyin theflow designer.42 +//__Improved validation feedback in migrating to the next-generation architecture__// 43 +We have improved several things with regards to the validation feedback when migrating to the next-generation architecture. 89 89 90 -//__ Improvedsortingonruntimeoverview__//91 - As of this release,wenowsortthe runtimesintheruntimeoverviewcorrectlyby time.This meansthat theruntime witha changedstatus,closest to the current date andtime, is shownat the top ofthelist. This shouldreduce thechance of overlookinga criticalmistake.45 +//__Make sure that user credentials can be viewed with view rights__// 46 +This release makes sure that the user credentials in Deploy can be viewed with view rights and not only when having edit rights. 92 92 93 -//__ Improvedsortingoncatalogoverview__//94 - As of this release,wenowsort thetopicsin thecatalogbyname.48 +//__Refresh behavior within the deployment plan is fixed__// 49 +This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute. 95 95 96 -//__Styling fix on rich text editors__// 97 -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. 98 - 99 -//__Styling fix on release edit__// 100 -As of this release, the correct icon (green) will be shown when wanting to add a second API operation under the same "header." 101 - 102 -//__Removed false-positive alerts on transformations__// 103 -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. 104 - 105 -//__Event Streaming Graphs - view thirty days back__// 106 -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. 107 - 108 -//__Improved helptext__// 109 -We have improved various help texts across the portal to indicate better what should be filled in for specific fields. 110 - 111 111 == **Fancy Forum Answers** == 112 112 113 113 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: 114 114 115 -* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]] 55 +* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]] 56 +* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]] 57 +* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]] 116 116 117 -== **Key Takeaways** ==59 +== **Key takeaways** == 118 118 119 -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:61 +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: 120 120 121 121 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 122 122 * If you have feedback or ideas for us, talk to the Platypus 123 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 65 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 124 124 * Clear your browser cache (Ctrl + Shift + Del) 125 125 * Check out the release notes [here] 126 126 * Start thinking about how the license tracker can aid your development 127 127 * Start thinking about major, minor, and patch 70 +* Upgrade to the latest build number 128 128 * Keep making great integrations 129 129 130 130 Let's stay in touch and till next time! ... ... @@ -132,11 +132,6 @@ 132 132 {{info}} 133 133 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 134 134 135 -{{/info}} 136 -))) 137 - 138 -((( 139 -{{toc/}} 140 -))) 78 +~*~* Indicates a GEN3-only feature. 79 +{{/info}})))((({{toc/}}))){{/container}} 141 141 {{/container}} 142 -{{/container}}