Open topic with navigation

TIBCO iProcess® Engine 11.9.1

# pack_memo

The `pack_memo` table stores memo data associated with memo fields in the pack_data table before upgrading to iProcess Engine 11.6.

Since iProcess Engine version 11.6, all the new memo data associated with the memo fields is stored in the ``BLOB(2G)`` data type in the pack_nmemo table.

11.6

When a work item is sent out to a queue, memo data is copied from the memo table to the pack_memo table. The client uses the memo data in the pack_memo table to fill out the form correctly. When the form is kept any changed memo data is updated in the pack_memo table. When a work item is released memo data is moved from the pack_memo table to the memo table.

## Structure

The `pack_memo` table is structured as follows:

    TABLE pack_memo (
    	reqid		NUMERIC(20)		NOT NULL,
    	node_id		INTEGER			NOT NULL,
    	proc_id		INTEGER			NOT NULL,
    	casenum		NUMERIC(20)		NOT NULL,
    	memo_id		INTEGER			NOT NULL,
    	memo_index	INTEGER			NOT NULL,
    	memo_size	INTEGER			NOT NULL,
    	memo_data	BLOB(30K)		NOT NULL NOT LOGGED,
    	array_idx	INTEGER			NOT NULL)

Column | Description
`reqid` | ID of the work item that this memo belongs to, as defined in the staffo table.
`node_id` | ID of the node that this memo is associated with, as defined in the nodes table.
`proc_id` | Number of the procedure that this memo belongs to, as defined in the proc_index table.
`casenum` | Case number that this memo belongs to, as defined in the case_information table.
`memo_id` | Unique (for this case) ID of this memo.
`memo_index` | Index number in the set of rows that make up this memo. If a memo is longer than 30,000 bytes multiple rows (in 30,000 byte chunks) are used to store the memo data. Each segment of the memo data is uniquely identified by its `memo_index` value.
`memo_size` | Size (in bytes) of the memo data for this row.
`memo_data` | Memo data.
`array_idx` | Either:
| • | The array element index number of the memo.
| • | `-1`, if the memo is not an array memo field.

## Primary Key

The following primary key is defined for this table.

Key Name | Column(s)
`pk_pack_memo` | `reqid node_id casenum memo_id memo_index array_idx`

## Foreign Keys

None.

## Indexes

None.

## Table Activity

The `pack_memo` table contains one or more rows for every assigned memo field that contains data (i.e. that has a value other than `SW_NA`) in every outstanding step on the system.

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

A row is... | When...
added | Either:
| • | a step containing memo data is sent out.
| • | a memo field is assigned a value on a keep or release.
updated | An assigned memo field has its data changed on a keep or release.
deleted | any of the following occur:
| • | a release instruction for a work item containing memo data is processed by the background process.
| • | a work item containing memo data is withdrawn.
| • | a case containing memo data is 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