[Shift][Tab] Keystroke Not Working Correctly?

[KenRyan]

Am I correct in assuming that "[shift][tab]" should be entered into AA as "[Shift Down][Tab][Shift Up]?

When I do that, not only does AA not execute a [shift][tab] (moving backward through dialog box options), but the task editor breaks it into 2 commands as so:

1. [Shift][Down][Tab]
2. [Shift][Up]

Is that correct? Does it have any effect on the keystroke combination?

I attached the task I'm using. The problem comes in at line 19.

Thanks.

Ken

[KenRyan]

I just tried a simplified experiment had discovered that my [Shift][Tab] is being interpreted as just a [tab]. Could that have anything to do with the way AA depicts this command after I hit the "save" button? i.e.

1. [Shift][Down][Tab]
2. [Shift][Up]

Ken

[forumsupport]

Hello Ken,

Automation Anywhere bifurcates the long Keystrokes given in one line at a stretch into several lines. Breaking the keystrokes into several lines would give sufficient time to execute each action smoothly.

Can you please try inserting delay after every Keystrokes command as insufficient delay sometimes skips the command in task? Just double click on Delay/Wait command, specify delay of 200 ms and save it. Copy-paste this command after every keystroke command and save the task.

Hope that helps.

[KenRyan]

That was it! Thanks.

Ken

[philkryder]

I often see this need to separate keystrokes with slight delays.

If they are "needed" for accurate execution, why don't you just have AA put them into each command?

or have an option to add them on the window where we enter the keystrokes...

[forumsupport]

Hello,

IF you record the task, the delays associated with the command are added automatically however, if you create the task through Task Editor then you need to enter delay manually as per the requirement.

[philkryder]

the inconsistency is confusing.

when you look at a command is there any way to tell if the delays have been included or not?

perhaps when we double-click on a command to edit it, you could have part of the edit window show how much delay was built in.

Sometimes the amount of the delay when RECORDING is based on hesitating while thinking and doing the recording.

It would be nice to have the delays EXPOSED to us, so that we knew what was happening.


It would be nice to be able to edit the delay to a reasonable amount.

Regarding my original point: IF DELAYS are needed for accurate execution, then you should have them included whether the command was entered via EDIT or VIA recording.

Phil

[forumsupport]

Hello,

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

It is with customers like you that we update and improve our existing features to fulfill our customer's requirements.