Window synchronizations such as CitrixWaitForWindow() and CitrixWaitForWindowCreation() are well suited to synchronizing with an application. It is important to synchronize with the application so that the script waits until the application is ready for additional user input. If you do not use synchronizations, the script will most likely overrun the application. Also, synchronization gives you point-in-time reference as to when tasks are completed, effectively measuring response times.
Many tasks that can be performed on an application do not show, hide, create, or destroy windows, they simply change a section of the screen. In such instances you should use the Silk Performer text synchronization functionality.
After recording your script, you can visually add text synchronization points via the TrueLog Explorer Synchronize Text option. Text synchronization works via built-in OCR (Optical Character Recognition).
Silk Performer offers two types of screen synchronizations: wait for content change and wait for content match. This form of synchronization requires a window reference and two sets of x/y coordinates. However since unplanned events can lead to displaced window coordinates, you should use text synchronization whenever possible, and only use screen synchronization when there is no text to compare.
Wait for content change waits until the selected portion of the screen changes, while wait for content match waits until the selected portion of the screen matches what was defined during recording.