Open topic with navigation

TIBCO iProcess® Engine 11.10.0

# predict

The `predict` table stores the prediction data for all expected work items currently defined on the system.

## Structure

The `predict` table has the following structure:

    TABLE predict (
    	node_id			INTEGER		NOT NULL,
    	proc_num		NUMERIC(5)	NOT NULL,
    	case_num		NUMERIC(20)	NOT NULL,
    	parent_proc_num		NUMERIC(5)	NOT NULL,
    	parent_case_num		NUMERIC(20)	NOT NULL,
    	main_proc_num		NUMERIC(5)	NOT NULL,
    	main_case_num		NUMERIC(20)	NOT NULL,
    	step_name		VARCHAR(8)	NOT NULL,
    	step_desc		VARCHAR(24)		NULL,
    	step_desc2		VARCHAR(24)		NULL,
    	step_addr		VARCHAR(49)	NOT NULL,
    	step_durn_secs		NUMERIC(10)		NULL,
    	step_durn_usecs		NUMERIC(10)		NULL,
    	step_start		DATETIME	NOT NULL,
    	step_start_usecs	NUMERIC(10)	NOT NULL,
    	step_end		DATETIME	NOT NULL,
    	step_end_usecs		NUMERIC(10)	NOT NULL,
    	field_name		VARCHAR(31)		NULL,
    	field_value		VARCHAR(255)		NULL)

Column | Description
`node_id` | ID of the node that this predicted work item is hosted on, as defined in the nodes table.
`proc_num` | ID of the procedure associated with this predicted work item, as defined in the proc_index table.
`case_num` | Either:
| • | Case number of the case associated with this predicted work item, as defined in the case_information table.
| • | `0`, if this is a predicted work item in a future sub-case, rather than in a currently outstanding sub-case.
`parent_proc_num` | ID of the parent procedure associated with this predicted work item, as defined in the proc_index table, if `proc_num` is a sub-procedure.
`parent_case_num` | Either:
| • | ID of the parent case associated with this predicted work item, as defined in the case_information table, if `case_num` is a sub-case.
| • | `0`, if this is a predicted work item in a future sub-case, rather than a currently outstanding sub-case, that was itself started from a predicted future sub-case.
`main_proc_num` | ID of the procedure associated with the main case that generated this predicted work item, as defined in the proc_index table.
`main_case_num` | ID of the main case that generated this predicted work item, as defined in the case_information table.
`step_name` | Stepname of the step associated with this predicted work item.
`step_desc` | Step description of the step associated with this predicted work item.
`step_desc2` | Additional description of the step associated with this predicted work item.
`step_addr` | Queue name that this predicted work item will be delivered to.
`step_durn_secs` | Expected duration (in seconds) between this predicted work item being delivered to and released from the `step_addr` queue. Note: The `step_durn_usecs` column can be combined with this column to provide resolution to a microsecond.
`step_durn_usecs` | Number of microseconds to be added to the value specified in the `step_durn_secs` column.
`step_start` | Date and time that this predicted work item is expected to arrive in the `step_addr` queue, to the resolution of a second. Note: The `step_start_usecs` column can be combined with this column to provide resolution to a microsecond.
`step_start_usecs` | Number of microseconds since the start of the seconds value specified in the `step_start` column.
`step_end` | Date and time that this predicted work item is expected to be released from the `step_addr` queue, to the resolution of a second. Note: The `step_end_usecs` column can be combined with this column to provide resolution to a microsecond.
`step_end_usecs` | Number of microseconds since the start of the seconds value specified in the `step_end` column.
`field_name` | Name of the field that has a CDQP assigned to it for this predicted work item.
`field_value` | Value of the CDQP assigned to the `field_name` field for this predicted work item.

## Primary Key

None.

## Triggers

None.

## Indexes

None.

## Table Activity

The `predict` table contains one or more rows for each predicted work item generated by each step of each case of each procedure that currently has prediction data defined for it.

If a predicted work item contains one or more fields that have CDQPs assigned to them, duplicate rows are added for each CDQP. In the first row, the `field_name` and `field_value` columns are blank. Each subsequent row contains the `field_name` and `field_value` entries for one assigned CDQP. For example, if a predicted work item contains 5 fields that have CDQPs assigned to them, it will have 6 rows in this table.

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

A row is... | When...
added | background prediction is enabled on the iProcess Engine, and anything occurs that causes prediction data for a case to be calculated or recalculated. For example, when a case is started, a work item is kept or released, a deadline expires or an event occurs. Note: One row is added for each step in the procedure that can occur on the currently predicted path(s).
updated | never.
deleted | background prediction is enabled on the iProcess Engine, when prediction data for a case is to be recalculated. For example, when a work item is kept or released, a deadline expires or an event occurs. Note: All rows for a given main case number are deleted for each step in the procedure that can no longer occur on the currently predicted path(s).

Note | Case prediction can be enabled and disabled using the `ENABLE_CASE_PREDICTION` process attribute. See TIBCO iProcess Engine Administrator's Guide for more information.

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