-
The Creating Dependent Lookups Based On Other Fields On The Same Page document provides the steps needed to allow a user to create lookups whose values are dependent on other fields on the same page. Having the ability to use a lookup field whose list of values change based on other fields values on the same page can help reduce the number of fields that might be required and provide more relevant options to the user based on other data selections.
-
A Quick Reference Card to assist in the creation of project level dependencies. You can create dependency relationships that exist between investments in a portfolio using the dependencies page of project or program properties. A dependency can occur when a task in an investment requires to be completed before a task in another investment can begin.
-
PMOs/EPMOs are feeling some pressure from Agile disruptors in their organizations. Some Agile purists insist that they can do everything with an Agile tool and no PMO governance, but this really isn’t the case. If you belong to a PMO or EPMO, this session will help you to better collaborate with your Agile counterparts in finding better and more holistic solutions to value delivery. Tips on how to use Agile principles in your talking points will also be shared.
-
PMOs/EPMOs are feeling some pressure from Agile disruptors in their organizations. Some Agile purists insist that they can do everything with an Agile tool and no PMO governance, but this really isn’t the case. If you belong to a PMO or EPMO, this session will help you to better collaborate with your Agile counterparts in finding better and more holistic solutions to value delivery. Tips on how to use Agile principles in your talking points will also be shared.
-
The Current Proxies portlet provides a user with an overview of all the resources in the system currently using a proxy. This portlet is helpful to determine a proxy if a user is currently out of the office. The portlet provides several pieces of information related to the resource including: resource names, proxy, start date, end date, days remaining, total days, and if the proxy is active. The user may filter by resource name, proxy name, proxy status (defaults to Yes), and start/end dates (defaults to the current date).
-
The Current Proxies portlet provides a user with an overview of all the resources in the system currently using a proxy. This portlet is helpful to determine a proxy if a user is currently out of the office. The portlet provides several pieces of information related to the resource including: resource names, proxy, start date, end date, days remaining, total days, and if the proxy is active. The user may filter by resource name, proxy name, proxy status (defaults to Yes), and start/end dates (defaults to the current date).
-
The Current Proxies portlet provides a user with an overview of all the resources in the system currently using a proxy. This portlet is helpful to determine a proxy if a user is currently out of the office. The portlet provides several pieces of information related to the resource including: resource names, proxy, start date, end date, days remaining, total days, and if the proxy is active. The user may filter by resource name, proxy name, proxy status (defaults to Yes), and start/end dates (defaults to the current date).
-
The Custom Attributes in System portlet displays all of the custom attributes present in the system and the lookup (if applicable) associated with each. This portlet is useful finding a custom attribute on an object, auditing, or for documentation purposes. The user may narrow the results by object, data type, and last updated date.
-
The Custom Attributes in System portlet displays all of the custom attributes present in the system and the lookup (if applicable) associated with each. This portlet is useful finding a custom attribute on an object, auditing, or for documentation purposes. The user may narrow the results by object, data type, and last updated date.
-
The Custom Attributes in System portlet displays all of the custom attributes present in the system and the lookup (if applicable) associated with each. This portlet is useful finding a custom attribute on an object, auditing, or for documentation purposes. The user may narrow the results by object, data type, and last updated date.
-
A presentation slide deck from Rego University 2022. The document reviews creating views and using Apps in Rally. Then digs into creation of Dashboards.
- Refresh on Creating View and Using Apps
- Introduction to Concepts of Dashboards
- Configuring Dashboards & Apps
- Patterns of Useful Dashboards
- Dashboard Patterns
- Examples
- Exercise: Lets create a Dashboard
-
The Custom License Count portlet displays the license type and number of users with each type of license. This portlet can be modified by adjusting the query to exclude certain rights within manager licenses based on negotiated license types with CA. For example, if CA allows creation of a sub-object to Incident to be included in a Team Member license, this portlet can be used to reflect the true license counts vs. the standard CA license counts.
-
The Custom License Count portlet displays the license type and number of users with each type of license. This portlet can be modified by adjusting the query to exclude certain rights within manager licenses based on negotiated license types with CA. For example, if CA allows creation of a sub-object to Incident to be included in a Team Member license, this portlet can be used to reflect the true license counts vs. the standard CA license counts.
-
The Custom License Count portlet displays the license type and number of users with each type of license. This portlet can be modified by adjusting the query to exclude certain rights within manager licenses based on negotiated license types with CA. For example, if CA allows creation of a sub-object to Incident to be included in a Team Member license, this portlet can be used to reflect the true license counts vs. the standard CA license counts.
-
The Custom License Count Detail portlet displays the license type information for all users within Clarity as well as last login date for clean-up. This portlet can be modified by adjusting the query to exclude certain rights within manager licenses based on negotiated license types with CA. For example, if CA allows creation of a sub-object to Incident to be included in a Team Member license, this portlet can be used to reflect the true license counts vs. the standard CA license counts.
-
The Custom License Count Detail portlet displays the license type information for all users within Clarity as well as last login date for clean-up. This portlet can be modified by adjusting the query to exclude certain rights within manager licenses based on negotiated license types with CA. For example, if CA allows creation of a sub-object to Incident to be included in a Team Member license, this portlet can be used to reflect the true license counts vs. the standard CA license counts.
-
The Custom License Count Detail portlet displays the license type information for all users within Clarity as well as last login date for clean-up. This portlet can be modified by adjusting the query to exclude certain rights within manager licenses based on negotiated license types with CA. For example, if CA allows creation of a sub-object to Incident to be included in a Team Member license, this portlet can be used to reflect the true license counts vs. the standard CA license counts.
-
The Custom Portlet Configs portlet will display all portlets where the user has modified any settings like the filter or list views. This portlet is helpful for troubleshooting and to determine which users may be affected during an upgrade. The portlet may be filtered by several criteria and displays the resource name, ID, OBS path, portlet, and portlet ID.
-
The Custom Portlet Configs portlet will display all portlets where the user has modified any settings like the filter or list views. This portlet is helpful for troubleshooting and to determine which users may be affected during an upgrade. The portlet may be filtered by several criteria and displays the resource name, ID, OBS path, portlet, and portlet ID.
-
The Custom Portlet Configs portlet will display all portlets where the user has modified any settings like the filter or list views. This portlet is helpful for troubleshooting and to determine which users may be affected during an upgrade. The portlet may be filtered by several criteria and displays the resource name, ID, OBS path, portlet, and portlet ID.
-
The Dashboard: Baseline Comparison portlet compares multiple baselines on a single project. The portlet is added to the dashboard page of a project and will pull in both baselines for that project and perform a comparison between the two. This portlet provides a quick way for project managers to view the differences between their baselines, especially if they have multiple members updating the project.
-
The Dashboard: Baseline Comparison portlet compares multiple baselines on a single project. The portlet is added to the dashboard page of a project and will pull in both baselines for that project and perform a comparison between the two. This portlet provides a quick way for project managers to view the differences between their baselines, especially if they have multiple members updating the project.
-
The Dashboard: Baseline Comparison portlet compares multiple baselines on a single project. The portlet is added to the dashboard page of a project and will pull in both baselines for that project and perform a comparison between the two. This portlet provides a quick way for project managers to view the differences between their baselines, especially if they have multiple members updating the project.
-
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.
-
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.