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 data type in the pack_nmemo table.

11.6 You can migrate case memo data in the pack_memo table to the pack_nmemo table when upgrading to iProcess Engine or migrate them by using the swutil MIGRATEMEMOS command after the upgrades.

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		number(20)		NOT NULL,
	node_id		number(5)			NOT NULL,
	proc_id		number(5)			NOT NULL,
	casenum		number(20)		NOT NULL,
	memo_id		number(4)			NOT NULL,
	memo_index	number(10)			NOT NULL,
	memo_size	number(10)			NOT NULL,
	memo_data	blob		NOT NULL,
	array_idx	number(6)			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. Note: • If you have upgraded your system from one of the following versions , existing memos are divided into 2000 byte chunks : — (UNIX Oracle) any Version i9.n-o iProcess Engine, or from a pre-Version 9.0-o(0.15) Process Engine. — (Windows Oracle) any Version 9.0-o Process Engine. • However, if a memo is modified, the existing rows are deleted and then re-added using 30,000 byte chunks.
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)	Index Tablespace
pk_pack_memo	reqid node_id casenum memo_id memo_index array_idx	HUGEINDEXSPACE

Foreign Keys

None.

Indexes

None.

Storage

The following STORAGE values are defined for this table.

Value	Definition
Initial	HUGETABLESIZE
Percentage Increase	HUGETABLEPCTINCREASE
Tablespace	HUGETABLESPACE

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.