Issue an Event
Use this command to issue an event from the command line. There is no equivalent menu option. Only users with administration access to a procedure can issue an EVENT on an iProcess case.
|
Note |
If you want to issue a large number of events you should consider using the |
swutil EVENT [-hostnode]procname[R]casenumeventname[-Ppriority] [datafile[-[r|R][p]]
where:
| • | hostnode is optional and, if included, should be the nodename of the node where the procedure is hosted. If the parameter is omitted the current node is assumed. |
| • | procname is the short name of the procedure (including sub-procedures), for example: QUOTA. |
| • | casenum is a single case number, for example: 23. You can only issue an event to a single case. |
An R preceding the case number can be used to restart a closed case. For example, R23 restarts case number 23.
|
Note |
After a case is closed, all the deadlines of the case are removed. If the case is reopened, you can reset the deadlines by running the |
| • | eventname is the short name of the step you are issuing the event for, for example: TREV. (This may be an event step, or an ordinary step.) |
|
Note |
If you issue an event for an ordinary step only the actions which follow the step are triggered; the ordinary step itself is not re-run. |
| • | -P priority specifies the internal message queue priorities. For more information about message priorities, see "Message Prioritizing" in the appropriate TIBCO iProcess Engine (Database) Administrator’s Guide. |
| • | datafile is optional and, if included, should be the full pathname of a file in abox format containing the new field values for the case. See "Using iProcess Abox Files" in TIBCO iProcess Modeler Integration Techniques for more information about abox format.) These values will be used to update the central case data (in the case_data database table). |
The following options can be used when a datafile is specified: