Bookshelf v7.5: Working with a User Interact Step

Siebel Business Process Designer Administration Guide for Financial Services > Designing Workflow Processes >

Working with a User Interact Step

The user interact step allows application designers to design and configure the flow of Siebel views within an application. Siebel Workflow guides end users through a specified flow of Siebel views based on the users' actions, or executes a specified set of actions. This flow can be modified as business rules change.

The user interact step has the following behaviors:

The user interact step brings up the required view. The user interact step runs in the user session. It sends a request to the Siebel Web Engine to build the view.

NOTE: Only one view can be built at a time. You cannot combine a user interact step with another action, such as bringing up a message box or building another view simultaneously.

The user interact step waits for a runtime event to resume processing. It waits in the memory of the user session. In cases where there is no runtime event defined, the workflow process will continue to the end.

If, after a user interact step, the user manually navigates out of the view, the workflow process remains in the memory of the user session. The process is deleted when the user session is terminated or when another workflow process is instantiated in the same user session.

If a workflow process containing a user interact step is run in the Process Simulator, incorrect behavior will result. To test workflows that contain user interact steps, you must test the workflow in the runtime environment. For more detailed information, see Testing User Interact Workflows.

NOTE: Workflows running in the Workflow Process Manager server component should not contain user interact steps. That is, if the workflow is running in background mode or in batch mode, it cannot include user interact steps. If the Workflow Process Manager encounters a user interact step, an error will result.

CAUTION: If using the workflow persistence feature with user interact steps, note that workflows with user interact steps should be persisted only for debugging purposes. A persisted workflow that contains a user interact step can resume in a different user session based on which user generated the event, causing unintended behavior. For more information on persistence and user interact steps, see User Interact Steps and Workflow Persistence.