SW_JUMPTO

The SW_JUMPTO procedure jumps a case from its current step to another step in the procedure, ignoring the procedure logic.

Syntax

SW_JUMPTO (
proc_name
varchar(8),
proc_maj_ver
integer,
proc_min_ver
integer,
jump_step
varchar(8),
case_number
numeric(20),
jump_reason
varchar(24),
user_id
varchar(24)
failurecount 
in integer,)

where:

•

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

•

proc_maj_ver is either the major version number of the proc_name procedure, or -1. See the notes .

•

proc_min_ver is either the minor version number of the proc_name procedure, or -1. See the notes .

•

jump_step is the name of the step that the case is to jump to.

•

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.

•

failurecount is an optional parameter. If passed, is used internally to pass it on to BusinessWorks and to wait for some time before retrying.

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).

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

If a SW_JUMPTO 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 102 of the CUSTREQ procedure from its current position in the workflow to STEP5. The reason for the jump will be displayed in the audit trail as “Administrator-initiated Jump”.

EXEC owner.SW_JUMPTO 'CUSTREQ', -1, -1, 'STEP5', 102, 'Administrator-initiated Jump', 'swadmin'

Note	This example does not have any explicit transaction control, so will be committed immediately if using Transact-SQL.