Task and Task Step Property Descriptions

Names cannot contain spaces; they must begin with alpha (a-z, A-Z) characters, and may contain alpha characters (a-z, A-Z), numbers (0-9), the underscore (_), and the dollar sign ($).

Names cannot contain spaces; they must begin with alpha (a-z, A-Z) characters, and may contain alpha characters (a-z, A-Z), numbers (0-9), the underscore (_), and the dollar sign ($).

If set to true, an input value must be supplied by the user of the task, otherwise it will not be executed by the run-time.

If set to false, an input is not required, but if one is supplied, it will be used. If one is not supplied, the runtime behavior is defined by the Input Not Supplied property.

To not send a value for a particular task input in the run-time environment, do one of the following:

• Beans (ITask interface)— enter a Null property value.

• Task files (XML files using the IConnectorAccess interface)— omit the XML tag from the input document. An empty XML tag, for example, <a></a>, is interpreted as an empty string.

Names cannot contain spaces; they must begin with alpha (a-z, A-Z) characters, and may contain alpha characters (a-z, A-Z), numbers (0-9), the underscore (_), and the dollar sign ($).

Names cannot contain spaces; they must begin with alpha (a-z, A-Z) characters, and may contain alpha characters (a-z, A-Z), numbers (0-9), the underscore (_), and the dollar sign ($).

At least one step in a task must be marked as a task endpoint, and regardless of the task flow, every flow of execution through a task must have a task endpoint. Global screen handlers are always task endpoints. When you mark a task endpoint, a red dot is added to the appropriate icon.

Values must be valid integers and cannot be less than one or greater than the height of the screen.

If there are no values set:

• On a formatted screen - the cursor will be placed at the last position set by the host.

• On an unformatted screen - the cursor will be placed at the end of the last text input.

Because cursor placement on unformatted screens is handled automatically, use caution when setting a cursor row position.

When navigating, the cursor displays at the location specified before the transition action is sent, unless the values are blank.

If there are no values set for both the cursor row or cursor column properties and you enter a value for either a row or a column, the corresponding value defaults to 1. Alternatively, if you clear either the cursor row or cursor column values, the corresponding value will also be cleared.

Values must be valid integers and cannot be less than one or greater than the width of the screen.

If there are no values set:

• On a formatted screen - the cursor will be placed at the last position set by the host.

• On an unformatted screen - the cursor will be placed at the end of the last text input.

Because cursor placement on unformatted screens is handled automatically, use caution when setting a cursor column position.

When navigating, the cursor displays at the location specified before the transition action is sent, unless the values are blank.

If there are no values set for both the cursor column or cursor row properties and you enter a value for either a row or a column, the corresponding value defaults to 1. Alternatively, if you clear either the cursor column or cursor row values, the corresponding value will also be cleared.

For example, you have a task that takes an account number (with a task input called AccountNumber) and returns account information. When a bad account number is entered, the host shows a screen that displays an error message in HostField2 and your task is recorded to handle the situation. You can log an Error event to MCS on the step that contains the host error screen using the following User Event Message Expression:

Click the Transition Action Value field for a drop down list of all possible transition actions, including IBM AID keys and other special actions. Unisys and VT AID keys are not included in the drop down list.

Use caution when changing your transition action to a special action, such as <NONE>, <DISCONNECT>, and <WAIT FOR SCREEN (Transient)>. Possible complications can occur, which may involve unrecognized screen errors, task execution errors, and timeout issues.

If you enter an AID key manually, Task Builder contains a translator that formats all AID key designations. It is important that you enter the AID key in the correct format, for example {F8}. If you enter an 8 in the transition action value, the translator will correctly read {F8}. However, if you enter F8, the translator reads F{F8}, which is an invalid command. By correctly entering the AID key, you will avoid navigation errors.

VT-specific expressions for transition actions

The expressions are bracketed { }, and multiple expressions can be included using commas as separators.

• Alpha characters are single quoted. For example, {'a', 'b', 'c', 'd'}

• Numeric characters are sub-expressions, bracketed with the Keypad label. For example, {{Keypad 1}, {Keypad 2}, {Keypad 3}, {Keypad 4}}

• Control + Key sequences are also sub-expressions, bracketed with the Control label. For example, {{Control R}, {Keypad 1}}

• Function keys are supported. For example, {{F5}, 'a', 'b'}

This setting	Does this
Fail Task and Send User Exception	An error is logged to MCS, consisting of the following text, A task endpoint was reached in error. The task has failed. Return Code Number: { } Message: { }, and a User Exception is sent from the Runtime Service to the client application when the step is reached. The task will fail, however, since the Runtime Service can reset the session, the session will not be lost.
Close Connection and Fail Task	An error is logged to MCS, consisting of the following text: A task endpoint was reached in error. The task has failed. Return Code Number: { } Message: { }. When the step is reached, the host connection will be severed, the task will fail, and the session will be lost.

In previous versions of Task Builder, warnings were sent to MCS using the Log Warning to MCS setting under the Task Endpoint Action property. You can now use the Log User Event property to log warning, errors, and information to MCS on any task step. Any warnings that you set up using the previous method will automatically be modified to use the new Log User Event property.

Available adapter classes are those classes that you have saved in the <Install Location>\Attachmate\EAI\recordings\<project name>\scripts\java\classes directory.

1. Step Description
2. Task Endpoint
3. User Return Code Expression
4. User Message Expression
5. Task Endpoint Action

These are step properties that are available when following the standard workflow.

To log events to MCS from within a custom step use the INavSystem interface. Errors (system.logErrorEvent(String)), warnings (system.logWarningEvent(String)), and info (system.logInfoEvent(String)) can be logged to MCS. By extending the BaseCustomNavStep, which must be done when implementing a custom step, you can access the system class member.

The column names must be comma delimited and any leading or trailing spaces are trimmed from each column name. Column names cannot contain spaces; and can only contain alpha characters (a-z, A-Z), numbers (0-9), or the underscore (_).

By default the variables in the expression can refer to both host fields and user fields (screen data). To refer to task data, (task inputs or outputs, and step inputs or outputs), prepend the variable name with the string, Task.  For example, Task.MyTaskInput.