Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 88.1
edited by eMagiz
on 2023/02/28 13:18
on 2023/02/28 13:18
Change comment:
There is no comment for this version
To version 366.1
edited by Carlijn Kokkeler
on 2024/01/29 15:02
on 2024/01/29 15:02
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 93 -FanOut1 +213 - Joyful Journeys - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. eMagiz1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,87 +1,93 @@ 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 th e lastcoupleof weeks,weworked hard on API improvements and 3rd generationimprovements foryouall tosee.Amongst the API improvementswenow introducethe optiontodefineREST/XMLstructures in yourAPI gateway for your API callerstocall. This bringsmoreoptions to theusercommunity in settingup theAPI Gatewaystructureinaccordancewith the needsanddesires ofthe client.On top of thatweereleased several3rd generationimprovements. Amongstthese we willaddWS-Security functionality to the runtimeandimprovementson viewing release properties. Furthermore we havereleasednewcloud templatesto improvesecurity in our current runtime and improve theauto-healing for3rd generation runtimecloud slots. Lastbut notleastwerelease the firstadaptation of "Stategeneration" that can beimplementedwith the helpof us inyourmodel.In the upcoming monts wewill gatherfeedbackfrom actual clientcases andimprove onthisfunctionality.6 +**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been made so that more user friendly messages are shown that reflect actual behaviour. Moreover, formatting and alignment improvements have been made to improve the user journey. Lastly, we have worked on some more feedback items and several more bug fixes have been done. 6 6 7 -== ** REST XML forAPIGateway** ==8 +== **Pop-up Improvements** == 8 8 9 -{{warning}}Note that a decision needs to be made to select XML or JSON as default format for all your operations hosted in your API Gateway.{{/warning}} 10 +//__Property releases__// 11 +When a new property release is created, this property release can now be viewed and deleted. 10 10 11 - To enhanceyour optionswhen developing an API gateway that can becalledbyothers wenow introduce the option to select XMLasthedefault message format onyourAPI Gatewayattern. You can do this underDesign -> Settings-> API Management. In hereyou can selectand edit thesettings.13 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 12 12 13 -[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-default-setting.png]] 15 +//__Runtime deletion__// 16 +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. 14 14 15 -Every operation made after this decision will default to XML (or JSON which is still the default). Should you want to support JSON on some operations and XML on others you can select a default and manually correct the mediaType for the requests and responses to which it matters. 18 +//__Wiretap & debug error messages__// 19 +The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly. 16 16 17 -[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-change-media-type-setting.png]] 21 +//__Action messages__// 22 +The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour. 18 18 19 -==** Cloud Template update** ==24 +== **Formatting & Alignments** == 20 20 21 -We have released several new Cloud templates which will be installed via the auto-upgrade settings of your model (or manually in case not set). 22 - 23 -====Cloud Template R23 - Single Lane ==== 26 +//__Input fields__// 27 +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. 24 24 25 -This release introduces a new cloud template for all our customers running in a single-lane setup in the 2nd generation runtime. This cloud template will update some specific security settings on these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] 29 +//__UI improvements__// 30 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 26 26 27 -====Cloud Template R6 - Single Lane ==== 32 +//__Component changes reversion__// 33 +In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed. 28 28 29 -This release introduces a new cloud template for all our customers running in a single-lane setup in the 3rd generation runtime. This cloud template will improve the auto-healing functionality of these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] 35 +//__State generation statistics__// 36 +The state generation graphs will now show the correct number of cache hits and misses. 30 30 31 -====Cloud Template R6 - Double Lane==== 38 +//__Queue browser timestamps__// 39 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 32 32 33 -This release introduces a new cloud template for all our customers running in a double-lane setup in the 3rd generation runtime. This cloud template will improve the auto-healing functionality of these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] 41 +//__Addition and deletion of internal recipients__// 42 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page. 34 34 35 -== ** WS-Security on the3rdgenerationruntime**~*~*==44 +== **Feedback Items** == 36 36 37 -To further improve our offering on the 3rd generation runtime we now also have added the necessary functionality to allow you to call SOAP endpoints while utilizing WS-Security as well as securing your hosted SOAP endpoint through WS-Security protocols. Please make sure to create a new release that will trigger the image creation process which will included this feature when necessary. 46 +//__Update flows__// 47 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. 38 38 39 -== **State Generation ~*~* == 49 +//__Q&A forum search__// 50 +The option to search by pressing the Enter key has been added to the Q&A forum. 40 40 41 -With this release we introduce our first "State Generation" functionality to our user community. After rigorous internal testing and use we have now made a stride to also make it available to the user community on specific use case. In the following months we will gather feedback on this to further improve and release it in a simpler and more user friendly way to the user community. 52 +//__Memory settings__// 53 +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. 42 42 43 -{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}} 55 +//__Runtime validation__// 56 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 44 44 45 -== **Feedback items ** == 58 +//__Runtime overview image versions__// 59 +Insight into invented and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview. 46 46 47 -//__Removed OData as option for an API Gateway operation__// 48 -With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform. 61 +== **Bug Fixes** == 49 49 50 -//__ Changes in API Gatewayoperationpaths is automaticallyupdated inCreate__//51 -W henyou changeyour path ona hostedAPI Gateway wewillnowutomaticallyupdate the accompanyingcomponentinyourCreate(all-)entry.63 +//__Removal of onramp__// 64 +We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before). 52 52 53 -{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}} 66 +//__Runtime statistics details__// 67 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 54 54 55 -== **Bug fixes ** == 69 +//__Deployment prechecks__// 70 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 56 56 57 -//__Prevent endless loop in Deploy -> User Management__// 58 -With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion. 59 - 60 -{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}} 61 - 62 -//__Update error handling during migration to the 3rd generation runtime__// 63 -As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration. 64 - 65 65 == **Fancy Forum Answers** == 66 66 67 67 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: 68 68 69 -* [[ Access SpringApplicationContextwithinGroovyScript>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]70 -* [[ Configurationproblem:Failedtolocate'$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]71 -* [[ 503onSOAPWebservicehostedineMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]]76 +* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]] 77 +* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]] 78 +* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]] 72 72 73 -== **Key takeaways** ==80 +== **Key Takeaways** == 74 74 75 -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:82 +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: 76 76 77 77 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 78 78 * If you have feedback or ideas for us, talk to the Platypus 79 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 86 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 80 80 * Clear your browser cache (Ctrl + Shift + Del) 81 81 * Check out the release notes [here] 82 82 * Start thinking about how the license tracker can aid your development 83 83 * Start thinking about major, minor, and patch 84 -* Upgrade to the latest build number 85 85 * Keep making great integrations 86 86 87 87 Let's stay in touch and till next time! ... ... @@ -89,6 +89,11 @@ 89 89 {{info}} 90 90 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 91 91 92 -~*~* Indicates a GEN3-only feature. 93 -{{/info}})))((({{toc/}}))){{/container}} 98 +{{/info}} 99 +))) 100 + 101 +((( 102 +{{toc/}} 103 +))) 94 94 {{/container}} 105 +{{/container}}