WRK16 - Project (and Portfolio) Status Report

• portfolio_size_limit=

• Greater than 100 projects

• portfolio_size_limit=100

• collapsed
• expanded

• No filtering at all: the user doesn’t have the ability to filter on anything. User parameter will not be usable.
• Filtering by one attribute (e.g.,. work status) with zero or more values selected as the default (Open/Active, Completed, etc.), but the user can change the selections and will have access to all the values in the attribute.
• Filtering by more than one attribute (e.g., work status and milestone type) with zero or more values selected from both structures as the default. Again the user can change the selections from the default but this time, selecting from all the values in both the attributes.
  
  ​In this scenario a logical AND exists between attributes with a logical OR within each attribute. For example if they chose the following: Work Status/Open, Work Status/On-Hold, Milestone Type/Governance, and Milestone Type/Reporting, the filter would be milestones that have both:
  • Work Status of either Open OR On-Hold
  • AND a Milestone Type of either Governance or Reporting

• Only single-select alternate structures for work can be used in the filtering.
• Configuration entries for structure values will use the sequence id (structure_code) of the entry. This value can be found by administering the structure and choosing the option to show the seq id. 
• Configuring an entry of none (if it remains selected) will override any other selections. So if the report is executed with No Filtering and Work Status/Open – the no filtering will be used.
• Only values that are explicitly defined in the configuration structure will be checked by default. There is no option to identify an attribute and have all values selected by default. If you want all work statuses to be checked by default – you have to configure each one in the structure.
• You can make an attribute available without any values defaulted with a special entry. For instance to show all Work Status (Wbs20) values without selecting any you would use this configuration entry:
  ms_filter_value=wbs20$null
  Notice the $null after the structure name.

• exec_sum_header=

• Executive Summary

• exec_sum_header=Executive Summary

This parameter controls the visibility of the Last Change in Value column in the Executive Summary section and the Last Modified column in the Highlight Report section.

• Section Break blank gap between attributes
  section_break1
• Section Break with Heading
  section_break1=heading
• Section Break with Line
  section_break2
• Section Break With Line and Heading
  ​section_break2=heading

• hist_table_title=

• Attribute History

• hist_table_title=Attribute History

• rag_table_title=

• Status Assessment Indicators

• rag_table_title=Status Assessment Indicators

Long Text Fields Section of Report

Determines the list of long text fields near the top of the report

Prior to RPM Analytics v2.2.1 the maximum number of fields that can be configured is 10.

• lt_table_title=

• Long Text Fields

• lt_table_title=Long Text Fields

• collapsed
• expanded

Financial Variance Background Formatting

☑ Enhanced in RPM Analytics v2.2.1

Provides the ability for the customer to configure the background coloring that’s used for the variance columns in the Financials section of the report. Previously the backgrounds were hard coded to be red (if the variance was “worse” than zero) or green (if the variance was 0 or “better”). Worse or better, directionally, depended on the “variance_calculation_type” configuration. That configuration still applies and simply determines if “good” variance (spending less than expected) results in a positive or negative value.
 

To support a wide variety of customer use cases, up to six “bands” that can be defined (a band is a rule and associated color). For instance a rule may be something like, “if the variance is less than or equal to -10% then the color should be red.”

Using this as an example, a band defines a single rule which is composed of a threshold -0.10 (10%) and an operator <= which is used in the comparison to the variance value. Percentages are always entered as their float value (e.g., 25%=0.25).

Since a rule only defines a single operation, the way multiple bands are supported is to use the first matching rule. So you may have the following rules defined:

• Less than or equal to  -10% is Red
• Less than or equal to -5% is Yellow
• Greater than -5% is Green

In this case -25% technically matches the first two rules, but only the first one applies since it’s the first one in the list (the first one listed in the configuration structure).

There MUST be at least two rules defined.

To remove color completely, create two rules that both have the color value set to Transparent (or White).

The color banding logic does not take into account the variance_calculation_type. Therefore ensure that thresholds are appropriate to the positive/negative outcome of your selected configuration.

Nomenclature: Each rule is created using a parameter default called “fm_thresholds”. To the right of the equal sign are three pieces of information separated by the pipe character (“|”):the operator (<, <=, >=, >), the threshold value (entered as a floating point number), and the color (either as a Hex value or CSS color name).

The prior example (three rules) would be entered as follows (and in this order):

fm_thresholds=<=|0.10|#FF0000

fm_thresholds=<=|-0.05|#FFFF00

fm_thresholds=>|-0.05|#00FF00

• 1: indicates baseline-forecast (so a negative cost variance is bad)
• 2: indicates forecast-baseline (so a positive cost variance is bad)

• 1 = the phase level (PPL+1)
• 0 = Project Only (PPL)
• -1 = Hide the table
• 20 (or any high number): will display the full project schedule. 

• show_requested_dates=

• Y = (Yes)
• N (No)

• Show Requested Dates

• show_requested_dates=Y

Possible values;

• hide_milestones=all
  • milestones section hidden
• hide_milestones=none
  • both milestones sections are shown

• Only show milestones in the future
• Only show milestones within a range of time relative to today

• structure =  Orders the milestones in the order they appear in the work schedule
• alpha = Orders them alphabetically
  sorted ascending (A-Z))
• schedule = Orders them based on their actual/schedule finish dates
• baseline=Orders them by their baseline finish dates

• proj_ms_title=

• Project Milestones

• proj_ms_title=Project Milestones

• cri_filter_attrib=attribute ID

• cri_filter_value=attribute value ID

• N=CRI title
• Y=CRI title and description text concatenated together