Changes for page 212 - Failover Fiesta
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 168.1
edited by Carlijn Kokkeler
on 2023/10/11 13:32
on 2023/10/11 13:32
Change comment:
There is no comment for this version
To version 96.1
edited by Erik Bakker
on 2023/04/11 10:14
on 2023/04/11 10:14
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 - 206-Situational Deployment1 +195 - Easter Party - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -2,108 +2,89 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** In the last few weeks, we have don emuchworkfortheDeployphase.On topofthat,we have workedonseveralstorefunctionalities.Next to this,we have several smaller feedback itemsfromour hackathon efforts that are now releasedtoyou.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 -== ** DeploymentPlan** ==7 +== **API improvements** == 8 8 9 -//__Improved deployment planto maketheprocess better andmore predictable__//10 - Thealgorithmforgenaratingadefaultdeploymentplan isimprovedtokeepjms downtimeandalerting toaminimum.Next to this, thestart/stop/restartmachine deploymentstepsarenowalsoexecutedcorrectly forawsand on-premisesmachines.9 +//__Improved auto-generated error handling__// 10 +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. 11 11 12 -//__ Editingreleaseproperties__//13 -With this release,it will bepossibletochange thedescriptionofa propertybyeditingthe property.12 +//__Switch default message format__// 13 +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. 14 14 15 -//__ JMSmemory settingcheck__//16 - Achangeinmemorysettingstriggers redeploymentofthecontainer now.15 +//__Re-using elements in gateway message__// 16 +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. 17 17 18 -//__ Properties tab__//19 - We haveremovedthedeprecatedtabProperties in theDeploy phase.18 +//__Improved naming of API operations when adding integrations to Create__// 19 +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. 20 20 21 -//__Cleanup old images__// 22 -When a release is removed, the related unused images in the on-premises machines will be removed as well. 21 +== **3rd generation improvements** == 23 23 24 -//__ Performanceimprovementsfor loadingreleases__//25 - Performanceimprovements havebeenimplementedforloadingreleasesinDeploy.Releasesshouldnowloadfaster thanbefore.Allfunctionalityshouldremainexactlythesame asbefore.23 +//__Update of the static alerting engine__// 24 +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. 26 26 27 -== **Store Improvements** == 26 +//__Add "Data pipeline" functionality__// 27 +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. 28 28 29 -//__ Messageefinitionelementsorder__//30 - Wefixed anissuethattheorder ofmessagedefinition elementswaschangedafterbeing imported.29 +//__Fix related to the debugger__// 30 +This release introduces a fix that allows users to debug a flow once the toggle "Send error messages to eMagiz" is activated. 31 31 32 -//__Improting a store item with synchronous message definitions__// 33 -We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions. 32 +{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}} 34 34 35 -//__Imp orting storeitems containingstatic copies__//36 - Wefixed anissuethat storeitemsweremissing staticcopies. Now,store items with staticcopiesareimported correctly.34 +//__Improved migration process__// 35 +This release introduced a fix that allows a user to migrate event processors with custom error handling without manual intervention. 37 37 38 -//__ Importing Storecontent__//39 - Wefixedan issue that blockedyou from importingStorecontentintheDesignphase. The messagedefinitionsand message mappingsarenowimportedcorrectlyastheoriginalcontentin theitemoftheStore.37 +//__Deployment plan change__// 38 +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. 40 40 41 - ==**FeedbackItems**==40 +{{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}} 42 42 43 -//__Alerting manual pause__// 44 -A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment. 42 +== **Feedback items ** == 45 45 46 -//__ Orderingof graphsin Manage__//47 - ThegraphsinManage are noworderedaccordingtoimportance. Thismeansthatruntimestatisticsaresortedby "ProcessCPU usage"(highest first),queuestatisticsaresorted by "Messagesinqueue" (highestfirst), andHTTP statisticsaresorted by "Unsuccessful requests"(highestfirst).44 +//__License Tracker improvements__// 45 +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. 48 48 49 -//__ UTCtimes inGrafanapanels__//50 - All Grafana panelsnowshowUTC times, whicharenormallyusedineMagiz,insteadoflocal(browser)timezones.Thisway,itiseasiertomatchgraphswithloggingeventsoralerts.47 +//__Ability to view the message definition for a topic__// 48 +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. 51 51 52 -//__ Update flowdesignerversion__//53 -T he frameworkusedin the flowdesignerhasbeenpdatedto the latestversion.50 +//__Restricted access for uploading custom certificates to endpoints__// 51 +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. 54 54 55 -//__Carwash track TLS versions in logging__// 56 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards. 53 +== **Bug fixes ** == 57 57 58 -//__ Movingchannelsinthe flowdesigner__//59 - Movingalready attachedchannelsintheflowdesigner hasbeen madeligthlyeasier.55 +//__Improved deletion behavior for enumerations__// 56 +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. 60 60 61 -//__ Topic sizes descriptionchange__//62 - Inthechangedescription (andHistory) whenalteringthetopicsizeof a topic thenewandoldvaluewereswitchedaroundcreatingconfusion,thishasbeenresolved.58 +//__Prevent "async" api operations__// 59 +With this release, we have removed the ability to select the "async" option when the default message format is API Management. 63 63 64 -//__ Passwordchange notification__//65 - Whenan accountpasswordchange request ismade, evenwhen thisfails,a mail is sentto theaccount ownerto informtheowner about theaction.61 +//__Importing a response definition broke the request definition__// 62 +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. 66 66 67 -//__ Passwordcomparison__//68 -When changingapassword,itiscomparedtoalistofknowndatabasebreachesfor security.A warningisshown when thepasswordcorrespondswithapasswordinhedatabase.64 +//__Removing a flow does not update the API "all-entry" anymore__// 65 +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. 69 69 70 -//__ Inactiveuseralerting__//71 - Inactivatedusers arewremovedfromallalert settings(included“disabled“settings)toavoidundesirable notifications.67 +//__Stop deployment plan when a property is missing__// 68 +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. 72 72 73 -//__ AlphabeticalsortingonuserlevelinHTTPstatistics__//74 - Variables in the3rd generationruntimesHTTPstatisticsdetailpages are nowsortedcaseinsensitive.70 +//__Cap stack trace of error messages and log entries__// 71 +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. 75 75 76 -//__SOAP Web services path__// 77 -Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings. 78 - 79 -== **Bug Fixes** == 80 - 81 -//__Flow designer styling__// 82 -The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities. 83 - 84 -//__Partial search for messages__// 85 -It is now possible to search on messages partially in Manage Monitoring. For example, search for Uptime can be done by searching for "up" "time" "ptim". 86 - 87 -//__Disk usage after cloud template update__// 88 -In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates. 89 - 90 -//__Error handling migration__// 91 -If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false. 92 - 93 - 94 94 == **Fancy Forum Answers** == 95 95 96 96 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: 97 97 98 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]] 77 +* [[Entry stops polling occasionally since generation 3>>https://my.emagiz.com/p/question/172825635703376768||target="blank"]] 78 +* [[Invalid datetime>>https://my.emagiz.com/p/question/172825635703389326||target="blank"]] 79 +* [[Paging with a queue -16>>https://my.emagiz.com/p/question/172825635703389781||target="blank"]] 99 99 100 100 == **Key takeaways** == 101 101 102 -Thanks to all whohelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:83 +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: 103 103 104 104 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 105 105 * If you have feedback or ideas for us, talk to the Platypus 106 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 87 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 107 107 * Clear your browser cache (Ctrl + Shift + Del) 108 108 * Check out the release notes [here] 109 109 * Start thinking about how the license tracker can aid your development ... ... @@ -116,6 +116,6 @@ 116 116 {{info}} 117 117 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 118 118 119 -~*~* Indicates a next-generation-architecture only feature.100 +~*~* Indicates a GEN3-only feature. 120 120 {{/info}})))((({{toc/}}))){{/container}} 121 121 {{/container}}