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:
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.
A defect in Pegasystems’ code or rules.
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.