Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 100.1
edited by Erik Bakker
on 2023/04/13 08:56
on 2023/04/13 08:56
Change comment:
There is no comment for this version
To version 246.1
edited by Carlijn Kokkeler
on 2023/11/21 11:35
on 2023/11/21 11:35
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 - 195-EasterParty1 +209 - Max Verstappen - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -2,93 +2,78 @@ 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 thelast few weeks, wehavefocusedwrapping up theprevious 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.5 +**Hi there, eMagiz developers!** We have done ..... 6 6 7 - ==**Releaseproperties**==**7 +{{warning}}Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC. {{/warning}} 8 8 9 -With this release we bring an improved version of the release properties functionality. With the introduction of the 3rd generation runtime the way properties can be updated and when they need to be available for the solution to start up has changed compared to the current runtime architecture. More on that can be found [[here>>Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target= "blank"]] 9 +== **Quicker deployment plan** == 10 +We fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deploynment plan will be finished much quicker now! 10 10 11 -== **API improvements** == 12 +== **Next Generation Architecture Default** == 13 +With this release, the next generation architecture will become the default. New models will use this generation as default. 12 12 13 -//__Improved auto-generated error handling__// 14 -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. 15 +[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]] 15 15 16 - //__Switchdefaultmessageformat__//17 - Wehave improvedthelogicwhenyouswitch theessage formatofyour gateway messagefromXMLtoJSON orviceversa.Asaresult,theSwaggerfilewillbechanged accordingly.Onceyou updatehe relevant flow in Createand deploythelution,theSwagger UI will automatically match theexpected result.17 +== **Cloud Template R11 - Single Lane** == 18 +This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found here 18 18 19 -//__Re-using elements in gateway message__// 20 -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. 20 +== **Cloud Template R13 - Double Lane** == 21 21 22 -//__Improved naming of API operations when adding integrations to Create__// 23 -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. 24 24 25 -== ** 3rd generationimprovements** ==23 +== **Feedback Items** == 26 26 27 -//__Update of the static alerting engine__// 28 -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. 25 +//__Unused properties overview__// 26 +In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are: 27 +* Not used by any runtime that is in the Create phase release. 28 +* Not required by a flow that is in the Create phase release. 29 +* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release. 29 29 30 -//__ Add"Data pipeline"functionality__//31 -Th is release introducesthe"datapipeline"functionalityto the3rd generation runtime.This removesanother blockagefor models waitingonthisbeforemigratingtothe3rdgeneration runtime.31 +//__Send build requests asynchronously__// 32 +The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. 32 32 33 -//__ Fix relatedtothedebugger__//34 -Th isreleaseintroducesfix that allowsusers toebuga flow oncethe toggle "Send errormessagesto eMagiz" isactivated.34 +//__Queue explorer milliseconds__// 35 +The queue browser now displays milliseconds in the timestamps. 35 35 36 -{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}} 37 +//__Cancel and next buttons order__// 38 +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. 37 37 38 -//__ Improvedmigration process__//39 - Thisrelease introduceda fixthatallowsa userto migrateevent processors with customerrorhandlingwithout manualintervention.40 +//__Unused images__// 41 +When a release is removed, the related unused images in the on-premises machines will be removed as well. 40 40 41 -//__ Deployment plan change__//42 - Inthisrelease,the preparerelease step willnotstartautomaticallyanymore.This preventstheuserfrom waiting for this action to befinishedbefore they canontinue deployingthesolutionto theirenvironment.43 +//__Carwash logging__// 44 +A new logging feature enabling us to make better choices in encryption standards will be released. 43 43 44 -{{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}} 46 +//__Static alerts queue consumers__// 47 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server. 45 45 46 -== ** Feedbackitems49 +== **Bug Fixes** == 47 47 48 -//__ LicenseTrackerimprovements__//49 - Withthis release,wehaveaddedseveralnewfeaturesavailable to purchase.Ontop ofthat,additional informationon thelicense,suchas adding notesandseeingthedatasinkpackets,isnowavailable.51 +//__Flow Designer connection line__// 52 +In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas. 50 50 51 -//__ Ability toviewthe messagedefinition for apic__//52 - Currently,youcaneasilynavigateto themessagedefinitionofapicviathecontextmenuinDesign,even ifthereis noeventprocessorlinked to the topic.54 +//__Portal for migrated models__// 55 +We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture. 53 53 54 -//__ Restricted access foruploading custom certificatesto endpoints__//55 - To improveour cloudofferings'generalsecurityand preventusers fromuploading thewrongcertificates,wehavenow restrictedaccesstothisviewto ensure thatonlytheadministratorcanexecutethischange. This allowsfor a discussionbetweenthe teamimplementingthe solutionandeMagizbeforeactionsaretaken.57 +//__Error channel inbounds__// 58 +We added a migration step, where we set the error channel to โerrorChannelโ of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to โerrorChannelโ only for the first inbound in an entry flow. 56 56 57 -== **Bug fixes ** == 58 - 59 -//__Improved deletion behavior for enumerations__// 60 -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. 61 - 62 -//__Prevent "async" api operations__// 63 -With this release, we have removed the ability to select the "async" option when the default message format is API Management. 64 - 65 -//__Importing a response definition broke the request definition__// 66 -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. 67 - 68 -//__Removing a flow does not update the API "all-entry" anymore__// 69 -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. 70 - 71 -//__Stop deployment plan when a property is missing__// 72 -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. 73 - 74 -//__Cap stack trace of error messages and log entries__// 75 -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. 76 - 77 77 == **Fancy Forum Answers** == 78 78 79 79 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: 80 80 81 -* [[Entry stops polling occasionally since generation 3>>https://my.emagiz.com/p/question/172825635703376768||target="blank"]] 82 -* [[Invalid datetime>>https://my.emagiz.com/p/question/172825635703389326||target="blank"]] 83 -* [[Paging with a queue -16>>https://my.emagiz.com/p/question/172825635703389781||target="blank"]] 64 +* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]] 65 +* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]] 66 +* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]] 67 +* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]] 84 84 69 + 85 85 == **Key takeaways** == 86 86 87 -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:72 +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: 88 88 89 89 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 90 90 * If you have feedback or ideas for us, talk to the Platypus 91 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 76 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 92 92 * Clear your browser cache (Ctrl + Shift + Del) 93 93 * Check out the release notes [here] 94 94 * Start thinking about how the license tracker can aid your development ... ... @@ -101,6 +101,6 @@ 101 101 {{info}} 102 102 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 103 103 104 -~*~* Indicates a GEN3-only feature.89 +~*~* Indicates a next-generation-architecture only feature. 105 105 {{/info}})))((({{toc/}}))){{/container}} 106 106 {{/container}}