Auto Prompting is great... But, is there a way for it to execute the associated fex anytime a selection is made, instead of needing to click on the run button. I'm not a fan of this methodology, but I do have a request to do it, similar to the tableau functionality which we want to obviate.

I can do it easily using the HTML Canvas, etc., but we don't want the users to have to create parm pages when Auto Prompting is out of the box.

This message has been edited. Last edited by: Doug,

You can disable auto prompting by going into the file properties and clicking on "prompt for parameters" checkbox.

Enrique,
I don't think that it's what Doug is looking for.
He wants to have it automatically executed "on selection change" (same feature as if he was using HTML Canvas) even when he's using the auto-prompting.

Doug,
I think that it's not an available feature with auto-prompting.
I found that auto-execute is good when you only have one selection (one param) to choose from.
But from when you have several choices, having the report and/or graph updated each time you perform a selection change, I found it a little "overkill" for the server when it has to update the same reports/graphs 5 times in few second. And this only because you change your selection in the 5 choices you have per example. Especially when you only care of the report/graph result once you performed all your selection change...

Thanks Martin,

You're correct on both accounts. 1) I don't want to disable autoprompting", and 2) I, too, agree that it's "overkill". But, that's what's available in tablow and they want it in WebFOCUS / InfoAssist as well.

Perhaps I'll suggest it as a NFR...

quote:

Perhaps I'll suggest it as a NFR...

Doug, I would put an on_change or on_click event on those controls and refresh the report. Let them have overkill. At least you gave them what they asked for. If you don't, all they will remember is, "WebFOCUS couldn't do it and Tableau could".

This message has been edited. Last edited by: Don Garland,

Thanks All,

We'll most likely build on what we have. Right now (Immediate requirement) is to get this information out there without the filtering.

I'll close this for now with an note.