GetText helps you extract values from specific elements or controls within the
desktop application's user interface.

Technical Reference

	Input	DelayAfter: It assists the user to add a delay before initiating subsequent activities. The delay duration here is in milliseconds. By default, it is set to "300" milliseconds. When the option is left blank, the delay will not be considered.
		DelayBefore: It assists the user in adding a delay before starting the execution of the activities. The delay duration here is in milliseconds. By default, it is set to "300" milliseconds. When the option is left blank, the delay will not be considered.
		Execute_by: Gets auto-filled once the "Active Application" is selected. This contains the set of attributes for the specific spied element.
		WaitTime: It enables the user to introduce a delay before initiating subsequent activities. The delay is specified in milliseconds.   By default, it is set to 10000 milliseconds. Leaving the option blank will result in no delay being applied.
	Misc	DisplayName: Displays the name of the activity. The activity name can be customized, which aids in troubleshooting.
		SkipOnError: Specify the "Boolean" value as "True" or "False."   True: Continue executing the workflow regardless of any errors thrown. False: Halt the workflow if it encounters any errors. None: If the option is left blank, the activity will, by default, behave as if "False" were chosen.
		Version: It indicates the version of the feature being used.
	Output	Result: It provides the ability to view the execution status of the activity. It returns values in "Boolean." True: Indicates that the activity has been executed successfully without any errors. False: Indicates that the activity has been unsuccessful due to an unexpected error being thrown.
		Text: The extracted value is stored in the declared variable as a string. This parameter returns the value in "String" datatype.(Check the workflow to see how to store the extracted value in the variable.)

* Represents mandatory fields to execute the workflow

Here's an example of how the “GetText” activity works –

1.       Drag and drop the "GetText" activity onto the designer pane and set as
“StartNode.”

a.       Double-click the activity.

b.       Here we are choosing the "Select Element" option.

c.       Click here to know “Link from Reusable Objects.”

d.       Select the element that needs to be stored. Here, I am selecting the element
from the 'Calculator' app.

e.       Once you have chosen the "Element," the attributes will be stored in the "Spy"
window, along with an "image" of the element.

f.        If you wish to add or remove any attributes, you can edit the "Attributes Editor."
In this case, we are not making any changes in the “Editor.”

g.       Once you click on the "Save" button, the elements will be stored in the activity
window.

h.       Declare a variable to store the spied value in the “Output” window.

i.      There are two methods to store the spied value in the variable.

Method 1: Double-click on the variable parameter in the “Output” section and enter
a name that helps you easily identify it in the flow. Here, I'm using the name "Result"
and using the shortcut key "Ctrl+Q" to create the variable.

Method 2: Click on the variable pane, enter your preferred name (here, I'm using
"Result"), and choose the data type as "String" since the output value accepts the
string data type.

2.       Drag and drop the “WriteLine” activity next to the “GetText” activity to view
the return output of the “GetText” activity.

a.       Enter the variable you declared in the “GetText” activity into the “Text” field.
Here, I’m entering the value as “Result.”

b.       Execute the workflow to view the output.

Click here to know how the activity is used in the workflow.