That graph (meas_bkout_gph01.fex) uses
pmf_booklet_data as the extraction backend, and so *is* detecting the measure type and using RPT_ACTUAL as the field it prints, not the ACTUAL field (which is the raw value only for linearly aggregated actuals and thus wouldn't have been valid for percent, ratio or change in percent type measures). So the aggregation it's using does reflect the measure type and the scale for it.
Perhaps the only thing wrong with this graph is that the
magnitude scale for the Y axis is in thousands. That might be the confusion, and it's a reasonable type of confusion, I'd say.
We don't have an internal way to indicate magnitude for measures in PMF yet. That would be a good idea for the future.
One immediate way to remediate the graph would be to put in logic to detect the magnitude (by, say, grabbing the first 100 rows of RPT_ACTUAL, summing them, and dividing by the count to get an average) and use dialog manager to adapt the graph stylesheet setting for the Y axis label according to the magnitude detected. How's that for a suggestion?
I estimate you'd need to be a WebFOCUS programmer of medium-level skill to accomplish this. I'm sure there are developers out there who have also solved this problem. Anyone want to volunteer sample code?
Bob Jude Ferrante
Director of Business and Development
WebFOCUS Performance Management
Bob_Ferrante@ibi.com
917-339-5105
I'll take any questions about PMF - business or technical - anytime!