Jobs

📄️ Defining a job

A job in USoft is essentially a procedure: a series of operations that form a functional whole and that are performed in a predefined sequence each time the job is called.

📄️ Executing a Job from USoft Binder

You can execute jobs by activating items in a USoft Binder file.

📄️ Executing a Job from the Command Line

To execute a job from the command line, call runbatch.exe with the appropriate options:

📄️ Executing a Job from within a USoft Web Application

To execute a job from a GUI element in a USoft web application such as a button, link, image, or menu element, append a JavaScript script to that GUI element that calls an executeSQLStatement( ) action. Such an action can be used to call a SQL statement by name, for example:

📄️ Executing a Job from within a USoft C/S Application

To execute a job from within a USoft client/server (Windows) application, call the ActionStartJob() action. This action may be called from GUI elements such as menu pages, dialog boxes, buttons, and generally from SQL scripts such as defined in USoft Definer decisions.

📄️ Executing a Job from another Job

You can execute a job from another job:

📄️ Executing a Job from a Constraint

The only way to execute a job from a constraint is to call its job method.

📄️ Invoking a job via Batchrunner

For each job, the internal BatchRunner component automatically contains a job method that has the same name as the job. Calling the job method executes the job.

📄️ Getting job properties from Batchrunner

You can get a runtime property of a batch job currently being executed from the Batchrunner component.

📄️ Passing parameters to Batchrunner

You can pass the following predefined parameters in calls to the BatchRunner internal component.

📄️ Job parameters and variables

Job input parameters

📄️ Job Parameters as Import Task Variables

Use job input parameters as variables during an import task, for example to:

📄️ Import Task Set Virtuals Managing Decision Trees

Complex import tasks often include decision trees: if the current import record meets a SQL condition, then if it meets another condition A should happen, otherwise B, etc.

📄️ Import Task Set Virtuals in Record-by-Record Computations

Suppose a table has a number of columns with computed values, and records in it are processed by an import task. (Computed values can theoretically be extracted from other tables, but because this takes time and the computed values are often re-used, they are stored in a separate field for performance reasons.)