Batch Task Behavior (Magic xpa 2.x)
Listed below are different characteristics that determine the Batch task behavior.
A Batch task loops through the Main Source records (within a Range criteria). The task repeats the Record Prefix and Suffix logic unit operations for each scanned record.
The task execution is terminated if one of the following conditions is met:
If no Main Source is defined, the Batch task is executed as long as the End Task condition is not met.
This type of task is called a Zero Main Source Batch task.
For example, if you create a program that cycles through Virtual variables, the record loop will be endless, until the End Task condition is met.
When defining a Batch task with a Main Source and the Initial Mode property is set to Create mode, the task behaves like a Zero Main Source Batch task.
For example, if you create a program that only adds records to the data source, the record loop will be endless (no range can apply here), until the End Task condition is met.
|
Note:
|
A Batch form is not seen when called from a Rich Client task. This is because the Batch task runs on the Background engine on the Server side and, therefore, will not show the form.
|
How Do I Stop a Batch Task from Running Forever?
How Do I Improve Performance When a Task is Being Called Repeatedly by a Batch Task?
