Siebel Business Process Framework: Workflow Guide > Options for Configuring a Workflow Process > Configuring a Workflow Process for a Multilingual Environment >

Using Wait Steps with Global Time Calculations

Siebel CRM can use the following types of wait steps:

• Absolute Wait. A wait period that the duration controls. For example, an absolute wait that you set for 30 minutes waits 30 minutes from the time that the wait step starts the wait.
• Service Calendar Wait. Not absolute. For example, assume a service calendar wait begins at 6:00 P.M. but the service hours for the organization are 9:00 A.M. to 6:00 P.M.In this situation, the wait does not start until 9:00 A.M. the next morning. It runs from 9:00 A.M. to 9:30 A.M. instead of from 6:00 P.M.to 6:30 P.M.

Using a Time Zone Setting with a Wait Step

If a workflow process runs as a server task, then you must shut down, and then restart the Workflow Process Manager after you make any changes to the Time Zone user preference for the SADMIN user. Siebel CRM uses these changes only after it restarts the Workflow Process Manager, which is important if you your deployment uses UTC because it might be necessary for you to set the Time Zone user preference.

Time zone settings do not affect an absolute wait, including server or user time zone preferences. You can use UTC with the server that contains the database that your Siebel CRM deployment uses. For more information, see Siebel Global Deployment Guide.

A service calendar wait step requires a time zone for delay computations. In this situation, Siebel CRM uses the time zone for the current user.