Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Timeliness function aliases break average computation on null



Several of the "timeliness" function aliases must be modified to return a 0 (zero) instead of a NULL for all the CASE statements that return false. When they return a NULL value, using the AVERAGE summarize function in a report definition returns an incorrect result. The following Function Aliases must be updated to return a 0 when the result is false: 
  • pxSLAAgeByClassTimeliness 
  • pxSLAAgeTimelines
  • pxSLAHistoryTimeliness 
  • pxSLAAssignTimeliness 

Error Messages

Not Applicable

Steps to Reproduce

Attempt to use an AVERAGE summarize function in a report definition when one of the timeliness function aliases returns a NULL result. Resulting average computation is clearly incorrect.

Root Cause

A defect in Pegasystems’ code or rules.


Apply HFix-27382.

Published May 19, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us