Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 101.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 363.1
edited by Carlijn Kokkeler
on 2024/01/29 14:50
on 2024/01/29 14:50
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,107 +1,96 @@ 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 last few weeks, we have focused on wrapping up the previousquarter and starting the new one. When this happens, we go silent forafew weeksto plan for theupcoming quarter during our PI rituals. This timewe added the famous "Hackathon" to the end of the PI week so we could start the Easter break with excellent spirit after solving severalsmaller feedbackitems and bugs reported by you. Several of thosestories will be included inthisand the upcomingrelease.On topf that, we introduce various improvementsto our API Gatewaypattern and our 3rd generationruntimearchitecture. Subsequently, we will release a new runtime image supporting the multiple improvements.6 +**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been achieved. 6 6 7 -== **Release properties** ==** 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 +== **Pop-up Improvements** == 10 +//__Property releases__// 11 +When a new property release is created, this property release can now be viewed and deleted. 10 10 11 - As of now you can not only viewall property values related to a specific release by pressing the wrench icon.You can also create what we call a "property release"on each of the three environment that allows you to quickly changene ormoreproperty valuesand deploy the changes toour environment. When deploying such arelease eMagiz will check onwhich runtimestheproperties areused and onlyexecute the deployactionsfor themachines to which said runtime(s) belong(s).13 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 12 12 13 -{{info}}The following considerations need to be taken into account when using this functionality: 14 -* This functionality works from the moment one runtime is running on the 3rd generation runtime architecture 15 -* This functionality can only change property values. Functional changes need a seperate release that needs to be promoted 16 -* In comparison to standard releases a property release can be created on each environment (as the property value is linked to a specific environment). 17 -*{{/info}} 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. 18 18 19 -== **API improvements** == 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. 20 20 21 -//__ Improved auto-generatederror handling__//22 - Whenyoucreate a newoperationinyourAPI gateway,eMagizwill nowautomaticallygenerate the correctschemas,HTTPcodes,and examplesfor this operation based on industry standards.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. 23 23 24 -//__Switch default message format__// 25 -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. 26 26 27 -//__Re-using elements in gateway message__// 28 -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. 25 +== **Formatting & Alignments** == 29 29 30 -//__I mprovednaming of API operationswhen adding integrationsto Create__//31 - PreviouslywhenyouaddedAPIoperationsto theCreatephase,theHTTP operation(i.e., POST, PUT, GET) was notvisible to auser. Asaresult,it becametough for a user todiscernbetweenspecific operations once multipleof them wereusedon oneresource(i.e., Order,Invoice,Lead). To clarifythis for theuser,thedisplay name defined in Design (insteadof Capture) isnow used within thisoverview for these operations.27 +//__Input fields__// 28 +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. 32 32 33 -== **3rd generation improvements** == 30 +//__UI improvements__// 31 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 34 34 35 -//__ Updateof thestaticalerting engine__//36 -In th is release,wehave updated thestatic alertingenginethatdetermineswhen oneofthestaticlerts,asdefinedby eMagiz, should betriggered(ornot). Thischangewillimprovethe performanceofthelutionand will ensure thatthealerts areactivatedcorrectly.33 +//__Component changes reversion__// 34 +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. 37 37 38 -//__ Add "Datapipeline" functionality__//39 -Th is releaseintroduceshe "data pipeline"functionality to the 3rdgeneration runtime. Thisremovesanotherblockage formodels waitingonthisbeforemigrating tothe3rdgenerationruntime.36 +//__State generation statistics__// 37 +The state generation graphs will now show the correct number of cache hits and misses. 40 40 41 -//__ Fix relatedto thedebugger__//42 - This releaseintroducesa fixthatallows usersto debuga flow oncethetoggle"SenderrormessagestoeMagiz"isactivated.39 +//__Queue browser timestamps__// 40 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 43 43 44 -{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}} 42 +//__Addition and deletion of internal recipients__// 43 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page. 45 45 46 -//__Improved migration process__// 47 -This release introduced a fix that allows a user to migrate event processors with custom error handling without manual intervention. 48 48 49 -//__Deployment plan change__// 50 -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. 46 +== **Feedback Items** == 51 51 52 -{{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}} 48 +//__Update flows__// 49 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. 53 53 54 -== **Feedback items ** == 51 +//__Q&A forum search__// 52 +The option to search by pressing the Enter key has been added to the Q&A forum. 55 55 56 -//__ License Tracker improvements__//57 - Withthisrelease,wehaveaddedseveralnewfeaturesavailableto purchase. Ontop ofthat,additionalinformationonthelicense,suchasaddingnotesandseeingthedatasinkpackets,is nowavailable.54 +//__Memory settings__// 55 +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. 58 58 59 -//__ Ability to view themessagedefinitionfor a topic__//60 - Currently, you can easily navigateto themessagedefinitionofatopicviathe context menuinDesign,even if thereisnoeventprocessor linkedto the topic.57 +//__Runtime validation__// 58 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 61 61 62 -//__R estrictedaccess foruploadingcustom certificatestoendpoints__//63 - Toimproveour cloud offerings' generalsecurityandpreventusersfromuploadingthewrong certificates, wehave nowrestricted accessto thisview toensure thatonlytheadministrator canexecute thischange. Thisallowsfor a discussion betweenthe teamimplementingthesolution andeMagizbeforeactions aretaken.60 +//__Runtime overview image versions__// 61 +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. 64 64 65 -== **Bug fixes63 +== **Bug Fixes** == 66 66 67 -//__ Improved deletionbehaviorforenumerations__//68 - To preventthat eMagiz will incorrectlydeleteenumerationlists when you pressa"Cancel"button,wehave improvedthedeletionbehaviorwhenviewingenumerationsinthe CreatephaseofMagiz.65 +//__Removal of onramp__// 66 +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). 69 69 70 -//__ Prevent"async"api operations__//71 -W iththis release,wehavemovedthebilityto selectthe"async"option when thedefaultsage format isAPI Management.68 +//__Runtime statistics details__// 69 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 72 72 73 -//__ Importing a responsedefinitionbroketherequest definition__//74 - Currently,importinga responsedefinitionbreakstherequestdefinition.With this release,wehavechangedthisbehavior,ensuringthatonlytheresponseefinitionis changedwhen importingand not therequestdefinition.71 +//__Deployment prechecks__// 72 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 75 75 76 -//__Removing a flow does not update the API "all-entry" anymore__// 77 -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. 78 78 79 -//__Stop deployment plan when a property is missing__// 80 -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. 81 - 82 -//__Cap stack trace of error messages and log entries__// 83 -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. 84 - 85 85 == **Fancy Forum Answers** == 86 86 87 87 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: 88 88 89 -* [[ Entrystopspollingoccasionallysince generation 3>>https://my.emagiz.com/p/question/172825635703376768||target="blank"]]90 -* [[ Invaliddatetime>>https://my.emagiz.com/p/question/172825635703389326||target="blank"]]91 -* [[ Pagingwith aqueue-16>>https://my.emagiz.com/p/question/172825635703389781||target="blank"]]79 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 80 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 81 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]] 92 92 93 -== **Key takeaways** ==83 +== **Key Takeaways** == 94 94 95 -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:85 +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: 96 96 97 97 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 98 98 * If you have feedback or ideas for us, talk to the Platypus 99 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 89 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 100 100 * Clear your browser cache (Ctrl + Shift + Del) 101 101 * Check out the release notes [here] 102 102 * Start thinking about how the license tracker can aid your development 103 103 * Start thinking about major, minor, and patch 104 -* Upgrade to the latest build number 105 105 * Keep making great integrations 106 106 107 107 Let's stay in touch and till next time! ... ... @@ -109,6 +109,11 @@ 109 109 {{info}} 110 110 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 111 111 112 -~*~* Indicates a GEN3-only feature. 113 -{{/info}})))((({{toc/}}))){{/container}} 101 +{{/info}} 102 +))) 103 + 104 +((( 105 +{{toc/}} 106 +))) 114 114 {{/container}} 108 +{{/container}}