adding delays

[philkryder]

I often see the advice given to add delays between mouse moves and keystrokes.

If this is really necessary for reliable execution, why not pass along to development to add a 100 ms delay between each keystroke?

whether they are bunched together in a single command or not?

perhaps you could have a default of 100, with the ability to supress the delays at the users express overt choice.

lets try to make AA code no more verbose than necessary.

thanks
Phil

[forumsupport]

Hello Phil,

When you open a recorded task in Task Editor, you can see Delay command after every action you performed, those are the delays associated with the command that are required for errorless execution of a task. Automation Anywhere recorder automatically inserts the delay associated with each action or command. However, when you create the task through editor, you need to insert the delay manually.

We have forwarded your requirement to the product development team for the future version of product.

[philkryder]

thanks -
perhaps on the command editor window there could be a "delay before"
and or
a delay after field.
or, a "delay 50 ms" button that could be added into the keystroke stream so that delays could be inserted among the keystrokes.

What I don't understand about all this is "how does the RECORDER know how much delay is needed?"

Sometimes, I just sit and think a bit before typing or clicking.
Sometimes, the application is faster or slower to respond.

Also,
how does the SPEED option affect this?

if there are MOUSE moves and you choose TURBO, are the mouse moves suppressed and ignored?
And are ALL delays suppressed?

And when "High-Speed Replay (faster)" is chosen,
are the delays reduced from the values coded?
If so, how much delay is retained?
or,
what is done?

Thanks much for all your help in increasing our understanding.
Phil

[philkryder]

thanks -
perhaps on the command editor window for keystrokes there could be a "delay before"
and or
a delay after field.
or, a "delay 50 ms" button that could be added into the keystroke stream so that delays could be inserted among the keystrokes.

What I don't understand about all this is "how does the RECORDER know how much delay is needed?"

Sometimes, I just sit and think a bit before typing or clicking.
Sometimes, the application is faster or slower to respond.

Also,
how does the SPEED option affect this?

if there are MOUSE moves and you choose TURBO, are the mouse moves suppressed and ignored?
And are ALL delays suppressed?

And when "High-Speed Replay (faster)" is chosen,
are the delays reduced from the values coded?
If so, how much delay is retained?
or,
what is done?

Thanks much for all your help in increasing our understanding.
Phil

[TylerMitton]

I'm also interested in the answers to Phil's questions... thanks for posting Phil. And forumsupport I look forward to seeing those answers.

[forumsupport]

Hello,

Regarding your queries,

1) Automation Anywhere Recorder records the delay as time taken for recording the action. If you wait for 2 mins before typing then the recorder will record those 2 mins as delay associated with that particular action. It records the typing speed as well.

2) Turbo speed option, ignores mouse moves and the delays associated with mouse moves also it ignores the delays associated with each command in recorded task. For e.g. while recording you opened a notepad waited for 2 mins and typed something now when you will run this task with turbo speed it will open the notepad and will start typing in it. It will execute the next command (in this case Keystrokes) as soon it finds the notepad window. It will wait intelligently to run the task flawlessly.

3) High-Speed option, ignores only the associated delays intelligently.

Hope that helps.

[philkryder]

so, If I have mouse clicks or mouse moves, I can't really use turbo because some commands will be ignored.

therefore if I want the best speed, I would need to use high speed.
Is that correct?


but, if I ADD delays, as is often suggested, they will NOT be ignored or reduced, but rather kept at the length coded?
is that correct?

how can I determine the minimum length for these added delays that are suggested?
in the past, I had seen 50 ms but recently, I've seen 200ms suggested.
That can add up to a lot of delay.

Is the minimum delay that works based on processor speed?
or?? what?

[forumsupport]

Hello,

Only Mouse Moves will be ignored by Turbo speed (not mouse clicks) so the best speed option is Turbo speed option.

Yes, manually inserted delays are not ignored by the speed options.

Minimum delay varies, depending upon factors like application start-up time, processor speed, etc.

Hope that helps.

[philkryder]

thanks - that does help a bit.

I wish there were some more definitive way to determine how long the hidden delays were going to take.

Two other questions:

Suppose I recorded a session with some long "think time" delay;
is there any way to remove them, or reduce them?
Can I play the task up to the point of the command and then RE-CAPTURE the command?

also, does the SPEED option (such as Turbo) apply to the EXEs we create and run on machines without AA installed?
I'm assuming yes, but would like to verify.

Thanks so much for all your help and PATIENCE.
Phil

[forumsupport]

Hello,

Yes, you can certainly edit those delays using Task Editor. Just figure out the action and its associated delay, double click the delay command and edit it.
While playing the task, you cannot recapture however, using editor you can certainly re-capture the command.

Yes, speed option applies to Exe of task as well.

Hope that helps.