Adding new job records in a database
New job records can be added to the database table by inserting rows in the "job" table. For new jobs, the following columns are used:
Column | Type | Mandatory | Value | Description |
processed | Integer | Yes | 0 | Indicates processing status of the job. 0 = unprocessed, 100 = processing, 1 = completed |
xml | Blob | Yes | Input data | The input data for the workflow (typically an XML document) |
processingPriority | Integer | No | Priority | The priority of the job. Jobs will be executed in order of priority (highest first) |
created | Datetime | No | Creation time | The time at which the job was created. Oldest jobs are processed first. |
Note that an id for the row will be created automatically when the row is inserted.
When the workflow reads jobs from the database, it will process the jobs in the following order: Highest processingPriority first. If multiple have the same priority, then oldest created date first. If multiple have the same created date, then lowest id first.
At most 10 jobs will be executed in each poll (to limit memory usage).
Additionally metadata values can be attached to each job. Metadata values are added by inserting rows in the metadata table. A metadata value can for instance be used to branch to different sub-workflows. The following columns are used:
Column | Type | Mandatory | Value | Description |
md_key | varchar | Yes | metadata key | The unique key of this metadata value |
md_value | varchar | No | metadata value | The metadata value |
job_id | Integer | Yes | id of job | The id of the job row that the metadata value belongs to |
Related Articles
From database
A workflow can be initiated by a job record in a database table. Only relational databases are supported. Please notice, that this input only supports the very specific table layout as described in the section, Database configuration, where in input ...
Database SQL update
The advanced, utilities workflow component, Database SQL update can be used in order to update or insert data in a table in a database. Enabling custom SQL Custom SQL needs to be enabled in the global System settings. It is divided into two sections: ...
APIs for job logs
Below the APIs for job logs are listed. APIs are introduced here. Get job log names This returns a list of all the logger names that are used in the job log. These can be used as filter criteria when searching the job log. GET ...
Database configuration
The section below describes the database configuration for the From database workflow input, which is very seldomly used. For most you should consider the alternative: From database with custom SQL. To use the database input component, database ...
Database connections
If you want InterFormNG2 to connect to a database in order to get input files for processing, then you need to configure the database as below. This section contains these topics: Prerequisite A prerequisite for a database connection is, that you ...