Open Performance Cloud Release Notes 1/8/19

Track Measure Performance by Last Value

Based on customer feedback, we've introduced a new reporting period type called Last Value. On the Reporting Period tab in the edit modal, you can now see this third type. The following is what you can now see in the Reporting Period tab:

POC_1819_release_1.png

This new reporting type (labeled "Last Value") is best used when there is a delay in data reporting, allowing performance programs to accurately track and display up to date data while affording for a delay in data reporting. If you have a measure that reports data one or two reporting periods after it's been collected, this configuration option is likely the best choice for that measure.

As you can see in the screenshots below, you can see how Last Value, Closed, and Open look before and after these changes. It is important to note that we have not only added a third reporting period type but also changed how missing data displays on the visualization for closed and open periods. See text below the visualizations for more information. (Please scroll from left to right to view the whole table.)

Recent Value Before After
Open Reporting Period

poc_1819_release_2.png

Data has been reported in today's reporting period (January 2019) and missing data plots as a straight line (inheriting the last value reported)

poc_1819_release_3.png

Gaps in the line (missing data) can be closed if cumulative math is enabled from the calculation tab for the following calculation types: Average, Sum, Recent Value, and Count. 

Closed Reporting Period

poc_1819_release_4.png

Data has not been reported since September, but the chart continues to plot the same value through the end of the last closed reporting period. Missing data plots as a straight line (inheriting last value reported). 

poc_1819_release_5.png

Data has not been reported since September and data stops plotting in September. The metric card reads that not enough data is available for the current reporting period because today (in this case January 2019) does not yet have any data. Gaps in the line (missing or delayed data) can be closed if cumulative math is enabled on the calculation tab for the following calculation types: Average, Sum, Recent Value, and Count. A line will plot after September if cumulative math is enabled through the last closed reporting period. This line will plot the same value as last reported in September.

Last Value Reporting Period  

poc_1819_release_6.png

Data has not been reported since September and stops plotting in September. The metric card reads the last value reported. If cumulative math is enabled, the gaps in the line will be closed for the following calculation types: Average, Sum, Recent Value, and Count. The line will still, however, not plot data after September.

 

Other Updates & Bug Fixes

  • Measure updates
    • The date range displayed on visualizations and measures has historically read, in the example of a monthly timeframe or reporting period, something like 1/1/2018-2/1/2018. This has been adjusted so that the date range (using this example), reads 1/1/2018-1/31/2018. You will see this change in visualization flyouts, including those within the metric visualization, and metric card.This adjustment applies to other reporting periods including quarters and years.
    • Two small rendering bugs in the metric card are resolved: (1) When there is not enough data for the current reporting period, the metric card will now render this error correctly for both Count and Sum calculations. (2) When the result is 0 for a Count calculation, it will now render as 0 rather than "No value".
    • When a measure has ended, the metric card will show the appropriate date range based on the last reporting period before the measure end date.
  • Open Performance updates
    • With the introduction of the Action Bar, a bug appeared that introduced the incorrect rendering and publication of goals that had either been migrated to the new goal editor or had been updated and published. This has been resolved.

 

Check out our other Product News, and give us a shout at datainsights-support@tylertech.com with questions or ideas. 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.