AX2570

Task Control properties

The following task properties are available for all Scheduler task types. To edit these properties, select the task in the Scheduler job, then expand the Task Control section.

Item	Description
Skip this Task	If selected, the task will not be run when the job is processed. By default, this option is not selected, which means this task will be run.
Process task only if the value of this expression is true	Optional. Enter a logical expression to conditionally process this task depending on whether the expression resolves to true or false at the time the job is executed. If true, the task is processed as normal. If false, the task is skipped. The logical expression is evaluated by the Scheduler server using an IF function. The expression can be any statement that would be valid within an IF function. You can use Excel functions, Axiom functions, and Scheduler job variables in the expression. If you use a job variable in the expression, you must place the variable in double quotation marks unless you expect it to be resolved and evaluated as a number. For more information, see Conditionally processing tasks in a job.
If this Task fails, continue executing subsequent Tasks	If selected, the job will continue processing even if this task fails. By default, this option is not selected. If a task in a job fails, the job is canceled and no further tasks are processed.
Create a Subordinate Job for this Task	If selected, this task will be processed as a subordinate job to the current job. Selecting this check box enables concurrent processing of different tasks, if the option to Wait for all Subordinate Jobs to complete before proceeding to the next Task is not selected. NOTE: This option is not available for Process Plan File tasks.
Wait for all Subordinate Jobs to complete before proceeding to the next Task	If selected, the job will wait for any subordinate jobs to complete before moving to the next task. If this check box is not selected, and the option Create a Subordinate Job for this Task is selected, then tasks can be processed concurrently instead of sequentially. This check box is selected by default for Plan File Refresh and File Processing tasks. For other task types, this option is not selected by default.
Workbook processing engine to use	This option should always be set to Axiom Web Engine. Use of Excel for processing on the Scheduler server is no longer supported. If any tasks in the job involve spreadsheet processing, the spreadsheets are processed using the same spreadsheet emulation engine used by the Windows Client.
Override Log Level for this Task	By default, Scheduler jobs perform logging at the same level that is specified for the application. If necessary, you can override the logging level for a particular task, so that it always runs at a specified logging level. You may want to do this if you encounter performance issues for tasks that generate a lot of logged messages. To do this, select the check box for Override Log Level for this Task, then select the desired logging level from the drop-down list. NOTE: This option is only available for File Processing tasks.

Iteration

This section can be used to optionally enable iterative processing for the task. For more information, see Using iterative task processing.

Item	Description
Iterate this Task	Specifies whether iterative processing is enabled for the task. If enabled, then the task will be performed N times, where N is the number of unique items in the specified iteration column. Job variables can be used to apply the current iteration value and iteration number to the task.
Create a Subordinate Job for each iteration	Specifies whether each iteration is processed as a separate subordinate job. By default, this is disabled, which means that all iterations are processed sequentially within the overall subordinate job created to process the iterations. If enabled, then each iteration is processed as a separate subordinate job, enabling concurrent execution of multiple iterations. This option should only be enabled if the order of iteration processing is not important.
Column	The column that contains the values to iterate over. Use Table.Column syntax to specify the column. Multiple-level lookups can be used. For example, if you specify `Dept.Region`, then the task will be processed once for each unique region value in the column (after applying any filter to limit the list of values).
Group By	Optional. By default, the group by column is the same as the iteration column, so that the task is processed once for each unique value in the iteration column. However, if needed, you can specify a different grouping level. You can use any column or columns that would be valid as the "sum by" level for an Axiom query, where the primary table is the table specified for the iteration column.
Order By	Optional. By default, the values are sorted based on the iteration column, in ascending order. You can specify a different sort column, or use the same sort column but change the order to descending. The sort order is ascending unless the keyword `desc` is used to specify descending order. For example: Dept.Dept desc
Filter	Optional. A filter criteria statement to limit the list of values for the iterative processing. You can use any filter that is valid against the source table (the table of the iteration column).