Please enable JavaScript to view this site.

Administration manual

Navigation: Tech Doc > Description of the JobRouter database > Database structure > Instance data

Structure of the JRINCIDENTS table

Scroll Prev Top Next More

The following table shows the structure of the JRINCIDENTS table:

Column name

Data type

Description

processname

(N)VARCHAR(50)

Process name of the instance to be started

version

INTEGER

Process version of the instance to be started (0 for the active process version)

jobfunction

(N)VARCHAR(50)

Name of the assigned Job Function

step

INTEGER

Number of the step

processid

(N)VARCHAR(50)

Instance ID (unique for every instance)

workflowid

(N)VARCHAR(50)

Step ID (unique for each step)

steplabel

(N)VARCHAR(50)

Not used

lastuser

(N)VARCHAR(50)

Username of the previous user

indate

DATETIME

Receipt date

outdate

DATETIME

Completion date

status

INTEGER

Status of the step

-1: Error

0: Open

1: Open, saved

2: Open, returned

3: Completed

4: Completed assigned step

5: Completed last step of a process instance

6: Aborted step

10: Sending is in progress. The status prevents steps with a longer sending process from being visible in inboxes. As soon as the rules have been processed, the step is marked as completed or incorrect.

summary

(N)VARCHAR(255)

Subject

initiator

(N)VARCHAR(50)

Username of initiator

process_step_id

(N)VARCHAR(50)

Step ID of the process table

backlink

(N)VARCHAR(50)

Workflow ID of the last step

username

(N)VARCHAR(50)

Assigned user or user who sent the step

incident

INTEGER

Instance number

escalation_date

DATETIME

Completion Time

description

(N)VARCHAR(50)

Not used

escalation_value

(N)VARCHAR(50)

Escalation value (e.g. username or Job Function)

escalation_status

INTEGER

Escalation status for standard escalations

(Only for JobRouter 2.3 processes)

0: No escalation

1: Escalation

escalation_type

INTEGER

Escalation type:

(Only for JobRouter 2.3 processes)

2: Email to user

3. Assign step to a user

4: Email to Job Function

5: Assign step to a Job Function

notice

(N)VARCHAR(255)

Notice field

notice2

(N)VARCHAR(255)

Answer to requests

assigned

INTEGER

Flag assigned

1: This step was assigned to the user

0: Default

request

INTEGER

Flag request

-1: There was a request in this step

1: Request

2: Response

0: Default

startdate

DATETIME

Not used

visited

INTEGER

Flag already visited

1: The step was opened by someone

0: The step was not opened yet

module_name

(N)VARCHAR(50)

Name of system activity

step_status

INTEGER

Interim status of a step:

-1: System activity finished with error

0: Step was not edited yet

1-98: Interim states used by system activities

99: Work completed, step will be send

pool

INTEGER

Number of the processing pool if multiple pools are used

box_action

INTEGER

Number of the box action

errormsg

(N)VARCHAR(255)

Error message

step_type

INTEGER

Step type:

0: User step

1: Start step

2: Automatic step

3: Decision step

4. Parallelization start step

5: Parallelization end step

priority

INTEGER

Priority

module_type

INTEGER

Module type:

0: PHP module

1: Service module

in_substitution_for

(N)VARCHAR(50)

Username of the original user if step is send to a substitute

sentback

INTEGER

Step was send back

resubmission_date

DATETIME

Resubmission date

recipient

(N)VARCHAR(50)

Recipient field. Contains either the name of a Job Function or the system function of a user in the format #username#.

split_workflowid

(N)VARCHAR(50)

Workflow ID of the step where the parallelization started

locked_date

DATETIME

Not used