If you create an Insert action during flow recording then the host editor also creates at the same time from the information in the Insert action one or more mappings that describe how the operation specified in the Insert action is to be performed (see Overview of creating an action). The host editor also prompts you for the name of a variable to be used in the mapping. (The variable is used to store the text that the Insert action reads from the application screen.)
In contrast, if you create the Insert action during screen operations recording or in the screen operations editor, then the mapping or mappings are not created. To create the necessary mapping or mappings you must start a flow recording and play back the screen interaction containing the new Insert action when you have navigated to the appropriate application screen (see Overview of creating an action). The host editor then prompts you for a variable to be used in the mapping.
Points to remember when you use the Insert action:
If the Insert action attempts to write text into a protected field then the session generates an input inhibited error.
The Insert action does not clear the target field to blanks before writing text into it.
The Insert action starts writing the text from the variable into the target field at the first character position in the field.
| Property: | Description: |
|---|---|
| Encrypted | This property indicates whether the specified field is a hidden field in the corresponding application screen. Do not change the value of this property. |
| Field | Required string. This property specifies the fully qualified
name of the field into which the text is to be written. The fully qualified
name consists of:
|
| Name | Optional string. This property specifies the custom name of the field, if you have provided a custom name (such as CustomerBalance). |
| Value | Optional string. This property specifies the default
text to be written into the specified field.
|