JobRouter instance data is, stored in multiple tables depending on the number of subtables. The data is stored until the instance is deleted by hand, archived and/or deleted automatically.
The central tables of the instance data are JRINCIDENT and JRINCIDENTS. All general instance and step data is stored there. The JRINCIDENT table contains the instance data, the JRINCIDENT table the step data. This means that one row is created in the JRINCIDENT table for each instance and a row in the JRINCIDENTS table for each actually executed step. Both tables store the general data of the instance or step. This is for example the process name, start date, end date, assigned user, escalation times etc. This kind of data is independent of the process type.
The entries are linked together by the processid. The processid is a unique ID (GUID) assigned for every instance. It acts as the primary key in the JRINCIDENT table. This ID can be used to identify all steps belonging to this instance in the JRINCIDENTS table. The primary key in the JRINCIDENTS table is the workflowid. Every step in JobRouter has a unique ID. The following graphic displays those links, the IDs are shortened for a clearer overview.
For every row in the JRINCIDENTS table, this means every step in JobRouter, a record exists in the process table next to this general data. The process table is used to store all process specific data, e.g. invoice number, invoice date and creditor of an invoice process. As every process uses different data, they are all stored in their own process table. The linking of a row in the JRINCIDENTS table with the process table is done in the process_step_id column in the JRINCIDENTS table and the step_id column in the process table. The following graphic displays those links:
If a process has additional subtables, they are also linked via the process_step_id and step_id columns. A row in the JRINCIDENTS table and the process table might be linked to multiple rows in the subtable, as it is possible for each step to store any amount of data in a subtable. The unique ID in the subtable is a key consisting of step_id und row_id, whereas the row_id starts at 1 and is incremented for each further step. The following graphic displays those links:
