Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 29.1
edited by Erik Bakker
on 2022/10/24 09:03
on 2022/10/24 09:03
Change comment:
There is no comment for this version
To version 131.1
edited by Erik Bakker
on 2023/08/01 13:48
on 2023/08/01 13:48
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 - 186-Daemon Switch1 +202 - New Equilibrium - Content
-
... ... @@ -2,135 +2,74 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** Wehavehitthegroundrunninginthisquarter bynot only focusingon largerfeaturesbutalsospendasubstantialchunk of time on focusingwithusallona lotofsmallerfeedback items andbugs. Alltheseitemswill beprovidedtoyou withthisrelease.Amongthese are flowdesignerimprovements,navigationimprovements,and consistencyimprovements. On top of that,we havemadeournew monitoringstack availabletoafirstsetofmodels.Soletusdiveintoall wehave to offer this time!5 +**Hi there, eMagiz developers!** In the last few weeks, we have crossed our t's and dotted our i's on the release properties functionality that will impact the day to day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that we have several additional smaller feedback item coming from our hackathon efforts that are now released to you. 6 6 7 -== **New monitoring stack** == 7 +== **Release Properties** == 8 +As of this release, we will introduce a new way of handling properties for all our clients. There are several key changes compared to the current way of managing your properties. 8 8 9 - This release will introduce a new monitoring stack that is availablefor models thatrunin the new runtime architectureof eMagiz. With the help of this monitoring stack wehave redesigned various screens in Manage and restructured our alerting approach. For a sneakpreview of what these changes entailplease check out the following microlearnings.10 +{{info}}For more information please check out the following microlearnings: 10 10 11 -* [[Runtime Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-interpreting-runtime-statistics-gen3.WebHome||target="blank"]] 12 -* [[Alerting in eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3.WebHome||target="blank"]] 13 -* [[Queue Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-interpreting-queue-statistics-gen3.WebHome||target="blank"]] 14 -* [[HTTP Statistics>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Advanced monitoring.HTTP Statistics.WebHome||target="blank"]] 12 +* 13 +* 14 +* 15 15 16 -{{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}} 16 +Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 17 +{{/info}} 17 17 18 -== **Transformation Improvements** == 19 +== ** Deploy Architecture - Apply To Environment improvements ** == 20 +As of this release, we will show you a list of all changes about to be changed once you press "Apply to the environment" in Deploy Architecture. This will make it clearer for users, especially those working in teams, what will change when pressing this button. 19 19 20 -//__Toggle between Design and Create__// 21 -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. 22 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]] 22 22 23 - //__ImprovedTransformationoptionsfor booleans__//24 - On top of that,wewillintroduce additionalfunctionalitytotransform"Booleantoenumeration,""enumerationto Boolean,"and"BooleantoBoolean." Just asyou areusedtofor the"enumerationtoenumeration"transformation,youcannowdefinea valuemappingfor eachcombination mentionedabove.Seebelowfor anexample ofhow thislooks.24 +== ** Breadcrumb navigation in eMagiz ** == 25 +This release introduces the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed and impact the Create phase when you check out your transformation or system message on the flow level. Apart from there, the navigation is implemented consistently across the portal for a unified look and feel. 25 25 26 -[[image:Main.Images.Release Blog.WebHome@1 79-release-blog--transformation-options-boolean.png]]27 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]] 27 27 28 -== **Feedback items29 +== **Feedback Items** == 29 29 30 -Apart from the key updates around functionality, we have also solved other feedback items. 31 +//__Improved layout of catalog page in Design__// 32 +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 of several operations. 31 31 32 -//__ Correctlydefinethesizeofa cloudslotwhencreatingitfor thefirsttime__//33 -Currently, e Magizwilllook to Design when creating thecloudslot forthefirsttime.Thisistoavoid youhavingto“create” your solution twice,astherewereinstances where eMagizwouldalwayscreate the cloudslotwith the smallestsizevailablefirst, evenifthis were not whatyou wanted.34 +//__Improved layout of "Edit integration" pop-up for API Gateway integrations__// 35 +Currently, the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration. 34 34 35 -//__ UpdatedinfographicCapture__//36 - As of now, we haveupdated the infographic ontheCapturephase toincorporate thenew look andfeeland explain the updated functionalityin Capture.37 +//__Additional help texts on Design Architecture__// 38 +We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview. 37 37 38 -//__ Updatederrorfeedbackin Design__//39 - Before,you couldseetransformationerrorinDesign eventhough thetransformation was not used in your solution(i.e.,“data pipeline”functionality). However,whenyounowdefinea specificintegrationasadatapipelinesolution,theerror willnotbeshown.40 +//__Improved Audit Trail on several places__// 41 +In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time. 40 40 41 -//__ Improvedstylingof TopicStorage inDesignArchitecture__//42 - When havingalargenumberoftopicsinyourenvironment,thetopicstorage overviewinDesign Architecturewillnowbeimprovedase horizontal scrollbar isgone.43 +//__Removed the erroneous alert on message mapping when having a passthrough API__// 44 +This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API. 43 43 44 -//__Improved styling of error feedback on User Management in Deploy__// 45 -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. 46 - 47 -//__Show only the ten latest flow versions when selecting a flow version in a Release__// 48 -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. 49 - 50 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--ten-latest-flow-versions-release.png]] 51 - 52 -//__Optional Client Secret when using the grant_type Password when calling an OAuth2.0 IDP__// 53 -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. 54 - 55 -//__Clear API Gateway System message__// 56 -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. 57 - 58 -//__Additional information in Property History__// 59 -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. 60 - 61 -//__Save Tag when ready__// 62 -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. 63 - 64 -//__View deployment step information when having view rights__// 65 -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. 66 - 67 -//__Validating external recipients in notification settings__// 68 -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. 69 - 70 -//__Automatically link enumeration list to attribute__// 71 -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. 72 - 73 -//__Approve and go to environment__// 74 -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. 75 - 76 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--approve-and-go-to-environment.png]] 77 - 78 -//__Remove irrelevant information on a runtime in Design Architecture__// 79 -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. 80 - 81 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--container-view.png]] 82 - 83 -//__Add question about message redelivery in Capture__// 84 -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. 85 - 86 -//__Prevent pressing “Apply to environment” multiple times leading to conflicts__// 87 -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. 88 - 89 -//__Add “State” to the topic details in Deploy Architecture__// 90 -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. 91 - 92 -//__Improved stability of logging on the Gen3 Architecture__// 93 -With this release, we have improved the stability of the logging and made sure that the logging is correctly compacted internally. 94 - 95 95 == **Bug Fixes** == 96 96 97 -//__ Various updateswhenimportingstoreitemsinDesign including atransformation__//98 - Withthisrelease,weemadeseveral improvementsforimporting storeitemsinDesign,includinga transformation.Thiswill furtherbolsterourofferingonthis.48 +//__Avoid clicking on other components while deleting another__// 49 +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. 99 99 100 -//__ Openingflowtestingwidgetspecificcircumstances was notworking__//101 -W iththis release,we fixedan issue whereyou couldnotpentheflowtestingfunctionalityin theCreate phasewhenyour flow contained a particular construction combined with the“nullChannel.”51 +//__Improved validation feedback in migrating to the next-generation architecture__// 52 +We have improved the validation feedback when migrating to the next-generation architecture. 102 102 103 -//__ Improvedstylingwhenaddingargemessage toa flow test__//104 - Withthis release,thetylingof thepop-up will notchangewhenyou defineaarge messageasinput(orexpectedoutput) ofyourflowtest.Thiswillensure thatyou can stilleasilyspecify the flowtestmessage’sname anddescriptionafter enteringthelarge message.54 +//__Make sure that user credentials can be viewed with view rights__// 55 +This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights. 105 105 106 -//__ Errors on theUIdootkeepfollowingme__//107 - Before, wehadsomeissues:whenyou navigated awayfrom theAPI Gatewaystatistics page, an errorpop-up wouldkeepfollowingyouthroughouttheplatform.To resolve this issue,youneededtofreshthebrowser.Wehavefixedthisissuepermanentlywiththis release, making the refreshobsolete.57 +//__Refresh behavior within the deployment plan is fixed__// 58 +This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute. 108 108 109 -//__Navigating back to the transformation in Create works again__// 110 -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. 111 - 112 -//__Remove the qualified name when editing a non-legacy Mendix entry in eMagiz__// 113 -With this release, we have removed the possibility of changing the obsolete qualified name when editing a non-legacy Mendix entry in eMagiz. 114 - 115 -//__Selecting tags when drawing a line in Capture__// 116 -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. 117 - 118 -//__Remove invalid selection when configuring a cron trigger via the tooling__// 119 -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. 120 - 121 121 == **Fancy Forum Answers** == 122 122 123 -As always, a gentle reminder to a ll 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:62 +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: 124 124 125 -* [[ Header 'X' with value '0' willnotbeset sincetis not aStringand no Converter is>>https://my.emagiz.com/p/question/172825635700363586||target="blank"]]126 -* [[ Kafka ConsumerMendix String Deserializeris notworking>>https://my.emagiz.com/p/question/172825635700363585||target="blank"]]127 -* [[ Namespaceprefix 'xs' has notbeendeclared>>https://my.emagiz.com/p/question/172825635700363685||target="blank"]]64 +* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]] 65 +* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]] 66 +* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]] 128 128 129 129 == **Key takeaways** == 130 130 131 -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:70 +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: 132 132 133 -* If you have questions surrounding our Program Increment Planning, please get in touch with 72 +* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 134 134 * If you have feedback or ideas for us, talk to the Platypus 135 135 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 136 136 * Clear your browser cache (Ctrl + Shift + Del) ... ... @@ -143,7 +143,7 @@ 143 143 Let's stay in touch and till next time! 144 144 145 145 {{info}} 146 -~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 85 +~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 147 147 148 148 ~*~* Indicates a GEN3-only feature. 149 149 {{/info}})))((({{toc/}}))){{/container}}