Copyright © Cloud Software Group, Inc. All rights reserved.
Copyright © Cloud Software Group, Inc. All rights reserved.


Chapter 7 Cases : case_data

case_data
The case_data table holds the central copy of the field name and value of each assigned field in each case on the system.
When a work item is sent out to a queue, field data is copied from the case_data table to the pack_data table. The client uses the field values in the pack_data table to fill out the form correctly. When the form is kept any changed fields are updated in the pack_data table. When a work item is released field data is moved from the pack_data table to the case_data table.
Structure
The case_data table has the following structure:
TABLE case_data (
node_id
INTEGER NOT NULL,
proc_id INTEGER NOT NULL,
casenum NUMERIC(20) NOT NULL,
field_name VARCHAR(31) NOT NULL,
field_value VARCHAR(255) ,
field_value_N VARCHAR(255) )
“Normalized” value of the field_value value. That is:
Note: This value is stored to make case data searching easier, so that the database can do simple string comparisons, instead of having to do type conversions.
Primary Key
The following primary key is defined for this table.
Foreign Keys
The following foreign key is defined for this table.

1
This key enforces the DELETE CASCADE referential action.

Indexes
The following indexes are defined for this table.

1
This index can impact purge performance. If a large number of purges are being made at the same time TIBCO recommends that you delete this index before performing the purge, then recreate it when the purge has completed.

Table Activity
The case_data table contains n rows for each open case on the system, where n is the number of fields in the case that have assigned data values. Rows are added, updated and deleted in the following situations.

Copyright © Cloud Software Group, Inc. All rights reserved.
Copyright © Cloud Software Group, Inc. All rights reserved.