Changes for page 212 - Failover Fiesta
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 41.1
edited by Erik Bakker
on 2022/11/07 16:35
on 2022/11/07 16:35
Change comment:
There is no comment for this version
To version 200.1
edited by Carlijn Kokkeler
on 2023/10/24 09:06
on 2023/10/24 09:06
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 - 187 -IntegrationSponsor1 +207 - Aligned State - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -2,150 +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!** W iththis releasewe willrelease severalimpactfulfeaturesandenablersto our community.Amongothersthe nextphase ofthe eMagizStorewillbecome publicly available.Thismeans thatyou cannowimportdata modelsand transformationon topofsystemmessages inDesignand acceleratorsin Create.Furthermore, we will launch aw Betafunctionalitythroughsome ofour clientsthatwillenableyoutorestoreyourflowto apreviousversion.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. State generation functionality is only accessible for models with an add-on state generation license. 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. 6 6 7 -== **St ore- Next phase** ==7 +== **State Generation** == 8 8 9 -This release will introduce the next phase of the Store to our whole community. With this new functionality you can now import data model messages (i.e. CDM, API Gateway Data model or Event Streaming data model) and transformations. This way connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce and others will become even easier. 9 +//__New components__// 10 +The following components have been added: 11 +* Aggregator: reverse of the splitter, used to combine multiple messages into a single one. 12 +* Infinispan metadata outbound channel adapter: used to (temporarily) store metadata, which can be used to enrich messages, or make decisions in filters or scripts. 13 +* Content enricher: used to add properties to the payload of messages, similar to what the header enricher can do for headers. 14 +* 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. 15 +* Infinispan support objects, supporting the aggregator, metadata outbound channel adapter and content enricher. 10 10 11 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]] 17 +//__SpEL functions & JSON__// 18 +Added SpEL functions for: 19 +* Encoding & decoding Base64, Hex and hmac. 20 +* Date retrieval (currentDateTime, currentEpochMilli, currentEpochSecond). 21 +* Date conversion (DateTime to Epoch, Epoch to DateTime, DateTime formatter and DateTime parser). 12 12 13 - {{info}}Formoreinformationon theStorepleasecheck out this[[course>>doc:Main.eMagizAcademy.Microlearnings.Novice.eMagizStore.WebHome||target="blank"]].Asa reminderyou canfindalldocumentationonallavailableStorecontentpublishedbyeMagiz[[here>>doc:Main.eMagizStore.WebHome||target="blank"]].{{/info}}23 +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`. 14 14 15 - == **NeweMagizMendixConnector** ==25 +Added support for `#JsonPath` usage in SpEL expressions. 16 16 17 -With this release we introduce a new version of the eMagiz Mendix Connector. This version (6.0.0) will work both with the current runtime architecture and the new runtime architecture making the migration from the current runtime architecture to the new runtime architecture easier. The new version of the eMagiz Mendix Connector can be found in the Mendix Marketplace and in the eMagiz portal. 27 +//__New image version 2.0.0__// 28 +The above functionalities are features of the new image version 2.0.0. Important to note is that the library used for Code Mappings has been changed. Changed the library used for Code Mappings. Any customer with Gen3 runtimes and code mappings is required to reset their infra flows prior to deploying on image 2.0.0. 18 18 19 -{{info}}Migrating the runtime from the eMagiz portal works the same as for any other runtime. The migration path to migrate can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}} 30 +//__Component pages__// 31 +Pages to add the new components have been created. Forms have been created nicely with proper help texts. The EHCache cache manager has been removed. 20 20 21 -== **Flow version restore** ~* == 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 5, 7 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. 22 22 23 - On top of that wewillalso launchanew Beta featuretothecommunity that allows you to restoreyour flow to a previousversion. This way you can quickly undochanges madethatwerencorrect.36 +[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]] 24 24 25 - [[image:Main.Images.ReleaseBlog.WebHome@187-release-blog--flow-version-restore.png]]38 +== **Feedback Items** == 26 26 27 -{{warning}}Note, that the following restrictions apply when restoring to a previous version: 28 - * Changes made on definition and transformation level are **not** restored 29 - * You will **not** be able to restore to any flow version that was created before October 17th, 2022 30 - * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back 31 - * Your restored flow version will **not** be automatically committed to Deploy{{/warning}} 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. 32 32 33 -== **Feedback items ** == 43 +//__Save and cancel buttons placement__// 44 +The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking. 34 34 35 -We have also solved other feedback items besides the flow designer's critical updates. 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. 36 36 37 -//__ Redirect to theManageDashboardfrom yourmodel home page__//38 - Directlynavigating to theManagephase(of anyenvironment) willautomaticallyredirectyou to theerrormessageDashboard, asthatisthe landingpageoftheManagephase.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. 39 39 40 -//__ Readable entry ofaSpEL expressionin a flow component__//41 - As of now, theinput fieldfor your SpEL expression in certainflow componentswill dynamicallyexpand whenyou enteralargeSpELexpression.This will improvethe readabilityof your solutionand will make itasierto enter and validate your SpEL expressions.52 +//__Data sink page__// 53 +The data sink page has been moved to the “Explore” tab. 42 42 43 -[[image:Main.Images.Release Blog.WebHome@186-release-blog--spel-expression-readible.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. 44 44 45 -//__ KeepCreate and theCreatePhaseelease insync__//46 -P reviously the Create and theCreate Phase release might havebecomeoutofsync.As a result, comparinga releaseto theCreate Phase release couldyield confusingresults. With thisrelease,wehavemadeseveralimprovements to prevent this from happening.58 +//__Flow Designer performance__// 59 +Performance improvements for the Flow Designer have been implemented. 47 47 48 -//__ Mask password values intheunusedpropertiesoverview__//49 - All propertyvalues ofthe typepasswordcanbemaskedinthepropertiesoverview screen. However,this behaviorwas differentwhenpressingthe unused properties overview. With this release,wehavecorrectedthis behaviortoensurethatpasswords arealsoasked inhis overview.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. 50 50 51 -//__ Press EntertoSearchforproperties__//52 -W ith this release, wehaveadded functionalitythatmakesitpossible to press**Enter**whensearching for properties inthe property overview.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. 53 53 54 -//__ Styling updateon tagselectiononintegrationlevel__//55 - With thislease,wehave improvedthestylingoftagsdisplayedontheintegration andsystemlevel.This way,thetagisbetterreadable,and theicon toremove aselectedtagis completelyshownto the userinsteadofpartly.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. 56 56 57 -//__Enter to close automated flow testing pop-up__// 58 -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. 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. 59 59 60 -//__ Improved namingof downloaded EventStreamingkeystore__//61 - Whendownloading a Keystore that anEventStreamingclientedstoaccessa topic,the name now includestheclientname**and**the environmentoyou can easily discernthe difference between the keystores whendistributingthemtoourclient.74 +//__Highlighting resources__// 75 +The performance of highlighting resources of selected components is improved in Read only mode. 62 62 63 -//__Pop out on the Traces tab within Flow Testing__// 64 -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. 65 - 66 -//__Sorting User Management__// 67 -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. 68 - 69 -//__Improved warning on passthrough API operation__// 70 -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. 71 - 72 -//__Improved update functionality of Swagger file when changing data model__// 73 -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. 74 - 75 -{{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}} 76 - 77 -//__"Disapprove and go to environment"__// 78 -Following the "Approve and go to environment" functionality, we have now expanded that by adding the "Disapprove and go to environment" functionality. 79 - 80 -//__Improve readability of API Gateway operations in Create and Deploy__// 81 -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. 82 - 83 -//__Add Topic Storage information to License Tracker__// 84 -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. 85 - 86 -[[image:Main.Images.Release Blog.WebHome@186-release-blog--topic-storage-info.png]] 87 - 88 -//__Add Compatibility check when importing store items__// 89 -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. 90 - 91 -//__Show dependencies between support objects__// 92 -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. 93 - 94 -//__Improve rendering of validation definition when using multiple namespaces__// 95 -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. 96 - 97 -//__Improved help texts on next-generation runtime functionality across the portal__// 98 -With this release, we have improved several help texts on functionality related to the next-generation runtime that help you while migrating to the next-generation runtime. 99 - 100 100 == **Bug Fixes** == 101 101 102 -//__ Providecorrectfeedback whena flow is transferredtoDeploy forthe first time__//103 - Withthis release,we have madeseveralmprovementstowhatfeedbackis givenothe userwhenmoving aflowfromCreatetoDeployfor thefirst(upon creating your firstdefinitiveversion).This willensurethat no confusingpop-ups willbe shownthat are incorrectandonlyconfusethe userfurther.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. 104 104 105 -//__S how information in theExceptionof errormessages overview__//106 - With this release,we have resolved thebugplaguingthispage. As aresult, you willagainseeinformationonthispagewhenthere isinformationtoow.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. 107 107 108 -//__ Improve styling of cron triggerconfigurationpop-up__//109 - Thetylingof thispop-upmadeitvery hard toconfigurea crontrigger.Wehaveredesigned thestylingto makethepop-upreadable again.85 +//__Error checking__// 86 +Besides checking error header, the error trigger is now configured to check if an error message contains a term. 110 110 111 -//__Prevent flow editing locks in specific situations__// 112 -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. 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. 113 113 114 -//__ Generate property value emptiestheruntimeelection__//115 - With this release,we havefixedthebug thatemptiedtheruntimeselectionupongeneratinga propertyvalue(i.e.,password).93 +//__Unused containers__// 94 +Containers are set inactive when they are unused and removed in Design. 116 116 117 -//__ Makesurenothingofasystem message isditablefrom yourexit__//118 - Before, you couldchangepart of yoursystemmessagefromyour exit(but noteverything). This led toconfusion.As aresult,wehaveowmade sureyoucannotitanythingon thesystem messagelevel fromyourexitto keepit consistentwith our design choices.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. 119 119 120 -//__Prevent users without view rights from seeing a weird screen in those phases__// 121 -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. 122 - 123 -//__Name of starting point of the flow test is incorrect__// 124 -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. 125 - 126 -//__Audit Trail on User Management could break__// 127 -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. 128 - 129 -//__Progress bar in the license tracker is shown twice__// 130 -With this release, we have fixed a bug that showed the progress bar twice in the license tracker. 131 - 132 -//__Compare flows with support objects in the new flow designer__// 133 -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. 134 - 135 135 == **Fancy Forum Answers** == 136 136 137 137 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: 138 138 139 -* [[How to translate CDATA>>https://my.emagiz.com/p/question/172825635703158962||target="blank"]] 140 -* [[SwaggerUI not found>>https://my.emagiz.com/p/question/172825635703171813||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"]] 141 141 108 + 142 142 == **Key takeaways** == 143 143 144 -Thanks to all thathelped build and 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: 145 145 146 146 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 147 147 * If you have feedback or ideas for us, talk to the Platypus 148 -* 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. 149 149 * Clear your browser cache (Ctrl + Shift + Del) 150 150 * Check out the release notes [here] 151 151 * Start thinking about how the license tracker can aid your development ... ... @@ -158,6 +158,6 @@ 158 158 {{info}} 159 159 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 160 160 161 -~*~* Indicates a GEN3-only feature.128 +~*~* Indicates a next-generation-architecture only feature. 162 162 {{/info}})))((({{toc/}}))){{/container}} 163 163 {{/container}}