Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 95.1
edited by Erik Bakker
on 2023/04/11 09:30
on 2023/04/11 09:30
Change comment:
There is no comment for this version
To version 356.1
edited by Carlijn Kokkeler
on 2024/01/29 13:54
on 2024/01/29 13:54
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 +213 - Joyful Journeys - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,95 +1,59 @@ 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.Thistime we added the famous "Hackathon" to the end of the PI week so we could start theEaster break with excellent spiritaftersolving severalsmaller 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!** This release .... 6 6 7 -== **API improvements** == 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. 9 +== **Feedback Items** == 11 11 12 -//__ Switchdefault messageformat__//13 -We haveimprovedthelogic when youswitch themessageformatof your gatewaymessagefrom XML to JSON or viceversa.As aresult, theSwaggerfile will bechangedaccordingly. Once youupdatethe relevant flowin Create and deploy thesolution, theSwagger UI will automatically match the expectedresult.11 +//__Property releases__// 12 +When a new property release is created, this property release can now be viewed and deleted. 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. 14 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 17 17 18 -//__ Improvednaming of API operations whenadding integrations to Create__//19 - Previously whenyou added API operationstothe Createphase, theHTTP operation(i.e., POST, PUT, GET) wasnot visible toauser.Asresult,itbecame tough fora usertodiscern betweenspecific operations oncemultiple of themwere usedononeresource(i.e.,Order, Invoice, Lead). To clarify this for theuser,thedisplaynamedefined in Design(insteadofCapture)is nowusedwithinthisoverviewfortheseoperations.16 +//__Runtime deletion__// 17 +When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container. 20 20 21 -== **3rd generation improvements** == 19 +//__Update flows__// 20 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. 22 22 23 -//__ Updateofthe static alerting engine__//24 - Inthisrelease,wehave updatedthestaticalertingenginethat determineswhenoneofthe staticalerts,as definedbyeMagiz, should betriggered (or not). Thischangewill improvetheperformance of thesolutionand willensurethatthe alertsareactivated correctly.22 +//__Input fields__// 23 +Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions. 25 25 26 -//__ Add "Data pipeline"functionality__//27 - Thisreleaseintroducesthe"datapipeline"functionalitytothe3rd generationruntime.Thisremovesanotherblockage formodelswaiting onthisbeforemigratingtothe3rdgenerationruntime.25 +//__Memory settings__// 26 +It is now possible to change the memory settings of a container before pressing "Apply to environment". Before, it was only possible to view the memory settings if a container was running on AWS or running on a docker machine. 28 28 29 -//__ Fix related tothe debugger__//30 - This releaseintroducesa fixthat allows userstodebugaflowoncethe toggle"SenderrormessagestoeMagiz"is activated.28 +//__Runtime validation__// 29 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 31 31 32 -{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}} 31 +//__UI improvements__// 32 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 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. 34 +== **Bug Fixes** == 36 36 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. 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}} 41 41 42 -== **Feedback items ** == 43 - 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. 46 - 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. 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 -* [[ Entrystopspollingoccasionallysince generation 3>>https://my.emagiz.com/p/question/172825635703376768||target="blank"]]78 -* [[ Invaliddatetime>>https://my.emagiz.com/p/question/172825635703389326||target="blank"]]79 -* [[ Pagingwith aqueue-16>>https://my.emagiz.com/p/question/172825635703389781||target="blank"]]42 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 43 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 44 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]] 80 80 81 -== **Key takeaways** ==46 +== **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:48 +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. 52 +* 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 91 91 * Start thinking about major, minor, and patch 92 -* Upgrade to the latest build number 93 93 * Keep making great integrations 94 94 95 95 Let's stay in touch and till next time! ... ... @@ -97,6 +97,11 @@ 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}} 64 +{{/info}} 65 +))) 66 + 67 +((( 68 +{{toc/}} 69 +))) 102 102 {{/container}} 71 +{{/container}}