-
The Dashboard: Open Risks portlet gives an overview of all risks that are not closed or resolved for a single project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The portlet sorts the risks first by priority and then by target date. It displays the name, owner, target date, probability impact, and priority. -
The Dashboard: Open Milestones portlet gives an overview of all milestones that are started or not started for a single project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The milestones are sorted by Due Date. It displays the name, Due Date, Baseline Date, Days Late (Due Date – Baseline Date), and Days Old (Current Date – Due Date). -
The Dashboard: Open Issues portlet gives an overview of all issues that are not closed or resolved for a single project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The portlet sorts the issues first by priority and then by target date. It displays the name, target date, owner, status and priority. -
The Dashboard: Open Issues portlet gives an overview of all issues that are not closed or resolved for a single project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The portlet sorts the issues first by priority and then by target date. It displays the name, target date, owner, status and priority. -
The Dashboard: Financial Summary by Charge Code portlet displays financial information from the project summarized by Charge Code. The portlet is added to the dashboard page of a project and will pull all actuals by charge code on the project. The user may filter by date range to narrow the results. -
The Dashboard: Change Requests portlet gives an overview of all change requests on the project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The portlet sorts the issues first by priority and then by target date. It displays the name, owner, status, target date, approved by, and the priority. -
The Dashboard: Change Requests portlet gives an overview of all change requests on the project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The portlet sorts the issues first by priority and then by target date. It displays the name, owner, status, target date, approved by, and the priority. -
This training document is a Rego Consulting Quick Reference Guide to assist in the replacement of roles with named resources in Clarity’s Modern User Experience. This doc references version 16.1 views. Document provides detail on soft bookings, default allocation and requested manager. Instructions are provided on how to access requests from the Staffing Plan view and how to swap the role for a named resource. If requests are not fulfilled in their entirety, details are provided on how the excess allocation is handled. -
This training document is a Rego Consulting Quick Reference Guide to assist with the creation and editing of Tasks in the Timeline View of Clarity’s Modern User Experience. This doc references version 16.1 views. Doc covers how to create a new task in the Timeline View, how to insert sibling or insert child tasks, how to set Milestones, access the Details pane and add resource Assignments. Also details how to move tasks by clicking and dragging within the Timeline View. -
This training document is a Rego Consulting Quick Reference Guide to assist with the utilization of some of the most common components in Clarity’s Modern User Experience. This doc references version 16.1 views. Document includes content on Grid View, View Options, Adjust Columns, Details Panel, Group By, Save Views and Manage Views. -
A presentation slide deck from Rego University 2022. This document reviews the model for using Clarity and an Agile tool in a Bi-Modal fashion to improve data and reporting.- Agile Journey
- Bi-Modal – what is it really and why is it important?
- Value of getting everything together: Planning to Execution
- How to Integrate

