WizLink – how it works?


Getting applications GUI elements

One of the most important steps during Scenario design is defining GUI elements of the targeted applications. Using Application Hunter tool allows you to easily indicate (“hunt”) any GUI element in the running.  

Operations GUI elements

After hunting, the GUI elements are placed in the Element Toolbox. They are grouped due to the original name of the application. To keep order, pay attention to the windows’ names while hunting – sometimes an application name includes the name of the file open and it will make of the difference seen in Figure […]

Retry timeout parameter

Appears in activities  working with GUI elements. Defines how long WizLink will wait until the activity will execute. Argument is an integer (if greater then 0, it is max time in seconds). Detailed explanation of parameter values below: < -1 Try once. If you fail – set Result to False and finish activity. 0 Try […]

Result Parameter

Used in case activity may fail. Parameter is optional or required. You can specify a boolean which will remember the success or failure of activity execution. An example success may be getting GUI element value, retrieving data from user. Result is set to false for example when GUI element is not found, or setting its’ […]

Log This Activity

Parameter is optional. When the check-box is selected the result of the activity will be stored in a central database for further analysis. Field Description begin_time Timestamp of activity start end_time Timestamp of activity end activity_type Type of activity activity_name Name of activity workflow_name Scenario file name controlled_element_name GUI element name ip Machine IP number […]