Open topic with navigation

TIBCO iProcess® Engine 11.9.1

# proc_index

The `proc_index` table holds information that is specific to a procedure (or sub-procedure or sub-procedure parameter template).

Note | Data that can change between versions or instances of a procedure is not held in this table. See the proc_version and proc_instance tables instead.

## Structure

The `proc_index` table has the following structure:

    TABLE proc_index (
    	node_id		INTEGER			NOT NULL,
    	proc_id		INTEGER			NOT NULL,
    	proc_used_count	SMALLINT		NOT NULL,
    	proc_name	VARCHAR(8)		,
    	proc_desc	VARCHAR(24)		,
    	proc_owner	VARCHAR(49)		,
    	dir_name	VARCHAR(12)		,
    	proc_used	SMALLINT		NOT NULL,
    	work_days	SMALLINT		NOT NULL,
    	auto_purge	SMALLINT		NOT NULL,
    	networked	SMALLINT		NOT NULL,
    	cdesc_type	SMALLINT		NOT NULL,
    	ignore_blanks	SMALLINT		NOT NULL,
    	is_predict	SMALLINT		NOT NULL,
    	normalise_data	SMALLINT		NOT NULL,
    	delay_purge	SMALLINT		NOT NULL,
    	delay_value	VARCHAR(512)		)

Column | Description
`node_id` | ID of the node that this procedure is defined on, as defined in the nodes table.
`proc_id` | Unique ID of this procedure, generated from the sequences table.
`proc_used_count` | Not used.
`proc_name` | Name of this procedure. Note: Internal procedures are prefixed with a dollar sign (`$`) character.
`proc_desc` | Description of this procedure.
`proc_owner` | Name of the owner of this procedure, as defined in the user_names table.
`dir_name` | Not used.
`proc_used` | Flag that defines whether this record is currently free (`0`) or being used (`1`).
`work_days` | Flag that defines whether the procedure uses a 7-day week (`0`) or a configurable working week (`1`) in date calculations.
`auto_purge` | Flag that defines whether (`1`) or not (`0`) cases of this procedure are automatically purged when they are closed.
`networked` | Reserved for possible future use.
`cdesc_type` | Flag that defines whether a case description is Required (`0`), Optional (`1`) or Hidden (`2`) when a case of this procedure is started.
`ignore_blanks` | Flag that defines whether or not a blank field is treated as an error when used as an addressee for a step of this procedure:
| • | `0` means that the field is treated as an error and the step is delivered to the undelivered queue.
| • | `1` means that the field is not treated as an error.
`is_predict` | Flag that defines whether (`1`) or not (`0`) case prediction is enabled for this procedure.
`normalise_data` | Flag that defines whether (`1`) or not (`0`) case data normalization is enabled for this procedure.
`delay_purge` | Flag that defines whether or not to delay the auto-purge operation.
| • | `0` means that the auto-purge operation is not delayed.
| • | `1` means that the auto-purge operation is delayed.
`delay_value` | The value of the `delay_value` column is:
| • | If the value of the `delay_purge` column is `0`, then the value of the `delay_value` column is `NULL`.
| • | If the value of the `delay_purge` column is `1`, then the value of the `delay_value` column is specified in one of the following ways:
| — | The period of the delay in days.
| — | Delayed date and time expressions:
`date expression``^``time expression`

## Primary Key

The following primary key is defined for this table.

Key Name | Column(s)
`pk_proc_index` | `proc_id node_id`

## Foreign Keys

The following foreign key is defined for this table.

Key Name | Column(s) | Referenced in Table...
`fk_proc_index` 1 This key enforces the DELETE CASCADE referential action. | `node_id` | nodes

## Indexes

The following index is defined for this table.

Index Name | Column(s) Indexed
`idx_proc_index_fk` | `node_id`

## Table Activity

The `proc_index` table contains one row for each procedure defined on the system.

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

A row is... | When...
added | a new procedure is created.
updated | a procedure’s details are updated.
deleted | never.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO iProcess® Engine