Changes for page 207 - Aligned State
Last modified by Carlijn Kokkeler on 2024/04/18 13:10
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 101.1
edited by Erik Bakker
on 2023/04/13 08:56
on 2023/04/13 08:56
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 86-DaemonSwitch1 +195 - Easter Party - Content
-
... ... @@ -2,135 +2,99 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** Wehavehitthegroundrunninginthis quarterbynotonlyfocusingonlarger featuresbutalsospendasubstantialchunkof timeonfocusingwithus allonalot ofsmaller feedback items and bugs.Alltheseitems will beprovidedto you with thisrelease.Amongtheseareflowdesignerimprovements,navigation improvements,and consistency improvements.Ontopofthat, wehavemadeournewmonitoringstack availabletoafirstsetof models. So letusdiveintoallwehave tooffer thistime!5 +**Hi there, eMagiz developers!** In the last few weeks, we have focused on wrapping up the previous quarter and starting the new one. When this happens, we go silent for a few weeks to plan for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with excellent spirit after solving several smaller feedback items and bugs reported by you. Several of those stories will be included in this and the upcoming release. On top of that, we introduce various improvements to our API Gateway pattern and our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the multiple improvements. 6 6 7 -== ** Newmonitoringstack** ==7 +== **Release properties** ==** 8 8 9 - This release willintroduceaewmonitoringstackthatis availableformodelsthat runin the newruntime architectureofeMagiz.With the helpofthismonitoringstack wehave redesignedvariousscreensinManageandrestructured ouralertingapproach.For asneakpreviewofwhat these changesilpleasecheck outthe followingmicrolearnings.9 +With this release we bring an improved version of the release properties functionality. With the introduction of the 3rd generation runtime the way properties can be updated and when they need to be available for the solution to start up has changed compared to the current runtime architecture. More on that can be found [[here>>Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target= "blank"]]. 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"]] 11 +As of now you can not only view all property values related to a specific release by pressing the wrench icon. You can also create what we call a "property release" on each of the three environment that allows you to quickly change one or more property values and deploy the changes to your environment. When deploying such a release eMagiz will check on which runtimes the properties are used and only execute the deploy actions for the machines to which said runtime(s) belong(s). 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}} 13 +{{info}}The following considerations need to be taken into account when using this functionality: 14 +* This functionality works from the moment one runtime is running on the 3rd generation runtime architecture 15 +* This functionality can only change property values. Functional changes need a seperate release that needs to be promoted 16 +* In comparison to standard releases a property release can be created on each environment (as the property value is linked to a specific environment). 17 +*{{/info}} 17 17 18 -== ** TransformationImprovements** ==19 +== **API improvements** == 19 19 20 -//__ TogglebetweenDesignandCreate__//21 - This release will introduceogglethatallows you to quicklynavigatebetweentheCreate Transformationand the DesignMessageMapping.Inboth CreatesDesign,anewbutton is added on the transformation level that allowsyouto openthetransformationin Design(orCreate)dependingon whereyou arecurrently. Thisshould makenavigatingeasierwhenyou make a mistake orforgetsomething in Design.21 +//__Improved auto-generated error handling__// 22 +When you create a new operation in your API gateway, eMagiz will now automatically generate the correct schemas, HTTP codes, and examples for this operation based on industry standards. 22 22 23 -//__ ImprovedTransformationoptions forbooleans__//24 - Ontop of that, wewill introduceadditionalfunctionalitytotransform"Booleantoenumeration," "enumerationtoBoolean,"and" Booleanto Boolean."Justasyou areusedtoforthe"enumerationtoenumeration"transformation,youcannowdefineavaluemappingforeachcombinationmentionedabove.Seebelowforan exampleofhowthislooks.24 +//__Switch default message format__// 25 +We have improved the logic when you switch the message format of your gateway message from XML to JSON or vice versa. As a result, the Swagger file will be changed accordingly. Once you update the relevant flow in Create and deploy the solution, the Swagger UI will automatically match the expected result. 25 25 26 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--transformation-options-boolean.png]] 27 +//__Re-using elements in gateway message__// 28 +This release improves how the examples and schemas in Swagger and the Flow Testing functionality are generated when certain elements repeatedly appear in different places within one specific gateway message. 27 27 28 -== **Feedback items ** == 30 +//__Improved naming of API operations when adding integrations to Create__// 31 +Previously when you added API operations to the Create phase, the HTTP operation (i.e., POST, PUT, GET) was not visible to a user. As a result, it became tough for a user to discern between specific operations once multiple of them were used on one resource (i.e., Order, Invoice, Lead). To clarify this for the user, the display name defined in Design (instead of Capture) is now used within this overview for these operations. 29 29 30 - Apartfromthekey updates aroundfunctionality, we havealso solved other feedback items.33 +== **3rd generation improvements** == 31 31 32 -//__ Correctlydefinethe sizeofacloud slot when creatingit for thefirst time__//33 - Currently,eMagizwill look to Designwhencreating thecloudslotforthefirstme.Thisisto avoid youhavingto“create” yoursolutiontwice,astherewere instanceswhere eMagizwouldalwayscreatethe cloudslotwiththe smallestsize availablefirst,evenif this werenotwhatyouwanted.35 +//__Update of the static alerting engine__// 36 +In this release, we have updated the static alerting engine that determines when one of the static alerts, as defined by eMagiz, should be triggered (or not). This change will improve the performance of the solution and will ensure that the alerts are activated correctly. 34 34 35 -//__ Updatedinfographic Capture__//36 - Asofnow, we haveupdatedthegraphicontheCapturephasetoincorporate thenewlookndfeel andexplain theupdatedfunctionalityinCapture.38 +//__Add "Data pipeline" functionality__// 39 +This release introduces the "data pipeline" functionality to the 3rd generation runtime. This removes another blockage for models waiting on this before migrating to the 3rd generation runtime. 37 37 38 -//__ Updatederrorfeedbackin Design__//39 - Before, you could seeatransformationerrorinDesigneventhoughthe transformationwasnotused in yourolution(i.e.,“datapipeline”functionality). However,whenyounow definea specific integrationasa datapipelinesolution,the error will notbeshown.41 +//__Fix related to the debugger__// 42 +This release introduces a fix that allows users to debug a flow once the toggle "Send error messages to eMagiz" is activated. 40 40 41 -//__Improved styling of Topic Storage in Design Architecture__// 42 -When having a large number of topics in your environment, the topic storage overview in Design Architecture will now be improved as the horizontal scrollbar is gone. 44 +{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}} 43 43 44 -//__Improved stylingof error feedback on User ManagementDeploy__//45 - Withthis releasewe haveimprovedthestylingofthe feedbackpop-upyouget in User managementafterpressing“Applyto environment”andseveral updatescouldnotbexecuted.46 +//__Improved migration process__// 47 +This release introduced a fix that allows a user to migrate event processors with custom error handling without manual intervention. 46 46 47 -//__ Show onlythetenlatestflow versionswhenselectinga flow version in a Release__//48 - Toimprove thequality and speedof defining arelease,we willshow onlythelatestenversions ofaflowintherelease widget, as these tenaremostlikelyto be selected by a user. Ifyouneedan olderversion,you canadd itvia the“Details”option onthe release.49 +//__Deployment plan change__// 50 +In this release, the prepare release step will not start automatically anymore. This prevents the user from waiting for this action to be finished before they can continue deploying the solution to their environment. 49 49 50 - [[image:Main.Images.ReleaseBlog.WebHome@179-release-blog--ten-latest-flow-versions-release.png]]52 +{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}} 51 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 +== **Feedback items ** == 54 54 55 -//__ ClearAPI GatewaySystemmessage__//56 -With this release, we have added theClearbuttonthatyou alreadyknowfromthemessagingpatternto theAPI Gatewaysystemmessage.This unifiesthe optionsbetween thetwo patternsinDesignonthe system message level.56 +//__License Tracker improvements__// 57 +With this release, we have added several new features available to purchase. On top of that, additional information on the license, such as adding notes and seeing the data sink packets, is now available. 57 57 58 -//__A dditionalinformationin PropertyHistory__//59 - To improveheusabilityoftheproperty history page inDeploy, wenowalsoshowthe runtimeon whichaparticularpropertyis changed.Thisisparticularlyuseful whenchangingthe same propertyused ondifferentruntimes.59 +//__Ability to view the message definition for a topic__// 60 +Currently, you can easily navigate to the message definition of a topic via the context menu in Design, even if there is no event processor linked to the topic. 60 60 61 -//__ SaveTagwhenready__//62 - Withthisrelease,wehavemadeit explicitthat whenyouwanttochange thename ofatag,youfirst needtopressthe“Save”button before thechangeis actualizedwithinyourmodel.62 +//__Restricted access for uploading custom certificates to endpoints__// 63 +To improve our cloud offerings' general security and prevent users from uploading the wrong certificates, we have now restricted access to this view to ensure that only the administrator can execute this change. This allows for a discussion between the team implementing the solution and eMagiz before actions are taken. 63 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. 65 +== **Bug fixes ** == 66 66 67 -//__ Validatingexternalrecipientsinnotificationsettings__//68 - Beforepressingsave,we will nowvalidatewhatyou enteredinthe externalrecipientssettingtoensurethatwhatisenteredthererevalidvalues.67 +//__Improved deletion behavior for enumerations__// 68 +To prevent that eMagiz will incorrectly delete enumeration lists when you press a "Cancel" button, we have improved the deletion behavior when viewing enumerations in the Create phase of eMagiz. 69 69 70 -//__ Automaticallylinkenumerationlist to attribute__//71 -Wh enyoucreate anenumerationlistrelevant to a particular attribute,eMagiz willnowautomatically linkthe two togetherwithoutyou havingtodothismanually.70 +//__Prevent "async" api operations__// 71 +With this release, we have removed the ability to select the "async" option when the default message format is API Management. 72 72 73 -//__ Approveandgo toenvironment__//74 - Withthisrelease,wewillprovideyou withtheoption toapproveareleasetoa specificenvironment andleteMagiz directlytakeyoutothat environment.73 +//__Importing a response definition broke the request definition__// 74 +Currently, importing a response definition breaks the request definition. With this release, we have changed this behavior, ensuring that only the response definition is changed when importing and not the request definition. 75 75 76 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--approve-and-go-to-environment.png]] 76 +//__Removing a flow does not update the API "all-entry" anymore__// 77 +When you removed a flow from Create, the API Gateway all-entry received a new version of the flow. With this release, we have changed this behavior so that this only happens when the flow you remove is an API-related flow and not when it is a messaging or event streaming flow. 77 77 78 -//__ Removeirrelevantinformationon a runtime inDesignArchitecture__//79 - We have removedallirrelevant information for a userwhenyou enterthedetailsviewofaruntimein DesignArchitecture.The information thatis stillshown isvisualizedbelow.79 +//__Stop deployment plan when a property is missing__// 80 +Currently, the execution of your deployment plan continues when eMagiz notices a missing property. As this is confusing for a user and not desirable, we have updated the logic to ensure that when this happens, the execution stops. This allows you to fill in the properties, and once filled in, you can continue with the remainder of the deployment plan. 80 80 81 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--container-view.png]] 82 +//__Cap stack trace of error messages and log entries__// 83 +To prevent that enormous stack traces of error messages and log entries need to be processed by various systems, we have now limited what is kept so only the relevant information is shown to the user. 82 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 -== **Bug Fixes** == 96 - 97 -//__Various updates when importing store items in Design including a transformation__// 98 -With this release, we have made several improvements for importing store items in Design, including a transformation. This will further bolster our offering on this. 99 - 100 -//__Opening flow testing widget in specific circumstances was not working__// 101 -With this release, we fixed an issue where you could not open the flow testing functionality in the Create phase when your flow contained a particular construction combined with the “nullChannel.” 102 - 103 -//__Improved styling when adding a large message to a flow test__// 104 -With this release, the styling of the pop-up will not change when you define a large message as input (or expected output) of your flow test. This will ensure that you can still easily specify the flow test message’s name and description after entering the large message. 105 - 106 -//__Errors on the UI do not keep following me__// 107 -Before, we had some issues: when you navigated away from the API Gateway statistics page, an error pop-up would keep following you throughout the platform. To resolve this issue, you needed to refresh the browser. We have fixed this issue permanently with this release, making the refresh obsolete. 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:87 +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' withvalue'0' willnot beset sinceit isnotaString and noConverteris>>https://my.emagiz.com/p/question/172825635700363586||target="blank"]]126 -* [[ Kafka Consumer Mendix String Deserializeris notworking>>https://my.emagiz.com/p/question/172825635700363585||target="blank"]]127 -* [[ Namespace prefix'xs'hasnot beendeclared>>https://my.emagiz.com/p/question/172825635700363685||target="blank"]]89 +* [[Entry stops polling occasionally since generation 3>>https://my.emagiz.com/p/question/172825635703376768||target="blank"]] 90 +* [[Invalid datetime>>https://my.emagiz.com/p/question/172825635703389326||target="blank"]] 91 +* [[Paging with a queue -16>>https://my.emagiz.com/p/question/172825635703389781||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:95 +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 97 +* 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]] 110 +~* 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}}