Configuring dashboard templates in the process
When a new dashboard is created, it checks whether there is a template that is registered for the particular dashboard type. Default templates are specified on the server, but project administrators can override them by placing a template in the project's process specification.
About this task
Procedure
To create a dashboard template in the process specification:
Results
Valid mementos for the dashboard templates
When the content of a widget is edited in a dashboard, the data is stored in a data object called a memento as part of the dashboard repository item. It is possible to pre-configure widgets in dashboard templates with the initial content as if the user already edited them. When you edit the template with the process editor, you can specify the memento objects that are used as the initial content. The following table lists the widgets that support mementos and the valid memento structures expected by these widgets to correctly configure them in templates:
Widget | Expected memento structure | Example |
---|---|---|
Work Item Queries | A single property queryStringIds with one or more value children (one for each predefined query id). |
![]() |
HTML | A single property html with the value that represents the raw HTML markup. |
![]() |
Bookmarks | A property bookmarks containing one or more child
memento objects. Each child memento captures one bookmark with the following properties:
A property nextId of type Integer must contain the next index (one higher than the highest index specified in the bookmarks). |
![]() |
Headlines | A multi-page widget containing one or more child memento objects. Each child
memento captures one headline with the following properties:
|