Skip to main content

I don't understand the difference between a knowledge model view and a dashboard. The same components exist in views and dashboards, but who uses the views and when?

Hello,

 

They are similar in functionality but have different approaches, for example:

A dashboard focuses more on analysis, either exploratory or confirmatory, so it is simpler to create and is customizable and easily modified. Practically the only knowledge required is PQL, since all the interface is Drag & Drop.

On the other hand, a view has a focus on execution, you can create action buttons in a dasboard but this feature is refined in a view, on the other hand, the views require a Knowledge Model necessarily, the KM is the "brain" of your views and allows you to reuse objects or kpis that you have created in different views . To create a view requires a little more technical knowledge, especially of YAML, to use all the available functions.

 

For example, if the user is a consultant or an auditor, he can use dashboard to perform analysis and get to know your as-is process.  

If he is a business user, he can use the views as a daily work tool that allows him to work in an intelligent and prioritized way or as a source of consultation on how is the execution of his process.

 

I hope it helps you.

 


Hello,

 

They are similar in functionality but have different approaches, for example:

A dashboard focuses more on analysis, either exploratory or confirmatory, so it is simpler to create and is customizable and easily modified. Practically the only knowledge required is PQL, since all the interface is Drag & Drop.

On the other hand, a view has a focus on execution, you can create action buttons in a dasboard but this feature is refined in a view, on the other hand, the views require a Knowledge Model necessarily, the KM is the "brain" of your views and allows you to reuse objects or kpis that you have created in different views . To create a view requires a little more technical knowledge, especially of YAML, to use all the available functions.

 

For example, if the user is a consultant or an auditor, he can use dashboard to perform analysis and get to know your as-is process.  

If he is a business user, he can use the views as a daily work tool that allows him to work in an intelligent and prioritized way or as a source of consultation on how is the execution of his process.

 

I hope it helps you.

 

@andré.tafur  Hello, Thank you for your reply. I have one question. I understand that views are more intelligence than dashboards. My feeling is that if the user is a business user, he/she has less knowledge of Celonis, but is the business user also responsible for setting up the views?


@andré.tafur  Hello, Thank you for your reply. I have one question. I understand that views are more intelligence than dashboards. My feeling is that if the user is a business user, he/she has less knowledge of Celonis, but is the business user also responsible for setting up the views?

Not necessarily, in Celonis there are two types of users formally called Analyst User and Business User.

Analyst User: They are those users who can build and modify celonis objects (data connection, dashboards, views, KM, etc) they have the necessary permissions for this.

Business User: They are generally End Users who simply use the platform without the need to modify or build objects, if they need any requirement they must rely on the Analyst Users for it.


@andré.tafur  Hello, Thank you for your reply. I have one question. I understand that views are more intelligence than dashboards. My feeling is that if the user is a business user, he/she has less knowledge of Celonis, but is the business user also responsible for setting up the views?

@andré.tafur  Thank you for your reply.I have one more question.Is there anything that cannot be done on the dashboard but can only be done in the View? Or vice versa?


Please check the: https://academy.celonis.com/learn/learning-path/build-views-and-knowledge-models training. It's all there.


Reply