Task Type (Magic xpa 4.x)
The Task Type can be one of the following:
|
|
Online
|
An interactive task. This is the default setting and means that the task requires user interaction, such as a data entry task.
|
|
|
Batch
|
An automatic task, not requiring any user interaction. Batch tasks are used to perform a process on a set of records from a data source. A Batch task can also perform processes with no data source. Batch tasks are used for processes such as reports, record updates or deletion, and calculations. Although a Batch task has a form, most Batch tasks are executed without anything being shown to the end user.
|
|
|
Browser
|
The program or task runs on a Web browser, using the Browser Client methodology. See Browser Client Applications.
|
|
|
Rich Client
|
The task runs as a Rich Client task, using .NET. See Rich Client Task.
|
|
|
Web Client
|
The task runs as a Web Client task, which is based on HTML front-end. This task communicates with Magic's engine in order to retrieve and upload the data. See Web Client Task.
Since version: 4.0
|
The icons above appear in the task tree to indicate the type of task.
To change the default of this property, use the Default Task Type environment setting.
When changing the Task Type (for example, from Online to Batch), all the transaction properties (that is, Transaction Mode, Transaction Begin, Locking Strategy, and Cache Strategy) for that task revert to their original default values specific to that Task Type.
|
|
The Magic xpa Single User Edition does not support the Browser task type.
|
See also: How Do I Create a Simple Batch Program?
|
|
|
|
Enables end-user interaction.
|
Does not allow end-user interaction.
|
|
Enables the end user to navigate through the Main Source records. Only the records which are scrolled are scanned.
|
The task scans all of the Main Source records within the range criteria. If no Main Source is defined, or the task is in Create mode, the task loops until the end task condition is met.
|
|
The Control logic unit is available. The engine handles logic related to end-user navigation.
|
The Control logic unit is not available, since there is no end-user interaction and the engine does not park on controls.
|
|
The Group logic unit is not available.
|
The Group logic unit is available and enables you to handle groups of data.
|
|
The Task Form is an essential part of the task creation and execution.
|
The Task Form is optional and most of the time is not in use.
|
|
If the data was changed, the Record Suffix logic unit is executed and the data is saved.
|
A record is always saved to the database, even if it was not changed. The Record Suffix logic unit is always executed.
|
|
Events are handled when the task is idle.
|
Events are handled every set period of time or every number of processed records.
|
