case_information

The case_information table holds information about every case and sub-case that has been started and not yet purged on the system.

Structure

The case_information table has the following structure:

TABLE case_information (
	 node_id	INTEGER 	NOT NULL,
	proc_id		INTEGER 	NOT NULL,
	casenum	 	NUMERIC(20) 	NOT NULL,
	starter		VARCHAR(49)	NOT NULL,
	casedesc	VARCHAR(24)	NULL,
	procflags	SMALLINT 	NOT NULL,
	next_deadline	TIMESTAMP,
	is_subcase	SMALLINT	NOT NULL,
	is_dead	 	SMALLINT	NOT NULL,
	is_suspended	SMALLINT	NOT NULL,
	major_vers	INTEGER		NOT NULL,
	minor_vers	INTEGER		NOT NULL,
	proc_precedence	INTEGER		NOT NULL,
	started		TIMESTAMP		NOT NULL,
	started_usecs	NUMERIC(10)	NOT NULL)
	using_blob	NUMERIC(10)	)

Column

Description

node_id

ID of the node that this case is hosted on, as defined in the nodes table.

proc_id

ID of the procedure that this case belongs to, as defined in the proc_index table.

casenum

Unique case number for this case, generated from the sequences table.

starter

Name of the user who started this case, as defined in the user_names table.

casedesc

Case description supplied when the case was started.

procflags

The procedure flags that were set at the time the case was started. For internal use only.

Note: These flags are stored to allow consistent operation of the case if the procedure changes status during the lifetime of the case. For example, if the procedure is unreleased when the case is started, but changes to released before the case completes, the case can continue using the original procedure flags.

next_deadline

Date and time that the next deadline expires on this case.

If no deadline is set this value appears as 12/31/3000 11:15:00 PM.

is_subcase

Flag that defines whether this case is a main case (0) or a sub-case (1).

is_dead

Flag that defines whether (1) or not (0) this case has completed.

is_suspended

Flag that defines whether (1) or not (0) the case is currently suspended (from a TIBCO iProcess Objects or SAL application).

major_vers

Major version number of the version of the procedure that this case belongs to, as defined in the proc_version table.

minor_vers

Minor version number of the version of the procedure that this case belongs to, as defined in the proc_version table.

proc_precedence

Stores the procedure precedence settings for opening sub-cases. One of:

• 32 - Released only.
• 64 - Unreleased > Released.
• 96 - Model > Released.
• 128 - Unreleased > Model > Released.
• 160 - Model > Unreleased > Released.

started

Date and time that the case was started, to the resolution of a second.

Note: The started_usecs column can be combined with this column to provide resolution to a microsecond.

started_usecs

Number of microseconds since the start of the seconds value specified in the started column.

using_blob

Decides to use the old memo data table or the new one.

Primary Key

The following primary key is defined for this table.

Key Name

Column(s)

pk_case_info

casenum
proc_id
node_id

Foreign Keys

The following foreign key is defined for this table.

Key Name

Column(s)

Referenced in Table...

fk_case_information1

proc_id
node_id

proc_index

Indexes

The following indexes are defined for this table.

Index Name

Column(s) Indexed

idx_case_info_fk

proc_id
node_id

Table Activity

The case_information table contains one row for every open and closed case and sub-case on the system.

Rows are added, updated and deleted in the following situations.

A row is...

When...

added

a new case or sub-case is started.

updated

any of the following occur:

• a case or sub-case is closed.
• a deadline on a case or sub-case is set or expires.
• a case or sub-case is suspended or re-opened.
• a new version of a procedure is released and the option is chosen to migrate cases (and sub-cases) that use the previously released version to the new version.

deleted

a case is purged.