XPC_CREATE_INDEX
XPC_CREATE_INDEX is used for creating a custom index on a given table-based on the user's needs.
Syntax
XPC_CREATE_INDEX (
idx_xpc_name VARCHAR(32))
The valid values for idx_xpc_name are:
| • | idx_xpc_status: Creates an index on the case information table with columns is_dead, casenum, and proc_id. |
| • | idx_xpc_ended: Creates an index on the case information table with columns next_deadline, casenum, and proc_id. |
| • | idx_xpc_started: Creates an index on the case information table with columns started, casenum, and proc_id. |
| • | idx_xpc_starter: Creates an index on the case information table with columns starter, casenum, and proc_id. |
| • | idx_xpc_tid: Creates an index on the case information table with columns type_id, and casenum. |
| • | idx_xpc_date: Creates an index on the case information table with columns audit_date, and casenum. |
| • | idx_xpc_desc: Creates an index on the case information table with columns stepdesc, and casenum. |
| • | idx_xpc_step: Creates an index on the case information table with columns stepname, and casenum. |
| • | idx_xpc_user: Creates an index on the case information table with columns user_name, and casenum. |
This stored procedure addresses any performance issues while searching millions of cases in the database. With the help of this logic, iProcess Engine checks the filter and the tables involved. In the search, if there is no proper index created, the system throws a suggestion in sw_warn and system event to create index to improve the performance. iProcess Engine checks for the index on the following fields, with the corresponding database table and database columns.
|
SYSTEM FIELD |
INDEX INPUT |
DB TABLE |
DB COLUMN |
|
SW_STATUS |
idx_xpc_status |
case_information |
is_dead |
|
SW_TERMINATED |
idx_xpc_ended |
case_information |
next_deadline |
|
SW_TERMINATEDDATE |
idx_xpc_ended |
case_information |
next_deadline |
|
SW_STARTED |
idx_xpc_started |
case_information |
started |
|
SW_STARTEDDATE |
idx_xpc_started |
case_information |
started |
|
SW_STARTER |
idx_xpc_starter |
case_information |
starter |
|
SW_AUD_TYPE |
idx_xpc_tid |
audit_trail |
type_id |
|
SW_AUD_DATE |
idx_xpc_date |
audit_trail |
audit_date |
|
SW_AUD_USER |
idx_xpc_user |
audit_trail |
user_name |
|
SW_AUD_STEP |
idx_xpc_step |
audit_trail |
stepname |
|
SW_AUD_DESC |
idx_xpc_desc |
audit_trail |
stepdesc |
This is primarily used when working with "Filtering Work Items and Cases" ( Ref: TIBCO iProcess® Server Objects (Java) or (.NET) Programmer’s Guide )