Use cases for Queries

Hi,

I don't think it is a very popular feature in ARIS because of the very limited circle of stakeholders. You cannot run Queries under Viewers, and you cannot even run them under Desktop Designers! So this feature is for a tiny group of specialists with an Architect license. 

And honestly, there are a very limited number of cases in which these queries are useful. In my case, I can remember using them for something other than the investigation of something disastrous that happened with the DB. This is the only group of applicable cases, and fortunately, they are rare cases. 

Where it works excellent is at presentation for the client; there is almost no contest for the show ))

Hi Alexander,

That is sooo intersting! I use them basically every day- not only for dashboards, but also in every day work. But you are right, I am an admin, I can access the queries and I know how to apply them. 
For me, they are so much more powerful than the search: the option to combine a query with an existing one is very handy or simply the possibility to query for objects of a particular model, etc. 
I love the possibility to create table- where I configure highlighting of certain thresholds, where I can write/enter data to attributes. I also like the nested view of my queried data.
I am very surprised that you don't use them- but I do get your point that it is a shame that they are not accessible to designers. However, on the other hand, it also makes sense as designers might not have access to all data so the queries they design might show wrong results (either too much or not the whole picture)... 
 

I cannot imagine the daily usage of queries, to be honest. If you can share some of your business cases, from the need/requirement to delivery (even if you deliver for yourself), that would be great. 

In ARIS 7, it was much better because queries were part of the search, so you could select the definition you needed by making a tricky request. Now it is a very questionable feature (btw, they have not been updating it for 10 years, I believe): the graphic part is absolutely useless for analysis, so there is only a table view that you can use somehow. 

Reports are a more prospective tool: all user types can run them, the analysis is much deeper and more complicated, and of course, the representation. Using reports, you can get a very comprehensive report in the format that the end-user requires. In case of queries, you need to copy that table somewhere (e.g., Excel) and format everything manually. 

That's true- reports are more powerful but take so much more time to create them and with that they are not so handy and flexible. 
You can do a whole lot with queries (see, e.g. the dashboard use cases) if you know how to apply them properly. As far as the formatting is concerned- you can do some of the formatting in ARIS and easily export the table. You're right if you do the copy-paste thing: formatting is lost- but if content is exported, the format remains. 

As you were asking about a use case: let's just take the dashboarding as an example: with reports you would need schedule a report for all languages and store them. With queries you don't have to do that- one query for all so to say.

Hi Veronika, 

Could you share your common use case for dashboarding with queries? If the information is confidential, I think the data could be blurred. 

just about anything, I would say. We discussed some dashboards during this event: https://vimeo.com/918031157/e33a04d19f (but that's in German, though); starting from Glossary, over a visualization of process statuses, etc.

The following video also shows an easy example for the usage of queries: Building Dynamic Dashboards with ARIS Aware | ARIS BPM Community

the missing "prequel" of J-M Erlendson video  Building Dynamic Dashboards with ARIS Aware | ARIS BPM Community 
about building queries as a data source seems to be this 
https://ariscommunity.com/videos/analyzing-impact-and-interconnectivity-aris-queries