Changes for page 212 - Failover Fiesta
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 28.1
edited by Erik Bakker
on 2022/10/24 09:02
on 2022/10/24 09:02
Change comment:
There is no comment for this version
To version 208.1
edited by Carlijn Kokkeler
on 2023/10/24 11:24
on 2023/10/24 11:24
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 +207 - Aligned State - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -2,137 +2,117 @@ 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 groundrunning in thisquarterby not onlyfocusing on largerfeaturesbut also spendasubstantial chunkof time onfocusingwithusall on a lot ofsmallerfeedbackitemsand bugs. Alltheseitemswill be providedtoyouwith this release.Among theseareflow designerprovements,navigationimprovements, andconsistencyimprovements.On top of that, we have madeour new monitoring stackavailableto a first setof models. So letus diveinto all we have to offer this time!5 +**Hi there, eMagiz developers!** We have done much work for state generation, so that you can derive more information from your data! Examples are enrichment, aggregation, change detection and duplicate detection. 6 6 7 - ==**Newmonitoringstack**==7 +{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}} 8 8 9 - Thisreleasewillintroducea newmonitoringstack thatisavailableformodelsthat run in thenew runtimearchitectureofeMagiz. With thehelpfthismonitoring stackwehaveredesignedvariousscreensin Manageandrestructuredour alerting approach.Forsneakpreviewofwhat thesechangesentailplease check out thefollowing microlearnings.9 +Next to state generation, several improvements regarding the alignment of components have been made. Moreover, performance improvements and bug fixes have been implemented. Lastly, a change in the metrics storage duration has been performed. 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-interpreting-runtime-statistics-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 +== **State Generation~*~*** == 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 +//__New components__// 14 +The following components have been added: 15 +* Aggregator: reverse of the splitter, used to combine multiple messages into a single one. 16 +* Infinispan metadata outbound channel adapter: used to (temporarily) store metadata, which can be used to enrich messages, or make decisions in filters or scripts. 17 +* Content enricher: used to add properties to the payload of messages, similar to what the header enricher can do for headers. 18 +* Duplicate detector: support object used to detect duplicate messages for a certain key on an inbound channel of a flow component. Duplicates can be marked or discarded. 19 +* Infinispan support objects, supporting the aggregator, metadata outbound channel adapter and content enricher. 17 17 18 -== **Transformation Improvements** == 21 +//__SpEL functions & JSON__// 22 +Added SpEL functions for: 23 +* Encoding & decoding Base64, Hex and hmac. 24 +* Date retrieval (currentDateTime, currentEpochMilli, currentEpochSecond). 25 +* Date conversion (DateTime to Epoch, Epoch to DateTime, DateTime formatter and DateTime parser). 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. 27 +Added support for SpEL property accessors for XML and JSON, meaning that you can read message payloads in SpEL expressions easily. For example, to retrieve the value for 'id' in the following JSON String: `{"id":"123"}`, this SpEL expression suffices: `payload.id`. 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. 29 +Added support for `#JsonPath` usage in SpEL expressions. 25 25 26 - [[image:Main.Images.ReleaseBlog.WebHome@179-release-blog--transformation-options-boolean.png]]31 +{{info}}The components are all configurable from the Flow Designer in Create and are accompanied by help text explaining the use cases and the various technical configurations. Note that to make the components work in your model, a new release containing the latest image (2.0.0) needs to be deployed.{{/info}} 27 27 28 -== **Feedback items ** == 33 +== **Metrics Storage Duration** == 34 +We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 7, 14 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively. 29 29 30 - Apart fromthe key updatesaround functionality, wehavealsosolvedotherfeedbackitems.36 +[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]] 31 31 32 -//__Correctly define the size of a cloud slot when creating it for the first time__// 33 -Currently, eMagiz will look to Design when creating the cloud slot for the first time. This is to avoid you having to “create” your solution twice, as there were instances where eMagiz would always create the cloud slot with the smallest size available first, even if this were not what you wanted. 38 +== **Feedback Items** == 34 34 35 -//__ UpdatedinfographicCapture__//36 - As of now, wehave updatedthe infographiconthe Capturephasetoincorporate thenewlook and feelandexplain theupdatedfunctionalityinCapture.40 +//__Import from store__// 41 +The button 'Import from Store' in Design will directly open the store instead of showing a pop asking whether the store should be opened. 37 37 38 -//__ Updatederror feedbackinDesign__//39 - Before,you couldseeatransformationerrorin Design even thoughthetransformationwasnotusedin yoursolution (i.e., “data pipeline”functionality). However,whenyounow defineaspecificintegrationas adatapipelinesolution, the error willnot be shown.43 +//__Save and cancel buttons placement__// 44 +The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking. 40 40 41 -//__ Improvedstyling of Topic Storagein DesignArchitecture__//42 - Whenhaving a large number oftopicsin your environment, thetopicstorageoverview inDesignArchitecturewillnowbeimprovedas the horizontalscrollbaris gone.46 +//__User session times__// 47 +The user session times for 3rd generation runtime dashboards have been extended, so that the user is not thrown out of the model when using the Manage phase for longer than an hour. 43 43 44 -//__ Improved stylingof error feedback onUser ManagementinDeploy__//45 - With thisreleasewe haveimprovedthe stylingofthefeedbackpop-up youget inUsermanagement afterpressing“Applytoenvironment”andseveral updatescouldnotbe executed.49 +//__Cancel and next buttons order__// 50 +The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button. 46 46 47 -//__ Show only the ten latest flow versions when selectingaflow versioninaRelease__//48 -T o improve thequality andspeed of definingarelease, we will show onlythe latestten versionsofaflow in the release widget,as these tenare mostlikely tobeselected by a user. If youneedanolderversion, you can additviathe “Details”option on therelease.52 +//__Data sink page__// 53 +The data sink page has been moved to the “Explore” tab. 49 49 50 -[[image:Main.Images.Release Blog.WebHome@179-release-blog--ten-latest-flow-versions-release.png]] 55 +//__Unused images removal__// 56 +When a release is removed, the related unused images in the on-premises machines will be removed as well. 51 51 52 -//__ OptionalClient Secretwhenusingthegrant_typePassword when calling an OAuth2.0 IDP__//53 - Before, youneededtodefinethe ClientSecret evenfor thegrant_type Password,whereit isot always required.Wehavecorrected thisbehavior toensurethat this is inlinewith theOAuth 2.0 specification.58 +//__Flow Designer performance__// 59 +Performance improvements for the Flow Designer have been implemented. 54 54 55 -//__ ClearAPI GatewaySystemmessage__//56 -W iththis release,wehave addedtheClearbuttonhatyoualreadyknowfromthemessagingpatternto theAPI Gatewaysystemmessage.Thisunifiesthe optionsbetweenthetwopatternsinDesignonthesystemmessagelevel.61 +//__Properties with special characters__// 62 +When a user would migrate to gen3 and deploy their release containing properties with special characters, certain flows could not find the correct values to properties anymore or could not find the properties altogether. With this release, special characters such as a backslash do not break properties after deployment. 57 57 58 -//__ Additionalinformationin Property History__//59 - Toimprovetheusabilityof theproperty history pagein Deploy,we now alsoshowtheruntimeonwhichaparticular propertyis changed.Thisisparticularlyusefulwhenchangingthesameproperty usedondifferentruntimes.64 +//__Hidden flow fragements__// 65 +When importing items from the store, flow fragments that are hidden in design will be listed under the versions in create. 60 60 61 -//__ SaveTag whenready__//62 - With thislease,wehavemadeitexplicitthatwhenyouwantto changethename ofatag,you firstneedtopressthe“Save”buttonbeforethechangeisactualizedwithinyour model.67 +//__Resources disappearances__// 68 +Resources would disappear in the flow designer when pressing Cancel on selecting a new resource. With this release, resources without a name will not trigger error messages when users select components. 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. 70 +//__Error channel for all inbounds__// 71 +If there is no custom error handling, Gen3 migration would set the error channel to “errorChannel” only for the first inbound in an entry flow. 72 +We added a migration step, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. 66 66 67 -//__ Validatingexternal recipientsin notification settings__//68 - Beforepressing save,wewill now validate whatyouenteredinthexternalrecipients settingto ensurethat whatisenteredtherearevalidvalues.74 +//__Highlighting resources__// 75 +The performance of highlighting resources of selected components is improved in Read only mode. 69 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 updateswhenimporting storeitemsin Designincludingatransformation__//98 - With thisrelease,wehavemadeseveral improvementsforimporting storeitemsin Design,includingatransformation. Thiswillfurtherbolsterourofferingonthis.79 +//__Topic and event-processor names__// 80 +The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable. 99 99 100 -//__ Opening flow testing widgetinspecific circumstances wasnotworking__//101 - With thisrelease,wefixedanissuewhereyoucouldnotpentheflow testingfunctionality in the Create phasewhenyourflow containeda particularconstruction combinedwith the “nullChannel.”82 +//__System alignment__// 83 +The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. So, systems are aligned regarding positioning across all phases. 102 102 103 -//__ Improvedstyling when addinga large message to a flow test__//104 - With this release,thestylingof thepop-upwill not changewhenyoudefine a large messageasinput (orexpectedoutput) ofyour flow test. This will ensure that youcan stilleasily specifytheflowtestmessage’sname and description afterentering the largemessage.85 +//__Error checking__// 86 +Besides checking error header, the error trigger is now configured to check if an error message contains a term. 105 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. 88 +//__Alerting__// 89 +For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%. 90 +For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of configured size used to 110%. 91 +The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match. 108 108 109 -//__ Navigatingback tothe transformationin Create worksagain__//110 - With this release,we have squashed a bugthatannoyed users. Before,it could happenthat whenyou navigated awayfrom the transformation pagein your flow inCreateand returned later, the transformation was not shown anymore. With this release, we havemadesure that regardless of where you come from, the transformationwill bevisible for you to see.93 +//__Unused containers__// 94 +Containers are set inactive when they are unused and removed in Design. 111 111 112 -//__ Removethe qualifiednamewhenediting anon-legacy MendixentryineMagiz__//113 -W iththis release,wehaveremovedthe possibilityofchangingthe obsoletequalified namewheneditinga non-legacy Mendix entryinMagiz.96 +//__Error popups when promoting a release version__// 97 +We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment. 114 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:101 +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"]] 103 +* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]] 104 +* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]] 105 +* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]] 106 +* [[3rd generation runtime with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]] 128 128 108 + 129 129 == **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:111 +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 113 +* 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. 115 +* 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 137 * Check out the release notes [here] 138 138 * Start thinking about how the license tracker can aid your development ... ... @@ -143,8 +143,8 @@ 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]] 126 +~* 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.128 +~*~* Indicates a next-generation-architecture only feature. 149 149 {{/info}})))((({{toc/}}))){{/container}} 150 150 {{/container}}