Output variables
| Variable | Description |
|---|---|
| NODENAME_ColumnName | The data you are looking for by name for the current row of data, for example, <!TData_EMPLOYEE>. |
| NODENAME_RECORD_COUNT | The number of records that were counted in a query. For example, <TData_RECORD_COUNT> |
|
NODENAME_RowNumber_ ColumnName |
For a specific iteration of a query, the value returned for a specific field. For example, you could use this variable: <!TData_0_EMPLOYEE>. This variable specifies only the information found in 0 for the column Employee. |
|
NODENAME_RowNumber_ ColumnNumber |
For a specific iteration of a query, the value returned for a specific field. For example, you could use this variable: <!TData_0_1>. This variable specifies only the information found in row 0 for column 1. This variable format can be used to refer to variables from outside the query loop, for example, to retrieve the e-mail ID of a user when you know that only one record will be returned. This variable format can also be used when the goal is to compare the results of two rows of data related to the same query. |
Properties
| Field | Description |
|---|---|
| Caption | The name of the activity that is displayed in the Designer diagram. |
| Name |
The name of the Data Service (DME) call to be performed. This name must be unique. This name becomes the prefix for variables from this Data Service (DME) call. For instance, if in an e-mail you wanted to refer to an employee identified by this Data Service (DME) call, you would use this variable: <!TData_EMPLOYEE> You can also reference a variable from a Data Service (DME) call by indicating the order number of the data element returned. For example, <TData_1> refers to the second data element returned, that is, EMPLOYEE. |