IBM FileNet P8, Version 5.2.1            

System function support in the simulation

A workflow definition can have any number of system steps that start system functions that are carried out by the workflow system.

In Simulation Designer on the Arrivals tab, you can specify a duration for these steps the same as for any user or queue step. For most of these system functions, the duration you specify is simulated. For example, if you specify a duration of 2 minutes, the simulation shows 2 minutes for that step. The Delay and WaitForCondition system functions have delays or time-outs specified as part of the function, so their behavior is different, as specified in this table.

The following table lists the system functions and specifies which functions you can simulate.

Table 1. System functions and descriptions
System functions Simulated Comment
Assign Yes Assigns values to data fields either pre- or post-execution of the step as specified in the workflow definition.

If the scenario results are published to Case Analyzer, the values are published to the cube specified in Process Task Manager.

Call Yes Simulates running the steps in the called submap.
BeginCheckPoint No  
EndCheckPoint No  
RollBackCheckPoint No  
Create Yes Injects a new arrival with the current simulated time as the arrival time and the values for Assign statements in the Create function.
DbExecute No  
Delay Yes Simulates waiting for the amount of time specified for the delay in the workflow definition. The delay time is generated in the analytical information.

If the scenario results are published to Case Analyzer, the analytical information is published to the QueueLoad, the Work Item Processing Time, and the Work Item WIP cubes.

Return Yes The Simulation Engine has the following behavior regarding the Retry option:

The map containing the Return instruction is a map called by using the Call system function or VW_Call API.

Retry = true results in Repeat (return to the calling step)

Retry =false results in Next (return to the step following the calling step)

TerminateBranch Yes Generally, the simulator does not include calls to the Terminate system map when performing the TerminateBranch system instruction. However, the user can supply a user-defined Terminate submap that overrides the default TerminateBranch system map. If a user-defined submap is present in the workflow definition, the simulator calls this submap before terminating the work item.
TerminateProcess No  
Invoke No  
Receive No  
Reply No  
Log No  
BeginTimer No  
EndAllTimers No  
EndTimer No  
SuspendTimer No  
ResumeTimer No  
WaitForCondition Yes Simulates waiting for a random amount of time between 0 and the timeout duration specified for the step in the workflow definition. If the specified timeout is 0, the simulation waits forever. The time is generated in the analytical information.

If the scenario results are published to Case Analyzer, the analytical information is published to the QueueLoad, the Work Item Processing Time, and the Work Item WIP cubes.

The simulation does not simulate the waited-for workflow.



Last updated: October 2015
pe_system_functions.htm

© Copyright IBM Corporation 2015.