Command Flow - More flexability and control over the data captured

The following requests have come from existing customers:
1) Provide limit for the number of tasks collected for command flow during the collection period. This should include a couple of options...Collect the first xxx tasks for the transid...Collect YYY comand flows for a tranid in every ZZZ tasks executions.

2) Create a time/calander option independent of the standard CINT timer options that will allow command flow to be activited and terminated from a timer/calendar. Customers collect dependency IA data frequently, but they want the option to activate and deactive command flow on a different schedule than the dependency data. They also want to be able to schedule when command flow starts/stops so they don't have to do it manually at the specific time.

3) Provide a limit to the amount of data collected for each task. Aetna was using Command Flow to help diagnosis a problem. The target transaction had a loop and the resulting command flow captured hundreds of thousands of records filling up the journal.

10/15 additional requests from Aetna:
4) Change of statements in the IA Command Flow so that the plug in will enable you to pick a range, say 10,000 records from 30,000 to 40,000, and so forth.
3) Have a Find command in Command Flow, so you can do a search for a program or any resource type without having to manually scroll down to look for it.