SW_JUMPTO

SW_JUMPTO_MULTI

The SW_JUMPTO_MULTI procedure is similar to SW_JUMPTO except that it can process, that is, jump to, more than one step. It allows the withdrawal of either a single step or all steps. In addition it allows setting of case data using the existing SW_ADD_PACK_DATA interface.

Syntax

SW_JUMPTO_MULTI (
tgt_proc_name in varchar2(8),
tgt_proc_maj_ver in number(5),
tgt_proc_min_ver in number(5),
src_step_name in varchar2(8),
tgt_step_name in varchar2,
case_number in integer,
jump_reason in varchar(2),
user_id in varchar2(24))

where:

•

tgt_proc_name is the name of the procedure that you want to jump a case of.

•

tgt_proc_maj_ver is either the major version number of the tgt_proc_name procedure, or -1. See the notes below.

•

tgt_proc_min_ver is either the minor version number of the tgt_proc_name procedure, or -1. See the notes below.

•

src_step_name is the name of the step to be withdrawn. Specifying * withdraws all outstanding steps.

•

tgt_step_name is the name of the step that the case is to jump to. Use a comma-separated list of step names to jump to more than one step.

•

case_number is the case number of the main procedure that is to jump.

•

jump_reason is a reason for this jump, used in the audit trail.

•

user_id is the name of the iProcess user who is performing the jump.

Notes

Instead of using the specific major or minor version number or both of the procedure, you can specify both the proc_maj_ver and proc_min_ver parameters as -1. If you do this, iProcess will use the version number of the procedure that the case was originally started with or, that it has subsequently been migrated to (if a subsequent version has been released while the case is still in progress).


	If you specify one version number parameter as -1, you must specify the other one as -1 as well.

If a SW_JUMPTO_MULTI procedure specifies an invalid jump_step, the transaction is rolled back. A warning message is generated and an Invalid Step message is written to the audit trail.

For more information about jumps and how to use them, please see the TIBCO iProcess Objects and TIBCO iProcess Server Objects programmer guides.

Example

This example jumps case 110 of the CARPOOL procedure to the ALLOCATE steps and REFUSED. The REQUEST step is withdrawn. The reason for the jump will be displayed in the audit trail as “Request Refused”.

EXEC SSOLITE.SW_JUMPTO_MULTI ('CARPOOL', -1, -1, 'REQUEST', ’ALLOCATE,REFUSED’, 110, 'Request Refused', 'swadmin')