Dashboards
Dashboards can be utilized to organize and visualize data. There are many different use cases for dashboard implementation. For example, a dashboard can be built to monitor and control home devices (thermostats, smoke alarms, door locks). The user of this dashboard is the homeowner, and they may have multiple dashboards to monitor several properties. If the homeowner wants to turn the heat down while they are at work, they can do so using the dashboard.
Another dashboard use case is on the service-side of a business. In this use case, dashboards can be used by maintenance technicians to analyze historical data, monitor changes in current data, and control devices remotely. For example, if a vending machine technician sees that one of the vending machines he is monitoring is critically overheating, he can power off the machine from the dashboard.
In any use case, dashboards give the end user the ability to dynamically control data by viewing, sharing, and rearranging the information as they desire.
There are four major steps to implement a dashboard in ThingWorx. Each of these steps is described in more detail in the sections linked below:
4. Configuring visibility and permissions. By default, dashboards are not visible or configurable for non-administrative users or users that did not create the dashboard. These permissions must be set. While setting visibility allows users to simply know a dashboard exists, it does not allow them to have any CRUD (create, read, update, and delete) permissions. To do this, configuring run time and design time permissions allows users to perform functions such as adding dashboards and adding groups at run time.
Related Links