Changes for page 214 - System Symphony
Last modified by Carlijn Kokkeler on 2024/04/18 13:06
From version 111.1
edited by Erik Bakker
on 2023/05/09 12:45
on 2023/05/09 12:45
Change comment:
There is no comment for this version
To version 362.1
edited by Carlijn Kokkeler
on 2024/01/29 14:49
on 2024/01/29 14:49
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 97-PayAttention1 +213 - Joyful Journeys - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,83 +1,97 @@ 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 lastfew weeks,wehavework hardonimproving our next generationarchitecture and introduced alertingfunctionality on topf our event streamingpattern basedon user feedback. Furthermore thereare severalsmaller feedback items and bugs that havebeenresolved with this release. So without further ado let us diveinto all we haveto offer.6 +**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been achieved. 6 6 7 -== **Event streaming alerting** == 8 8 9 -With this release we expand our alerting functionality into the event streaming pattern. As of now one new "static" alert is introduced for all clients (using event streaming) and two "dynamic" alerts are introduced that you can configure yourself if there is need for it. 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 - The "static"alert we have added raises anlert (and asubsequent email) when theactual topicsizecrosses the thresholdof 80% of the configured maximum retention size on a topic.This alert provides insights whethermessages on it aredeleted due toaizeor time constraint. In cases where data is deletedbecomes the topic was toofull way before the messages should have beenremoved asaresultof theetention hours constraint this alert can beseen as an indication that messages might be deleted before consumer groups had the optionto consume the messages.13 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 12 12 13 -The two "dynamic" alerts we have added mimic the alerting on queue level we already offer to the community. 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 -[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]] 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 -The first new "dynamic" alert allows you to raise an alert once the total number of messages on one (or more topics) is less than a certain number per defined time unit. So for example you can configure an alert once the number of message placed on a topic called "Exception" is less than 15 messages within 5 minutes. 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 -[[image:Main.Images.Release Blog.WebHome@196-release-blog--alert-config-example.png]] 20 20 21 - Thesecond new "dynamic"alertallows youto raise analert once one (or more) consumergroupsismore than X number of messages behind on one ormoretopics. The configuration of thisis comparable as we saw before.25 +== **Formatting & Alignments** == 22 22 23 -For more information on the generic way of working surrounding alerting please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3.WebHome||target="blank"]] and this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-dynamic-alerting.WebHome||target="blank"]]. 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. 24 24 25 -== **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. 26 26 27 -//__ EventStreaming statistics completion__//28 -In thisrelease, wehave updatedtheretrievalofdatatourethatforallmodels,allenvironmentsandalltopicsthis datacan beshowntotheusersotheycanproperly monitortheenvironment.33 +//__Runtime overview image versions__// 34 +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. 29 29 30 -//__ Deploymentsonnextgenerationarchitecture__//31 - Thisrelease fixes severalsmallerbugsandaddsseveralimprovementsto thedeployment processofthe nextgenerationarchitecture.36 +//__Component changes reversion__// 37 +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. 32 32 33 -//__ Cleanqueues option__//34 -Th is releaseintroducesan option for **admins**to cleanqueues that remained aftermigrationtowards the nextgeneration runtime architecture. This willmakethe overview of whichqueues are"problematic"amuchmorerealisticoverview.39 +//__State generation statistics__// 40 +The state generation graphs will now show the correct number of cache hits and misses. 35 35 36 -== **Feedback items ** == 42 +//__Queue browser timestamps__// 43 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 37 37 38 -//__ On-premise containersare starteduponslotwakeup__//39 - Withthis release,wehave added additionalfunctionality to models running in thenextgenerationruntime architecture.With this improvement allon-premisecontainersarestopped whenhecloudslot goesto sleepandarewokenup onceheslotswokenupin themorning.45 +//__Addition and deletion of internal recipients__// 46 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page. 40 40 41 -//__Resource path is shown to the user__// 42 -You can now, without downloading, see the resource path of a resource by viewing the metadata of the resource. You can do so by pressing the "eye" icon to view this information. 43 43 44 -//__Flow designer improvements__// 45 -With this release various improvements have been made to the flow designer. Among others we have improved the overview of what an "unused resource" is. You now have the option to define certain resources that are used but cannot be auto-detected by eMagiz to be an "used" resource to avoid confusion. 49 +== **Feedback Items** == 46 46 47 -//__ Improvedcapabilitiesofa company contact__//48 - Withthisreleasewehaveimproved thecapabilitiesofacompanycontact.As ofnowyou can also adduserstomodelsbelongingtosubcompaniesbelowyour the companytowhichyouarethecompany contact.51 +//__Update flows__// 52 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. 49 49 50 -== **Bug fixes ** == 54 +//__Q&A forum search__// 55 +The option to search by pressing the Enter key has been added to the Q&A forum. 51 51 52 -//__ Optional API parametersarehandled correctly__//53 - Currently,eMagizwouldcreate thewrongexpressionforhandlingoptionalAPIparameters.Withthisreleasewehaveimprovedthe expression insuchaway that alloptional parametersarehandledcorrectlyoutofthebox.57 +//__Memory settings__// 58 +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. 54 54 55 -//__ Without CDM rightsnothing related to any datamodelcan be editednymore__//56 - With thisrelease,wehave madesurethat nothingrelatedtoany datamodelcanbe editedwithout havingthe proper rights.60 +//__Runtime validation__// 61 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 57 57 58 -//__Improved sorting of Design and Deploy archticture__// 59 -With this release, we now ensure that both Design and Deploy architecture are sorted in the same manner to avoid confusion when quickly switching between both views. 60 60 64 +== **Bug Fixes** == 65 + 66 +//__Removal of onramp__// 67 +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). 68 + 69 +//__Runtime statistics details__// 70 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 71 + 72 +//__Deployment prechecks__// 73 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 74 + 75 + 61 61 == **Fancy Forum Answers** == 62 62 63 63 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: 64 64 65 -* [[ jsonPathinSpELexpressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]66 -* [[ Connecting toAzureSQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]67 -* [[ ChangestoJSON api keepbreakingmy modelvalidation,althoughthey areirrelevantto me>>https://my.emagiz.com/p/question/172825635703415225||target="blank"]]80 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 81 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 82 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]] 68 68 69 -== **Key takeaways** ==84 +== **Key Takeaways** == 70 70 71 -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:86 +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: 72 72 73 73 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 74 74 * If you have feedback or ideas for us, talk to the Platypus 75 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 90 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 76 76 * Clear your browser cache (Ctrl + Shift + Del) 77 77 * Check out the release notes [here] 78 78 * Start thinking about how the license tracker can aid your development 79 79 * Start thinking about major, minor, and patch 80 -* Upgrade to the latest build number 81 81 * Keep making great integrations 82 82 83 83 Let's stay in touch and till next time! ... ... @@ -85,6 +85,11 @@ 85 85 {{info}} 86 86 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 87 87 88 -~*~* Indicates a GEN3-only feature. 89 -{{/info}})))((({{toc/}}))){{/container}} 102 +{{/info}} 103 +))) 104 + 105 +((( 106 +{{toc/}} 107 +))) 90 90 {{/container}} 109 +{{/container}}