The system table TB_JOB_STATE stores the job state configuration. To define additional job states do this at the very beginning of all job configuration and data capture. After working with jobs respective job-enabled features do not add any new job states.
|
Attributes for TB_JOB_STATE |
Description |
|
|
ID |
Stores the unique key, which is system-generated. |
|
|
NAME |
Specifies the job name. |
|
|
INITIAL_STATE |
Indicates whether the state is the initial state for each job. 0= No. 1 = Yes. Note:
There can only be one initial state. |
|
|
FEATURES_EDITABLE |
Indicates whether the features can be modified using insert, update, or delete. |
|
|
USE_JOBID |
Specifies the job state whose features are displayed additionally to the features of the current job state. For example, this might specify that all live features are displayed, even if they do not belong to the current job state. |
|
The following table shows the default job states:
|
ID |
Name |
Initial state |
Editable |
Use Job ID |
|
1 |
Live |
No |
No |
No |
|
2 |
Pending |
No |
No |
No |
|
3 |
Open |
Yes |
Yes |
1 (live) |
|
4 |
Deleted |
No |
No |
No |