Changes for page 203 - Fast Paced
Last modified by Carlijn Kokkeler on 2024/04/18 13:12
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 30.1
edited by Erik Bakker
on 2022/10/24 11:04
on 2022/10/24 11:04
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -2,11 +2,11 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** We have hit the ground running inthis quarter bynot onlyfocusing onlarger featuresbutalsospend a substantial chunk of timeonfocusing with us all on a lot of smaller feedback items and bugs. All these items will be provided to you with this release. Among these are flow designer improvements, navigation improvements, and consistency improvements. On top of that, we have made our new monitoring stack available toafirst set of models. So let us dive into all we have to offer this time!5 +**Hi there, eMagiz developers!** We have hit the ground running this quarter by focusing on more prominent features and spending a substantial chunk of time focusing with us all on a lot of smaller feedback items and bugs. All these items will be provided to you with this release. Among these are flow designer improvements, navigation improvements, and consistency improvements. On top of that, we have made our new monitoring stack available to the first set of models. So let us dive into all we have to offer this time! 6 6 7 7 == **New monitoring stack** == 8 8 9 -This release will introduce a new monitoring stack that is available for models that run in the new runtime architecture of eMagiz. With the help of this monitoring stack we have redesigned various screens in Manage and restructured our alerting approach. For a sneak preview ofwhatthese changesentailplease check out the following microlearnings.9 +This release will introduce a new monitoring stack available for models that run in the new runtime architecture of eMagiz. With the help of this monitoring stack, we have redesigned various screens in Manage and restructured our alerting approach. For a sneak preview of these changes, please check out the following microlearnings. 10 10 11 11 * [[Runtime Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-interpreting-runtime-statistics-gen3.WebHome||target="blank"]] 12 12 * [[Alerting in eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3.WebHome||target="blank"]] ... ... @@ -13,124 +13,140 @@ 13 13 * [[Queue Statistics>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-interpreting-queue-statistics-gen3.WebHome||target="blank"]] 14 14 * [[HTTP Statistics>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Advanced monitoring.HTTP Statistics.WebHome||target="blank"]] 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 pleasecontact us at productmanagement@emagiz.com to discuss the possibilities{{/info}}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, don't hesitate to get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] to discuss the possibilities{{/info}} 17 17 18 -== ** TransformationImprovements** ==18 +== **Academy improvements** == 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. 20 +On top of that, we have added various microlearnings to our academy offering available on docs.emagiz.com related to the new runtime architecture. You can identify these microlearnings by looking at the following icon in front of a microlearning. 22 22 23 -//__Improved Transformation options for booleans__// 24 -On top of that, we will introduce additional functionality to transform "Boolean to enumeration," "enumeration to Boolean," and" Boolean to Boolean." Just as you are used to for the "enumeration to enumeration" transformation, you can now define a value mapping for each combination mentioned above. See below for an example of how this looks. 22 +[[image:Main.Images.Release Blog.WebHome@186-release-blog--gen3-microlearnings-icon.png]] 25 25 26 - [[image:Main.Images.ReleaseBlog.WebHome@179-release-blog--transformation-options-boolean.png]]24 +== **Flow Designer Improvements** == 27 27 28 -== **Feedback items ** == 26 +//__See last changed date and changed by on resource level__// 27 +This release will reinstate the ability to see who changed a resource last and when it was changed for the last time. You can find this information by double-clicking on a resource or viewing its details via the view button. 29 29 30 - Apart fromthe key updatesaround functionality, wehavealsosolvedotherfeedback items.29 +[[image:Main.Images.Release Blog.WebHome@186-release-blog--change-info.png]] 31 31 32 -//__ Correctly definethe sizeofa cloudslotwhencreating it forthefirsttime__//33 - Currently,eMagizwilllook to Designwhen creatingthecloud slotforthefirst time.Thisisto avoidyou havingto“create” yoursolution twice, as therewereinstanceswhere eMagizwould alwayscreate thecloudslotwiththesmallestsizeavailablefirst,evenifthiswere not what you wanted.31 +//__See on which other flows a resource is used__// 32 +This release will reinstate the ability to see whether a resource is used in other flows within your model or not. This will help to determine the impact of a specific change. 34 34 35 -//__Updated infographic Capture__// 36 -As of now, we have updated the infographic on the Capture phase to incorporate the new look and feel and explain the updated functionality in Capture. 34 +[[image:Main.Images.Release Blog.WebHome@186-release-blog--resource-used-in-other-configs.png]] 37 37 38 -//__ Updatederrorfeedbackin Design__//39 - Before,youcouldseeatransformationerror inDesign evenhoughthetransformationwasnotusedinyoursolution(i.e.,“datapipeline”functionality).However,when younowdefineaspecificintegrationasa datapipelinesolution,theerrorwill notbeshown.36 +//__Toggle option to see the generated resource by default__// 37 +Upon request, we have made the toggle for the generated resources in the new flow designer user-dependent. This means that you, as a user, can determine that the toggle should also be on. This means that the generated resources will be shown to you when opening any flow in eMagiz. When you switch the toggle off, this will mean that you will **not** see the generated resources by default. 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. 39 +== **Feedback items ** == 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. 41 +We have also solved other feedback items besides the flow designer's critical updates. 46 46 47 -//__ Showonlythetenlatestflowversionswhen selectinga flow versioninaRelease__//48 - Toimprovehe quality andspeedofdefining arelease,we will showonlythelatest tenersions of a flow inhereleasewidget,asthese ten are mostlikelyto beselectedbyauser.If youneedan olderversion,you canadditviathe“Details”optionontherelease.43 +//__Redirect to the Manage Dashboard from your model home page__// 44 +Directly navigating to the Manage phase (of any environment) will automatically redirect you to the error message Dashboard, as that is the landing page of the Manage phase. 49 49 50 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--ten-latest-flow-versions-release.png]] 46 +//__Readable entry of a SpEL expression in a flow component__// 47 +As of now, the input field for your SpEL expression in certain flow components will dynamically expand when you enter a large SpEL expression. This will improve the readability of your solution and will make it easier to enter and validate your SpEL expressions. 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. 49 +[[image:Main.Images.Release Blog.WebHome@186-release-blog--spel-expression-readible.png]] 54 54 55 -//__C learAPI GatewaySystemmessage__//56 - Withthisrelease,wehave addedtheClearbuttonthatyou alreadyknowfromthemessagingpatternto theAPI Gatewaysystemmessage.Thisunifies theoptionsbetweenthetwo patterns in Design on thesystemmessagelevel.51 +//__Keep Create and the Create Phase release in sync__// 52 +Previously the Create and the Create Phase release might have become out of sync. As a result, comparing a release to the Create Phase release could yield confusing results. With this release, we have made several improvements to prevent this from happening. 57 57 58 -//__ AdditionalinformationinProperty History__//59 - Toimproveheusabilityof thepropertyhistorypage inDeploy, wenowalsoshow the runtimeonwhichaparticularpropertyischanged.Thisisparticularly usefulwhenchangingthesamepropertyusedondifferent runtimes.54 +//__Mask password values in the unused properties overview__// 55 +All property values of the type password can be masked in the properties overview screen. However, this behavior was different when pressing the unused properties overview. With this release, we have corrected this behavior to ensure that passwords are also masked in this overview. 60 60 61 -//__ SaveTagwhenready__//62 -With this release, we have madeitexplicitthat whenyouwantto changethenameof atag,you first needto press the“Save” buttonbefore thechangeisactualizedwithinyourmodel.57 +//__Press Enter to Search for properties__// 58 +With this release, we have added functionality that makes it possible to press **Enter** when searching for properties in the property overview. 63 63 64 -//__ Viewdeployment stepinformationwhen having view rights__//65 -With this release, we have m adeitpossibletoviewnotlythedeploymentstepsbutlsothedetailedinformation ofeachdeployment stepwhenyouonlyhaveviewrightsonaspecificenvironment.60 +//__Styling update on tag selection on integration level__// 61 +With this release, we have improved the styling of tags displayed on the integration and system level. This way, the tag is better readable, and the icon to remove a selected tag is completely shown to the user instead of partly. 66 66 67 -//__ Validating externalrecipientsin notificationsettings__//68 - Beforepressingsave,wewillnowvalidatewhatyouenteredinthe external recipientsetting toensurethatwhatis enteredtherearevalidvalues.63 +//__Enter to close automated flow testing pop-up__// 64 +Upon your requests, we have made the pop-up detailing your automated flow test results to be closable by pressing the Enter key on your keyboard. This saves you the hassle of grabbing your mouse and clicking the button. 69 69 70 -//__ Automaticallylinkenumerationlisttoattribute__//71 -When youcreatean enumeration listrelevantto aparticularattribute,eMagizwill nowautomaticallylinkthe twotogether withoutyou having todothis manually.66 +//__Improved naming of downloaded Event Streaming keystore__// 67 +When downloading a Keystore that an Event Streaming client needs to access a topic, the name now includes the client name **and** the environment so you can easily discern the difference between the keystores when distributing them to your client. 72 72 73 -//__ Approve andgoto environment__//74 - With thisrelease,wewill provideyouwith the option to approvearelease toa specificenvironment andlet eMagiz directly takeyoutothat environment.69 +//__Pop out on the Traces tab within Flow Testing__// 70 +In line with the improvements we made before within the Flow Testing functionality, we have now added the pop-out functionality to all results shown in the traces tab. This will make it easier to analyze what happens between the start and the end of your flow. 75 75 76 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--approve-and-go-to-environment.png]] 72 +//__Sorting User Management__// 73 +As of this release, the user management overview in Deploy for users and roles will be sorted alphabetically to make it easier to find a specific user or role within this overview. 77 77 78 -//__ Removeirrelevantinformationon antime in DesignArchitecture__//79 - Wehave removedallirrelevant informationfor a userwhenyouenterthe detailsview ofaruntimein DesignArchitecture.Theinformationthatisstillshown isvisualizedbelow.75 +//__Improved warning on passthrough API operation__// 76 +Most users forget to configure a backend API operation or switch to the transformation option when configuring an API operation in Capture and Design before moving to Create. This is then blocked, leaving users confused about what to do next. Therefore we introduce an additional warning in the Design phase that lets you know that your configuration of an API operation is not yet finished. This way, you can correct it **before** trying to move it to Create. 80 80 81 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--container-view.png]] 78 +//__Improved update functionality of Swagger file when changing data model__// 79 +Before, there were specific scenarios in which the Swagger file was not updated according to changes made to your API data model. With this release, we have made a first step in improving this behavior. Then, when you change the order of attributes in your data model, the Swagger file will be updated accordingly. 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. 81 +{{info}}Note that just as with any resource that is changed from the Design phase, a version bump of your flow in Create is still necessary to deploy the changes to your environment(s){{/info}} 85 85 86 -//__ Preventpressing“Applyto environment” multiple times leading to conflicts__//87 - Withthis release,we have improvedthis functionalitytoverify whetheranupdateis currentlybeing executed. If thisistrue,all othertimes, you pushthebutton; youwillbeotified thattheprocessis still running.Thisisdonetoavoidpotentialconflicts if a user presses the "Apply to environment"buttonmorethanonce inashort period.83 +//__"Disapprove and go to environment"__// 84 +Following the "Approve and go to environment" functionality, we have now expanded that by adding the "Disapprove and go to environment" functionality. 88 88 89 -//__ Add“State”to thetopic details in DeployArchitecture__//90 - Based on yourfeedback,weveimprovedthetopic detailsoverviewto include the“State”ofatopic. Eachtopiccanbe“Unchanged,” “Changed,”“Deleted,”or“New.”Basedonthisstate,youcan determinewhich topicswillbeadded,changed,deleted,orremainuntouched.86 +//__Improve readability of API Gateway operations in Create and Deploy__// 87 +When you have a lengthy name for your API Gateway operation, it becomes tough to discern the various API Gateway operations in your landscape. To alleviate this problem, we have added a tooltip functionality that will show the full display name when hovering over the API Gateway operation. 91 91 92 -//__ Improvedstabilityof loggingon theGen3Architecture__//93 - With this release, we haveimproved thestabilityof thelogging andmade sure that theloggingis correctlycompactedinternally.89 +//__Add Topic Storage information to License Tracker__// 90 +On top of the information already shown in the License Tracker, we have added Storage information for the Event Streaming pattern. This way, you can easily see the amount of GB you have assigned and the amount of GB that was contractually agreed upon between you and eMagiz. 94 94 92 +//__Add Compatibility check when importing store items__// 93 +We have added a compatibility check to the platform to prevent you from importing store items that do not work on a specific runtime architecture to prevent this from happening. 94 + 95 +//__Show dependencies between support objects__// 96 +As of now, when you click on a support object, all related support objects will also be highlighted in the same overview. This makes it easier to see the relationship between support objects and components and among support objects. 97 + 98 +//__Improve rendering of validation definition when using multiple namespaces__// 99 +With this release, we have improved how we render the validation definition (XSD) when using multiple namespaces. This will prevent you from running into validation errors while everything seems configured correctly on your end. 100 + 95 95 == **Bug Fixes** == 96 96 97 -//__ VariousupdateswhenimportingstoreitemsinDesign includingatransformation__//98 -With this release, we have made several improvements for importingstoreitemsinDesign,includingatransformation. This willfurtherbolster our offeringon this.103 +//__Provide correct feedback when a flow is transferred to Deploy for the first time__// 104 +With this release, we have made several improvements to what feedback is given to the user when moving a flow from Create to Deploy for the first (upon creating your first definitive version). This will ensure that no confusing pop-ups will be shown that are incorrect and only confuse the user further. 99 99 100 -//__ Openingflowtestingwidget inspecificcircumstanceswas not working__//101 -With this release, we fixedan issuewhereyou couldnotopen theflow testingfunctionalityintheCreatephasewhenyourflowcontaineda particular constructioncombinedwith the“nullChannel.”106 +//__Show information in the Exception of error messages overview__// 107 +With this release, we have resolved the bug plaguing this page. As a result, you will again see information on this page when there is information to show. 102 102 103 -//__Improve dstylingwhenaddinga large messagetoaflowtest__//104 - Withthis release,thestyling of thepop-upwill not change when youdefinea large message asinput(orexpectedoutput)ofyourflow test. This will ensurethatyoucanstilleasilyspecifytheflow test message’snameanddescriptionafterenteringthelargemessage.109 +//__Improve styling of cron trigger configuration pop-up__// 110 +The styling of this pop-up made it very hard to configure a cron trigger. We have redesigned the styling to make the pop-up readable again. 105 105 106 -//__ Errors on theUI donotkeepfollowingme__//107 - Before,wehadsomesues:whenyounavigatedaway from theAPI Gatewaystatisticspage,anerrorpop-upwould keepfollowingyouthroughoutthe platform. To resolve thisissue,youneededto refreshthebrowser. We havefixed thisissuepermanentlywiththis release, making the refresh obsolete.112 +//__Prevent flow editing locks in specific situations__// 113 +There were specific situations when switching between Design and Create that could lead to unexpected behavior in the Create phase. This led to a flow editing lock warning to the user. We have solved this problem in this release. 108 108 109 -//__ Navigatingbacktothetransformation in Createworksagain__//110 -With this release, we have squashedabug thatannoyed users. Before, itcouldhappenthat whenyouavigated away fromthetransformation page in your flow inCreate and returned later, the transformationwasnotshown anymore.With this release, we have made sure that regardless of where youcomefrom,the transformation will be visible foryou to see.115 +//__Generate property value empties the runtime selection__// 116 +With this release, we have fixed the bug that emptied the runtime selection upon generating a property value (i.e., password). 111 111 112 -//__ Remove the qualifiednamewheneditinganon-legacyMendix entryineMagiz__//113 - With thisrelease,wehave removedthepossibilityofchangingthe obsoletequalifiednamewhen editinga non-legacyMendix entryin eMagiz.118 +//__Make sure nothing of a system message is editable from your exit__// 119 +Before, you could change part of your system message from your exit (but not everything). This led to confusion. As a result, we have now made sure you cannot edit anything on the system message level from your exit to keep it consistent with our design choices. 114 114 115 -//__ Selectingtags whendrawing aline inCapture__//116 -We have no w madethispossible(again). This way,youcandirectlyselectthetag(s)you wantinstead of openingthedetailedinformation onheline after it is alreadyadded to Capture.121 +//__Prevent users without view rights from seeing a weird screen in those phases__// 122 +With this release, we have introduced a consistent approach towards what we show a user that has no view rights on a complete phase. This means that you will always see the same information consistently. 117 117 118 -//__ Removeinvalidselectionwhen configuringa crontriggerviatheooling__//119 -With this release, we have removed invalidselection options presented toyou whenyouusedtheconfigurationoption ona propertyof typecronto leteMagizdefinethecron trigger value. Thisistoavoidunwanted surpriseswhen deploying yoursolution.124 +//__name of starting point of the flow test is incorrect__// 125 +With this release, we have ensured that the name of the starting point of your flow test you see in the "Results" tab is correct. 120 120 127 +//__Audit Trail on User Management could break__// 128 +When performing many changes to user management in Deploy at once, there was a chance the audit trail functionality would give an error blocking you from continuing your update. With this release, we have solved that issue. 129 + 130 +//__Progress bar in the license tracker is shown twice__// 131 +With this release, we have fixed a bug that showed the progress bar twice in the license tracker. 132 + 133 +//__Compare flows with support objects in the new flow designer__// 134 +We have fixed a bug related to support objects that prevented you from comparing two flows when one was built in the latest, and the difference was constructed in the old flow designer. 135 + 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:138 +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 125 * [[Header 'X' with value '0' will not be set since it is not a String and no Converter is>>https://my.emagiz.com/p/question/172825635700363586||target="blank"]] 126 126 * [[Kafka Consumer Mendix String Deserializer is not working>>https://my.emagiz.com/p/question/172825635700363585||target="blank"]] 127 127 * [[Namespace prefix 'xs' has not been declared>>https://my.emagiz.com/p/question/172825635700363685||target="blank"]] 128 128 144 + 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:147 +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 149 +* 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]] 162 +~* 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}}