Use either of these components to cause an automation to wait while other objects such as screens, forms, or applications are created.
|Timeout||The period of time the Wait component allows to elapse for the input component to be created. If the components are not created within this time period the Timeout event is triggered.|
|Handle||The WaitHandle of the components to be created. A control's WaitHandle is a signal that is turned on when a control is created and off when the control is destroyed. The WaitHandle allows callers to wait for the component's creation signal when using the WaitAny or WaitAll components. Click the Plus (+) button on the design block to add Wait inputs for multiple components.|
|WaitHandle||This event applies to the WaitAny component. An output event is triggered when the input WaitHandle indicates the component has been created.|
|TimedOut||This event is triggered if none the WaitHandles gets set before the timeout interval expires.|
|WaitCompleted||This event is triggered if a one of the associated WaitHandles gets set.|
Triggers an event when each member of a set of objects or components is created. If not created within the interval specified in the Timeout property, the WaitAll component triggers the Timeout event.
For example, this method could be used when all objects on a page must be created before executing the next link in an automation.
Triggers events when any one of a group of two or more objects are created. If none are created within the Timeout property value, the WaitAny Timeout event is triggered.
For example, a login process automation with two different login possibilities-one for local and one for remote-could trigger events based on the creation of either screen.