Best practices for running tasks

Follow these suggested best practices to run tasks.

Best Practices for Running a Recorded Task

Use Open Program and Open File commands from the Workbench to open applications
When using the standard recorder to record windows operations, you might experience errors when running the task if the application is not open. To avoid this, edit the task from the Workbench to add Open Program and Open File commands.
Use the Workbench command If Window Exists to check for the window before attempting to open it
This command prevents the possibility of an application not opening properly. You can find the command under other If conditions in the Workbench.
If Window Exists
Use the If Window Exists command in combination with the Open Program and Open Filecommands to launch particular applications.
Wait for Window
Use the Delay Wait for Window command to wait, continue with the next action, or stop the task if the window is not present.
If you do not want to use Workbench commands to open programs or files, ensure that applications necessary to run the task are open prior to running the task
Most of the commands in the standard recorder are based on mouse clicks and keyboard keystrokes. Therefore, you must ensure that application windows used in the process are already open before running the task, or you have added the appropriate commands to open the application windows in the task.
Avoid moving the mouse and keyboard
The standard recorder uses the mouse and keyboard while running a recorded task. If you use the mouse and keyboard at the same time, errors occur. You can track the progress of your running task by using the progress window displayed at the bottom of the screen.
Use wild cards
Specify wild cards (*) for the Image Recognition, Window Exists, and Window Does Not Exist commands.