The XPC_CREATE_INDEX stored procedure is used for creating a custom index on a given table based on users' needs.
Syntax
XPC_CREATE_INDEX (idx_xpc_name VARCHAR_TYPE(32))
The valid values for idx_xpc_name are:
• idx_xpc_status: Creates an index on case information table with columns is_dead, casenum, and proc_id.
• idx_xpc_ended: Creates an index on case information table with columns next_deadline, casenum, and proc_id.
• idx_xpc_started: Creates an index on case information table with columns started, casenum, and proc_id.
• idx_xpc_starter: Creates an index on case information table with columns starter, casenum, and proc_id.
• idx_xpc_tid: Creates an index on case information table with columns type_id, and casenum.
• idx_xpc_date: Creates an index on case information table with columns audit_date, and casenum.
• idx_xpc_desc: Creates an index on case information table with columns stepdesc, and casenum.
• idx_xpc_step: Creates an index on case information table with columns stepname, and casenum.
• idx_xpc_user: Creates an index on case information table with columns user_name, and casenum.
This stored procedure addresses any performance issues while searching millions of cases in the database. This logic facilitates the iProcess Engine to check 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 an index to improve the performance.
This stored procedure has been introduced in iProcess Engine 11.7 and above, and not documented as part of iProcess Engine 11.7 documentation. For more information, please refer to this
link in the iProcess Engine 11.8 documentation.