Yes, thats the idea. The underlying views are fairly intensive from a DB perspective, so the idea is to limit with prompts when using the report directly.
Now that personalization and bursting is a requirement, that makes the existing report somewhat unusable due to the fact we can't map personalization to prompts.
I'll have to check feasibility of running the report "wide open" so to speak, and then bursting out based on personalization.
Does that make sense?
Regards,
Justin