Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
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 508.1
edited by CarlijnKokkeler
on 2024/05/06 13:44
on 2024/05/06 13:44
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 186-Daemon Switch1 +220 - Patch Parade - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,150 +1,105 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}}((( 2 +{{container layoutStyle="columns"}} 3 +((( 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 in this quarter by not only focusing on larger features but also spend a substantial chunk of time on 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 a first set of models. So let us dive into all we have to offer this time!6 +**Hi there, eMagiz developers!** 6 6 7 -== ** New monitoring stack** ==8 +== **Feedback Items** == 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 of what these changes entail please check out the following microlearnings. 10 +//__Integration pattern information__// 11 +Integration pattern information of the selected message type has been added to the pop-up that is shown in Capture when creating a new integration. 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"]] 13 +[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]] 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}} 15 +//__Message queue history__// 16 +All events that relate to message queues (delete message, delete all messages or delete queue) are logged in the Manage phase instead of the Deploy phase. 17 17 18 - == **TransformationImprovements** ==18 +[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]] 19 19 20 -//__ Toggle between Design and Create__//21 - This release will introduce a toggle thatallowsyou to quicklynavigatebetween theCreate Transformation and the Design Message Mapping. In both Create as Design, a new button isaddedon thetransformation level that allowsyou to open the transformation in Design(or Create) dependingonwhereyou are currently. Thisshould make navigating easierwhen youmakeamistake or forget something in Design.20 +//__Search boxes__// 21 +Search boxes in the properties overview are now shown by default. 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. 23 +[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]] 25 25 26 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--transformation-options-boolean.png]] 25 +//__Set as mapped__// 26 +It is now possible to choose whether to set/unset all attributes of an entity as mapped in design. 27 27 28 - == **Feedbackitems** ==28 +[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]] 29 29 30 -Apart from the key updates around functionality, we have also solved other feedback items. 30 +//__SSL settings__// 31 +Changes can now be deployed on SSL level without creating a new version of a flow in Create. 31 31 32 -//__ Correctly definethesize of a cloud slot when creating it for the first time__//33 - Currently, eMagizwill looktoDesign when creatingthe cloud slotfor the firsttime.Thisis toavoid you having to “create” yoursolution twice,astherewere instances whereeMagizwould alwayscreate thecloudslotwith thesmallest size available first,evenif this werenotwhat you wanted.33 +//__Machine deletion__// 34 +When trying to delete a machine that still has containers linked to it, the user will be presented with a pop-up explaining why the machine cannot be deleted. 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. 36 +[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]] 37 37 38 -//__ Updatederrorfeedback inDesign__//39 - Before,youcouldseeatransformationerror in Designeventhoughthe transformationwasnot usedin yoursolution(i.e., “data pipeline” functionality).However, whenyounow defineaspecificintegration as adata pipelinesolution,the errorwillnotbe shown.38 +//__JMS header handling__// 39 +Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. For this, a new runtime image(LINK) has been released. 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. 41 +== **Bug Fixes** == 42 +//__Annotation styling__// 43 +It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability. 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. 45 +[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]] 46 46 47 -//__ Show onlytheten latest flow versionswhen selectinga flowversionina Release__//48 - Toimprovethe quality and speedofdefining a release, we will show onlythelatest ten versionsof a flow intherelease widget, asthese tenare mostlikely to be selected by a user. If youneedanolderversion,you can add itviathe“Details”optiononthe release.47 +//__Filter rejection warnings__// 48 +A discard channel is required for filter components when “Throw exception on rejection” value is set to false. 49 49 50 -[[image:Main.Images.Release Blog.WebHome@ 179-release-blog--ten-latest-flow-versions-release.png]]50 +[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]] 51 51 52 -//__ Optional Client Secret when usingthegrant_type Password when calling an OAuth2.0 IDP__//53 - Before,youneededtodefinetheClient Secretevenforthegrant_type Password, whereit isnotalways required.We have corrected thisbehaviortoensurethat thisis in line withtheOAuth2.0 specification.52 +//__Manage Explore__// 53 +An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage. 54 54 55 -//__ Clear API GatewaySystem message__//56 - Withthisrelease,wehaveadded the Clearbuttonthatyou already knowfrom themessagingpattern to theAPI Gateway systemmessage.This unifiestheoptions betweenthe twopatternsin Designonthe system messagelevel.55 +//__Page refreshing__// 56 +Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment. 57 57 58 -//__ Additionalinformation in PropertyHistory__//59 - Toimprovethe usabilityofthepropertyhistorypagein Deploy,wenow also show theruntimeonwhichaparticular property is changed.Thisis particularlyusefulwhenchangingthe same propertyused on differentruntimes.58 +//__Message redelivery__// 59 +An issue has been fixed where large messages would be shown at the bottom of the page instead of the right side of the page. 60 60 61 -//__ SaveTag whenready__//62 -With th is release,we have madeit explicitthatwhenyou want to changethenameof a tag,you first need topressthe“Save” buttonbeforethechange is actualizedwithinyourmodel.61 +//__Deployment plan__// 62 +We have implemented changes that should prevent a discrepantion between the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) and the actual execution of relevant steps. 63 63 64 -//__ View deployment step information when having viewrights__//65 -W iththis release,we havemadeit possible toview notonlythedeploymentstepsbutalso thedetailedinformation ofeach deploymentstep when you only haveviewrightson aspecific environment.64 +//__Overview pages__// 65 +We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase. 66 66 67 -//__ Validatingexternalrecipients in notification settings__//68 - Beforepressingsave,wewill now validatewhat youentered in the externalrecipientssettingtoensurethatwhatisenteredtherearevalid values.67 +//__Memory check__// 68 +Machines deleted in Design are excluded from the memory health check in Deploy, so that no unnecessary memory changes have to be done to delete machines. 69 69 70 -//__ Automaticallylink enumeration list toattribute__//71 - Whenyoucreatean enumerationlistrelevanttoaparticularattribute,eMagiz will nowautomaticallylinkthetwo togetherwithoutyouhaving todothismanually.70 +//__Copy password__// 71 +The copy to clipboard button now copies the actual value of passwords instead of the masked value of them. 72 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 -== **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:75 +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' will not be set since it is not a String and no Converter is>>https://my.emagiz.com/p/question/172825635700363586||target="blank"]] 126 -* [[Kafka Consumer Mendix String Deserializer is not working>>https://my.emagiz.com/p/question/172825635700363585||target="blank"]] 127 -* [[Namespace prefix 'xs' has not been declared>>https://my.emagiz.com/p/question/172825635700363685||target="blank"]] 77 +* [[Swagger UI: 503 Service Unavailable>>https://my.emagiz.com/p/question/172825635703824607||target="blank"]] 78 +* [[PATCH call without REST template>>https://my.emagiz.com/p/question/172825635703824685||target="blank"]] 128 128 129 -== **Key takeaways** ==80 +== **Key Takeaways** == 130 130 131 -Thanks to all thathelp build,those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:82 +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: 132 132 133 -* If you have questions surrounding our Program Increment Planning, please get in touch with 84 +* 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 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 86 +* 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) 137 -* Check out the release notes [here] 88 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]] 138 138 * Start thinking about how the license tracker can aid your development 139 139 * Start thinking about major, minor, and patch 140 -* Upgrade to the latest build number 141 141 * Keep making great integrations 142 142 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]] 96 +~* 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 -~*~* Indicates a GEN3-only feature. 149 -{{/info}})))((({{toc/}}))){{/container}} 98 +{{/info}} 99 +))) 100 + 101 +((( 102 +{{toc/}} 103 +))) 150 150 {{/container}} 105 +{{/container}}