JL

Hi,

I was wondering about best practices regarding data feeds for dashboards. How I see it there are different ways you could choose to do this:

-  One data feed per source: In this data feed you do basic configuration that is applicable for all widgets on a dashboard. You then have most cnfiguraitons/data calculations "in" the widgets of the dashboard

- One data feed per widget: One specific data feed per intended widget for the dashboard.

- One data feed per source, and then connect these to the different widget-specific data feeds.

 

Does enyone have a best practice regarding this they could share? What is best from an adaptability point of view as well as for maintenance of the dashboard?

With best regards,

Jessica

#arisaware #aris #aware #datafeed

by Harm Verschuren
Posted on Wed, 06/29/2022 - 09:33

Hi Jessica,

My best-practice ;-) is to create a (more or less) generic queries that could be the source of a group of data feeds and widgets. Next I create data feeds that result in providing "one goal", or one specific purpose. And also from a pragmatic point, because a data feed seems to be more flexible to create joins, transformations, etc than the query editor of a widget, i.e. technical restriction.
Finally, I create one or more widgets to visualise that "goal" and do as little as possible modifications in the widget query-editor. Only what's needed to visualise. The reason I mention one or more widgets is because you can visualise the same data using more than one widget. Thus reusing the same data-feed. This ensures widgets visualising the same goal or purpose do not return contradicting results (reproducability).

This workflow or best-practice main goal is to centralise all (most) data-feed handling and prevents scattering data-feed handlings all over the place.

Best regards,

Harm

0
by Veronika Ellermann
Posted on Wed, 06/29/2022 - 10:31

Hi Harm,

Yes, that is exactly how I do it. 

It's a bit difficult to see which query relates to which data feed. For that purpose, I also tried to implement a naming convention for the queries that allows me to identify that relationship easily.

Best,

Veronika

0
by Veronika Ellermann
Posted on Wed, 06/29/2022 - 11:00

In reply to by harmv

Great thinking! You now got one additional vote on your idea :)

0
by Jessica Lind Author
Posted on Mon, 07/04/2022 - 13:46

Thank you for your input both of you!:)

0

Featured achievement

Rookie
Say hello to the ARIS Community! Personalize your community experience by following forums or tags, liking a post or uploading a profile picture.
Recent Unlocks

Leaderboard

|
icon-arrow-down icon-arrow-cerulean-left icon-arrow-cerulean-right icon-arrow-down icon-arrow-left icon-arrow-right icon-arrow icon-back icon-close icon-comments icon-correct-answer icon-tick icon-download icon-facebook icon-flag icon-google-plus icon-hamburger icon-in icon-info icon-instagram icon-login-true icon-login icon-mail-notification icon-mail icon-mortarboard icon-newsletter icon-notification icon-pinterest icon-plus icon-rss icon-search icon-share icon-shield icon-snapchat icon-star icon-tutorials icon-twitter icon-universities icon-videos icon-views icon-whatsapp icon-xing icon-youtube icon-jobs icon-heart icon-heart2 aris-express bpm-glossary help-intro help-design Process_Mining_Icon help-publishing help-administration help-dashboarding help-archive help-risk icon-knowledge icon-question icon-events icon-message icon-more icon-pencil forum-icon icon-lock