Copyright © Cloud Software Group, Inc. All Rights Reserved |
The SW_JUMPTO procedure jumps a case from its current step to another step in the procedure, ignoring the procedure logic.SW_JUMPTO (
proc_name in varchar2(8),
proc_maj_ver in number(5),
proc_min_ver in number(5),
jump_step in varchar2(8),
case_number in integer,
jump_reason in varchar(2),
user_id in varchar2(24))
• 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 below.
• proc_min_ver is either the minor version number of the proc_name procedure, or -1. See the notes below.
• 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.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 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.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”.
Copyright © Cloud Software Group, Inc. All Rights Reserved |