Open topic with navigation

TIBCO iProcess® Engine 11.10.0

# staffo

The `staffo` table holds information about outstanding steps, that is, steps that have been delivered to work queues but not yet released (or otherwise removed).

## Structure

The `staffo` table is structured as follows:

    TABLE staffo(
    	o_flags			number(5)		NULL,
    	o_queuename		varchar2(24)	NULL,
    	o_locker		varchar2(24)	NULL,
    	o_username		varchar2(49)	NULL,
    	o_startname		varchar2(49)	NULL,
    	o_dirname		varchar2(12)	NOT NULL,
    	o_dirdesc		varchar2(24)	NULL,
    	o_procname		varchar2(8)	NOT NULL,
    	o_procdesc		varchar2(24)	NULL,
    	o_casedesc		varchar2(24)	NULL,
    	o_casenum		number(20)	NULL,
    	o_placeno		number(5)		NULL,
    	o_dirflags		number(5)		NULL,
    	o_procflags		number(5)		NULL,
    	o_host			varchar2(24)	NOT NULL,
    	o_pnum			number(5)		NOT NULL,
    	o_pnumcount		number(5)		NOT NULL,
    	o_caseptr		number(15)	NULL,
    	o_reqidhost		number(24)	NOT NULL,
    	o_reqid			number(20)	NOT NULL,
    	o_deadline		date	NULL,
    	o_reqstamp		date	NULL,
    	o_qparam1		varchar2(24)	NULL,
    	o_qparam2		varchar2(24)	NULL,
    	o_qparam3		varchar2(12)	NULL,
    	o_qparam4		varchar2(12)	NULL,
    	o_itempriority		varchar2(24)	NULL,
    	o_priority_changed	date	NULL,
    	o_majorvers		number(5)		NOT NULL,
    	o_minorvers		number(5)		NOT NULL)

Column | Description
`o_flags` | Flags associated with this work item. For internal use only.
`o_queuename` | Queue name of the user or group queue that contains this work item, as defined in the user_names table.
`o_locker` | Name of the user who has locked the queue (if it is locked), as defined in the user_names table. Note: This column is not written to or updated unless the `WIS_WRITELOCKS` parameter in the `SWDIR``\etc\staffcfg` file is set.
`o_username` | Queue name of the user or group queue that contains this work item, as defined in the user_names table.
`o_startname` | Username of the user who started the case that this work item belongs to, as defined in the user_names table.
`o_dirname` | Step name of the step that generated this work item.
`o_dirdesc` | Step description of the step that generated this work item.
`o_procname` | Procedure name of the procedure that generated this work item, as defined in the proc_index table.
`o_procdesc` | Procedure description of the procedure that generated this work item, as defined in the proc_index table.
`o_casedesc` | Case description of the case that this work item belongs to, as defined in the case_information table.
`o_casenum` | Case number of the case that this work item belongs to, as defined in the case_information table.
`o_placeno` | Step mark number. For internal use only.
`o_dirflags` | Step flags. For internal use only.
`o_procflags` | Procedure flags. For internal use only.
`o_host` | ID of the node that this work item is associated with, as defined in the nodes table.
`o_pnum` | Procedure number of the procedure that generated this work item, as defined in the proc_index table.
`o_pnumcount` | Version count of procedure. For internal use only.
`o_caseptr` | Case control record number. For internal use only.
`o_-reqidhost` | Nodename of the node where the `o_reqid` is generated, as defined in the nodes table.
`o_reqid` | Unique ID for this work item, generated from the sequences table.
`o_deadline` | Date and time that the deadline (if defined) expires on this work item. If no deadline is set this value appears as `12/31/3000 11:15:00 PM`.
`o_reqstamp` | Timestamp when this work item was delivered to the queue.
`o_qparam1` | Value of work queue parameter 1 for this work item.
`o_qparam2` | Value of work queue parameter 2 for this work item.
`o_qparam3` | Value of work queue parameter 3 for this work item.
`o_qparam4` | Value of work queue parameter 4 for this work item.
`o_itempriority` | Priority definition for this work item, in the format: `base`:`increment`:`number`:`period`:`type` where:
| • | `base` is the base priority value for this work item.
| • | `increment` is the amount that will be added to the item’s priority value whenever the `period` expires.
| • | `number` is the number of increments that will be added to the item’s priority value.
| • | `period` is the time period, in the units specified in `type`, which must expire before the item’s priority value is incremented.
| • | `type` is the unit of measure of the `period`, either “`M`” or “`m`” for minutes, “`H`” or “`h`” for hours or “`D`” or “`d`” for days.
`o_priority_changed` | Timestamp when the priority value for this work item was last changed.
`o_majorvers` | Major version number of the procedure that generated this work item, as defined in the proc_version table.
`o_minorvers` | Minor version number of the procedure that generated this work item, as defined in the proc_version table.

## Primary Key

The following primary key is defined for this table.

Key Name | Column(s) | Index Tablespace
`pk_staffo` | `o_reqid o_reqidhost` | HUGEINDEXSPACE

## Foreign Keys

None.

## Indexes

The following index is defined for this table.

Index Name | Column(s) Indexed | Tablespace
`idx_staffo` | `o_queuename` | HUGEINDEXSPACE

## Storage

The following STORAGE values are defined for this table.

Value | Definition
Initial | HUGETABLESIZE
Percentage Increase | HUGETABLEPCTINCREASE
Tablespace | HUGETABLESPACE

## Table Activity

The `staffo` table contains one row for every outstanding step on the system.

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

A row is... | When...
added | a work item is sent out to a queue.
updated | any of the following occur:
| • | a work item is kept and any changes have been made.
| • | a work item’s priority value changes.
| • | a work item is opened and the `WIS_WRITELOCKS` parameter in the `SWDIR``\etc\staffcfg` file is set.
deleted | either:
| • | a work item is released or withdrawn.
| • | a case is closed or purged.

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