Managing System Views

Shows tips for using the dashboard. You can replace these tips with widgets that contain reports, condensed activity views, or external Web pages.

• All users in your system will see the same content for the global context (All), so choose content that applies to a broad set of user privileges.
• Users cannot remove widgets, but they can and add and reorganize their own dashboard widgets.
• Users with the Remote Administration privilege can edit the My Dashboard view, click the System View button, and then change the name and description. After you save your changes, run the view to add widgets to the system view.

Shows the "All Items I Own (Primary)" system feed.

• Users cannot remove feeds added to the My Activity system view, but they can add feeds.
• Users with the Remote Administration privilege can edit the My Dashboard view, click the System View button, and then change the name, description, or settings.
• Changes made to the My Activity system view impact all users.

Has no default feeds. You can add public calendar feeds or leave this task to users, who can create and add their own calendar feeds.

• Users cannot remove feeds added to the My Calendar system view, but they can add feeds.
• Users with the Remote Administration privilege can edit the My Calendar view, click the System View button, and then change the name, description, or settings.
• Changes made to the My Calendar system view impact all users.

A default Kanban board in which columns are mapped to states in the workflow. Created automatically for each application. Each My Kanban view uses a default work item feed that returns all items you own and items that you co-own with other users.

• The My Kanban view is not available in the global context (All) or for application groups.
• Users cannot add or remove feeds from the My Kanban system views.
• Users with the Remote Administration privilege can change settings on each tab in the wizard.
  • This means administrators can change the default column mapping as needed. For example, an administrator might remove columns that were added for states that are not used often.
  • Administrators cannot change the name of the My Kanban view, but they can use the Save As option to create a copy of the view with a new name.
  • Note that if a process app is redeployed after changes are made to the workflow, the My Kanban system view is recreated.
• Other users can use the Save As option to save the My Kanban board as a new Kanban board, and then modify the new board and mapping as needed.

When a process app is deployed, the system performs an analysis of the workflow to determine the optimal mapping of workflow states to columns in the Kanban board. In general, when the analysis is performed three basic criteria are followed in order to determine which columns are created from the states in the workflow:

• In a Kanban board, progress is tracked from left to right. Therefore, successive states in a workflow are mapped from left to right on the Kanban board. If the workflow contains a returned state in which the item can move back in the sequence, the Kanban board will support moving cards from right to left.
• The distance between the columns that are generated should be as minimal as possible according to the workflow. In other words, the first state in the workflow and the second state in the workflow should result in adjacent columns in the Kanban board.
• When moving cards from left to right, the number of possible transitions that are available should be minimal (and ideally, there is only one transition available for a given card). This results in a reduced number of columns on the Kanban board because multiple states will be mapped to a single column in order to always present the fewest number of available transitions.