User Interface

New Keyboard Shortcuts

The following keyboard shortcuts for lists are added in Release 13.2.

Action	Keyboard Combination
Move to the end of a row Note: If the action is on a TSV row, repeat the keyboard combination to leave the TSV section.	Ctrl+Right Arrow
Move to the beginning of a row	Ctrl+Left Arrow
Page up or down	Ctrl+Alt+Up Arrow Ctrl+Alt+Down Arrow
Move to the top or bottom of a list Note: If the action is in the TSV section of a list, repeat the keyboard combination to leave the TSV section.	Ctrl+Up Arrow Ctrl+Down Arrow

Upgrade Action: None

Keyboard Shortcuts for Time-Scaled Values

The following keyboard shortcuts for TSVs are added in Release 13.2.

Action	Key Combination
Select a TSV row	Shift+Ctrl+Right Arrow
Select a TSV column	Shift+Ctrl+Down Arrow
Select a single cell to the left or right of the current cell	Shift+Right Arrow Shift+Left Arrow
Select a single row above or below the current cell	Shift+Up Arrow Shift+Down Arrow
Copy a TSV cell	Ctrl+c
Paste a TSV cell	Ctrl+v
Cut a TSV cell	Ctrl+x
Undo a cut, copy, or paste operation	Ctrl+z

Upgrade Action: None

Time-Scaled Value Edits

You can edit time-scaled values and scroll to different time periods in the grid. The edits you make are preserved even if they scroll offscreen. The edits persist until you save them or dismiss them without saving.

Upgrade Action: None

New Group-by Feature for Charts

The Group-by feature lets you narrow a chart result set based on an attribute that groups the results to provide a better display. The grouping feature is available for object data providers and portfolio system data providers. For example, for a column chart that shows Planned Costs by Project, the readability of the chart depends on the number of projects. Showing 500 projects along the X-axis or Y-axis does not provide a readable chart that scales to the amount of data available. If you group the column chart data by OBS, the chart result set is smaller and more readable.

The grouping feature uses the following chart property fields to control how the results are grouped and aggregated:

Group By Column

Defines the dimension attribute that controls how the chart results are grouped. For example, you can group data by attributes such as OBS, Stage, or Priority.

Group By Function

Defines the aggregation function that is applied to the chart metric. For example, for a column chart of Projects by Planned Costs, you can group by OBS and select Planned Cost as the chart metric. When the Group By column groups the results of the projects by OBS, the planned costs are aggregated based on the Group By Function selection. You can select the aggregation method for the chart metric using one of the following functions: Sum, Average, Count, Minimum, or Maximum.

Note: If you select a date value in the Group By field, you can only select a function of Maximum or Minimum for this field.

The following grouping type attributes (dimensions) are available:

String
Number
Calculated
Formula
Boolean
Lookup
Virtual

You can use the Group-by feature for the following chart types:

Bar
Column
Pie
Line
Area
Funnel

Upgrade Action: None

New Icon for Exports That Are In Progress

A new loading icon displays when you export information to Excel or PowerPoint. Only one export at a time is allowed. While the icon is present, the export is in progress and you cannot request another export. When the export is complete and the icon is no longer present, you can request another export.

Bubble Chart Export Limited to 255 Data Series

When a bubble chart export exceeds 255 data series, an alert is sent and no file is downloaded. Excel and PowerPoint do not support charts with more than 255 data series.

Row Limit Governor for NSQL Queries

To reduce the chance of an NSQL query using too much of server resources, a row limit governor has been established for grid portlets, chart portlets, and cases where XOG query tags are used. The governor restricts the number of rows that are processed to 50,000. The row limit is applied in the following cases:

Scenario 1: A portlet is running a single dimension NSQL data provider, and the portlet has an aggregation row defined.
Scenario 2: A portlet is running a multidimensional NSQL data provider.

When the system detects Scenario 1, the product displays a warning message when the row limit governor has been exceeded. The results up to the row limit (including the aggregation row total) are processed. You can enter filter criteria to display the specific rows you want. This action reduces the number of rows in the result.

When the system detects Scenario 2, the product displays a warning message when the row limit governor has been exceeded. For this scenario, the system does not display any results or aggregation row totals. Because of the nature of multidimensional NSQL queries, the correct result set or aggregation row cannot be determined.

A system administrator can change the row limit value to a smaller number (in this example, 25,000) with the following SQL:

Oracle:

CMN_OPTION_VALUES_UPD_SP('MAX_FETCH_LIMIT', NULL, NULL, '25000', 1);

MSSQL:

exec CMN_OPTION_VALUES_UPD_SP 'MAX_FETCH_LIMIT', NULL, NULL, '25000', 1

Note: Because a higher row limit can degrade the performance and health of the CA Clarity PPM server, we do not recommend increasing the row limit.

Upgrade Action: None