Changes for page 212 - Failover Fiesta
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From 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
To version 292.1
edited by Carlijn Kokkeler
on 2023/12/18 12:20
on 2023/12/18 12:20
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 -1 95-EasterParty1 +211 - Log Luminary - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,90 +1,67 @@ 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!** 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 +**Hi there, eMagiz developers!** 6 6 7 -== ** API improvements** ==8 +== **TBD** == 8 8 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 -//__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 -//__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. 12 +== **Feedback Items** == 17 17 18 -//__ Improved namingof API operations when adding integrationstoCreate__//19 - Previously whenyou added API operations to the Createphase, the HTTP operation (i.e., POST, PUT, GET) wasnotvisibleto a user. As a result,it becametoughforauserto discernbetweenspecific operations oncemultipleofthemwereused ononeresource(i.e., Order, Invoice, Lead).To clarify this fortheuser, the display name defined in Design(insteadofCapture)isnow used withinthis overview for these operations.14 +//__Missing properties overview__// 15 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 20 20 21 - ==**3rd generation improvements** ==17 +ADD FIGURE 22 22 23 -//__ Updateofthe staticalertingengine__//24 - Inthisrelease,wehaveupdated the staticalertingengine thatdetermineswhenoneofthestatic alerts,asdefinedbyeMagiz,should betriggered (or not). This changewill improvetheperformanceofthesolutionand will ensurethatthealertsare activatedcorrectly.19 +//__Container version overview__// 20 +Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release. 25 25 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. 22 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]] 28 28 29 -//__ Fixrelatedto thedebugger__//30 -Thi srelease introduces afixthatallowsuserstodebug a flow once the toggle"Send errormessages toeMagiz"isactivated.24 +//__Improved deployment process__// 25 +The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance. 31 31 32 -{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}} 27 +//__Rebuilding of images__// 28 +Changing the list of flows that should run on a container will now trigger the rebuilding of images. 33 33 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. 30 +== **Bug Fixes** == 36 36 37 -//__ Deployment planchange__//38 - In this release,thepreparerelease step willnotstart automatically anymore.This preventsthe userfromwaitingforthisactionto be finishedbeforetheycan continuedeploying thesolutionto theirenvironment.32 +//__Runtime metrics processing__// 33 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 39 39 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}} 35 +//__Deployment plan__// 36 +We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck. 41 41 42 -== **Feedback items ** == 38 +//__View all store items__// 39 +An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer. 43 43 44 -//__ LicenseTrackerimprovements__//45 -W iththisrelease, we haveaddedseveral new featuresavailable topurchase. Ontopofthat, additionalinformationonhe license,such as addingnotesandseeingthedatasinkpackets,isnowavailable.41 +//__Out of memory behavior__// 42 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs. 46 46 47 -//__ Abilityto viewthemessage definition for a topic__//48 - Currently,youcaneasilynavigate to themessagedefinition of a topicviathecontextmenuinDesign,evenif thereis noeventprocessor linkedtothetopic.44 +//__Max fetch size__// 45 +In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior. 49 49 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. 52 - 53 -== **Bug fixes ** == 54 - 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. 57 - 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. 60 - 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. 63 - 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. 66 - 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. 69 - 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. 72 - 73 73 == **Fancy Forum Answers** == 74 74 75 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: 76 76 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"]] 51 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]] 52 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]] 53 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]] 54 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]] 55 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]] 80 80 57 + 81 81 == **Key takeaways** == 82 82 83 -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:60 +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: 84 84 85 85 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 86 86 * If you have feedback or ideas for us, talk to the Platypus 87 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 64 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 88 88 * Clear your browser cache (Ctrl + Shift + Del) 89 89 * Check out the release notes [here] 90 90 * Start thinking about how the license tracker can aid your development ... ... @@ -97,6 +97,12 @@ 97 97 {{info}} 98 98 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 99 99 100 -~*~* Indicates a GEN3-only feature. 101 -{{/info}})))((({{toc/}}))){{/container}} 77 +~*~* Indicates a next-generation-architecture only feature. 78 +{{/info}} 79 +))) 80 + 81 +((( 82 +{{toc/}} 83 +))) 102 102 {{/container}} 85 +{{/container}}