locked
feature request - disable higher scoped commands at the QA level RRS feed

  • Question

  • Hi,

    I am pretty sure this feature is not available so I will ask that it get added in the next release as we have had several applications that would have used it already had it been there.

    What we need to do is to be able to 'turn off' active commands at a per QA level. So the scenario is we have a high level 'operator' command under whose scope all QAs fall. But there are one, or a few, of those QAs where we don't want that command to be active. Right now, we are forced to add a handler for the command at a lower level (scope) and when we get it, we simulate getting a noReco condition. Simulating a noREco condition is a pain because now we have to manage prompts differently for the QA, and we have to manage our own noReco counter for error handling.

    If this feature exists or if there is a better way to handle this, then please let us know.

    Thank you,

    Mike

    Thursday, August 16, 2007 10:16 PM