Open topic with navigation

TIBCO iProcess® Engine 11.10.0

# outstanding_addr

The `outstanding_addr` table holds information about each outstanding step on the system.

## Structure

The `outstanding_addr` table has the following structure:

    TABLE outstanding_addr (
    rowid 		NUMERIC(15)			NOT NULL
    GENERATED ALWAYS AS IDENTITY (START WITH 1, INCREMENT BY 1, CACHE 50),
    	node_id			INTEGER 	NOT NULL,
    	proc_id			INTEGER		NOT NULL,
    	casenum			NUMERIC(20)	NOT NULL,
    	sentdate		TIMESTAMP	NOT NULL,
    	deadline		SMALLINT	NOT NULL,
    	deadline_exprired	SMALLINT	NOT NULL,
    	sub_procedure		SMALLINT	NOT NULL,
    	deaddate		TIMESTAMP	NOT NULL,
    	stepname		VARCHAR(8)	NOT NULL,
    	user_name		VARCHAR(64)	NOT NULL,
    	reqid			NUMERIC(20)	NOT NULL,
    	item_suspended		SMALLINT,
    	item_withdrawn		SMALLINT,
    	array_idx		INTEGER		NOT NULL)

Column | Description
`rowid` | Unique identifier for this row
`node_id` | ID of the node that this outstanding step is hosted on, as defined in the nodes table.
`proc_id` | ID of the procedure that this outstanding step belongs to, as defined in the proc_index table.
`casenum` | Number of the case that this outstanding step belongs to, as defined in the case_information table.
`sentdate` | Date and time that this outstanding step was sent to the `user_name` queue.
`deadline` | Flag that defines whether (`1`) or not (`0`) this outstanding step has a deadline defined.
`deadline_expired` | Flag that defines whether (`1`) or not (`0`) the deadline (if defined) has expired and been processed.
`sub_procedure` | Flag that defines whether (`1`) or not (`0`) this outstanding step is a sub-procedure call.
`deaddate` | Date and time that the deadline (if defined) expires on this outstanding step. If no deadline is set, this value appears as `12/31/3000 11:15:00 PM`.
`stepname` | Stepname of this outstanding step.
`user_name` | Name of the queue that this outstanding step has been sent to, as defined in the user_names table.
`reqid` | Unique ID for this work item, generated from the sequences table.
`item_suspended` | Flag that defines whether (`1`) or not (`0`) this outstanding step is currently suspended. Note: `item_suspended` is only set if the case is suspended and the ignore suspend attribute is not set on the step.
`item_withdrawn` | Flag that defines whether (`1`) or not (`0`) this outstanding step is withdrawn.
`array_idx` | Either:
| • | The array element index number of the sub-procedure that generated this outstanding step, if the sub-procedure was called from either a graft step or a dynamic sub-procedure call step.
| • | `-1`, otherwise.

## Primary Key

None.

## Foreign Keys

The following foreign key is defined for this table.

Key Name | Column(s) | Referenced in Table...
`fk_outstand_addr` 1 This key enforces the DELETE CASCADE referential action. | `casenum proc_id node_id` | case_information

## Indexes

The following indexes are defined for this table.

Index Name | Column(s) Indexed
`idx_deadline_date` | `deaddate`
`idx_outstand_addr` 2 UNIQUE index. | `rowid`
`idx_outstd_addr_fk` | `casenum proc_id node_id`

## Table Activity

The `outstanding_addr` table contains one row for each outstanding step on the system.

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

A row is... | When...
added | a new step is sent out. Note:
| • | if a step has multiple addressees one row is added per addressee.
| • | for a dynamic sub-procedure, one row is added per called sub-procedure.
| • | for a graft step, one row is added per grafted sub-procedure or external step.
updated | any of the following occur:
| • | a deadline on an outstanding step expires.
| • | a case is suspended or re-opened.
| • | an outstanding step is withdrawn.
deleted | the background processes a release, withdraw, close or purge operation that affects an outstanding step.

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