Synchronous functions
The below synchronous functions can be used in every field in TruClient that can evaluate JavaScript, such as in step arguments, objects, and descriptor fields. However, while synchronous functions can be used in objects and descriptor fields, this use is not recommended because it can cause unexpected results.
Note:
-
Support for using synchronous APIs in JavaScript code will be deprecated in a future version. OpenText recommends using asynchronous APIs instead. For details, see Replace synchronous APIs with asynchronous APIs.
-
TruClient - Native Mobile scripts do not support asynchronous APIs. OpenText recommends using Generic API Action steps instead. For details, see Replace synchronous APIs with Generic API Action steps.
-
TruClient 2.0 - Web scripts support asynchronous functions only. For details on supported functions, see Using asynchronous functions with TruClient 2.0 - Web scripts.
In this topic:
- General notes on using TruClient functions
- Vuser functions
- Browser functions
- VTS functions
- Environment functions
General notes on using TruClient functions
-
Use escape backslashes in path arguments. For example,
c:\\temp\\myFile.ps1
.
-
The following arguments can be used with any method:
-
object. The step's object as defined in the application.
-
AUT.window. Points to the global window object within the active window or tab of the application.
-
AUT.document. The global document object within the active window or tab of the application.
The AUT API provides a common mechanism for handing the AUT window and AUT document for all TruClient protocols. For details, see Use JavaScript in the AUT window.
-
Vuser functions
Browser functions
VTS functions
Environment functions
See also: