Using the Properties View


You can use the right-click menu or keyboard shortcuts to cut, copy, and paste values. Also, if you right-click a property and choose copy from there, both the property and the value are placed on the clipboard.

The Show Categories toolbar button sorts the properties into categories. The Show Advanced Properties toolbar button shows the context for API calls only. Context will be the original host screen name for recorded screens, or the interaction name for API calls inserted outside the context of a specific host screen.

Editing API Calls

The Properties view provides a drop-down lists to make it easier to enter valid values for properties. For example, if you select the inField property for a setFieldValue API call, the value field will become a combo box, allowing you to edit the value directly, or select from a list of field names available on the current host screen, or any valid variables listed in the Variables view. For the inValue property, the list will just include the valid variables. Only variables that match the data type of the selected parameter are valid and will be listed in the value field lists.

Learning More about the API

When you select a property, a description is provided in the designer's status bar. If an input or output parameter is selected, the data type will be displayed in parentheses before the description.

Adding Input Parameters to API Calls

The designer does not support the use of variables as input to API calls unless the variable is the only input. The designer checks the input string against its list of variable names. If it doesn't find an exact match, it just sends the value as a string.

For example, based on the other optimizations described here, you might try to send variable data with a sendKeys call, by entering the following as the inKeys value for a sendKeys call:

${variable_name}@E

This will not send the variable data, but the string ${variable_name}@E. Instead, to provide variable data as input, you'll need to use a separate setFieldValue call, followed by the sendKeys call.

 

Related Topics
Bullet Using the Bridge Designer Views
Bullet Editing API Calls