Copyright © Cloud Software Group, Inc. All Rights Reserved |
The SW_EVENT_UPDATE_PACK procedure is the same as SW_EVENT, but when it triggers a specific event on a case of a procedure it refreshes the data of any work items that are outstanding for that case.SW_EVENT_UPDATE_PACK (
proc_name varchar(8),
proc_maj_ver integer,
proc_min_ver integer,
step_name varchar(8),
case_num numeric(20),
user_id varchar(24))
• proc_name is the name of the procedure that you want to trigger the event on.
• 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.
• step_name is the name of the event step that you want to trigger.
• case_num is the number of the case that you want to trigger the event on.
• user_id is the name of the iProcess user who is triggering the event.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).
For more information about events and how to use them, see TIBCO iProcess Modeler Integration Techniques.This example issues an event, as user swadmin, on step STEP1 of case 101 of the CUSTREQ procedure, and refreshes oustanding wortk items.
Copyright © Cloud Software Group, Inc. All Rights Reserved |