The DisplayApplet run-time event starts a workflow process the first time it runs but not for subsequent runs of the workflow process.

If the DisplayApplet run-time event is a UI event, and if the default Web UI framework uses a cache, then Siebel only starts the event the first time it accesses a noncached view. It starts the workflow process only if the event starts and works correctly.

To make the field work in this situation, you can set the EnableViewCache parameter in the .cfg file to FALSE.

After Siebel CRM starts a workflow process from a run-time event, it does not get the Row Id of the record on which the event occurs.

Siebel CRM passes the run-time event to the Row Id of the primary business component and not to the Row Id of the business component on which the run-time event occurs. For more information, see Defining the Primary Business Component.

To get the Row Id of the active business component, you can use a search specification. For example: the Active_row-id process property is equal to [Id], defined as Type equals Expression and the business component equals the business component name.

Siebel CRM displays the following error message:

Cannot resume Process x-xxxxx for Object-id x-xxxxx. Please verify that the process exists and has a waiting status.

Deleting existing instances of the workflow process does not help. This error typically occurs in the following situation:

1. A workflow process instance starts and pauses, waiting for a run-time event.

2. The run-time event starts. Siebel CRM resumes the instance and runs it to completion.

3. The run-time event starts a second time. The Workflow Engine attempts to resume the instance but fails because the instance is no longer in a Waiting state.

These steps must occur in the order described and in the same user session in order for Siebel CRM to report the error message. As a result, the error message disappears when the Siebel CRM application restarts.

Ignore the error message and proceed.

The Purge feature only works on instances that Siebel CRM has stopped and finished. To delete a persistent or incomplete instance, you first must manually stop the instance.

Unable to access a different business object from a workflow process.

Siebel Workflow restricts the use of one business object to a workflow process.

Use a sub process step to access a different business object.

Siebel CRM displays the following error message:

Unable to initiate the process definition process_name.

Not applicable

Make sure each of the following items is true:

• The workflow process exists.
• The status for the workflow process is set to Active.
• The workflow process is not expired.

Siebel CRM displays one of the following error messages:

• OMS-00107: (: 0) error code = 4300107, system error = 27869, msg1 = Could not find 'Class' named 'Test Order Part A'
• OMS-00107: (: 0) error code = 4300107, system error = 28078, msg1 = Unable to create the Business Service 'Test Order Part A'

Not applicable

Make sure Siebel CRM copies at least one SRF to the following directory,

Siebel_Root\objects\lang

where:

• Siebel_Root is the directory where you installed the Siebel Server.

Siebel CRM displays the following error message:

The selected record has been modified by another user since it was retrieved.

A workflow process attempted to update a record that another user or task updated since Siebel CRM initially retrieved the workflow process.

Define an error exception connector to handle the update conflict. For more information, see Defining an Error Exception Connector to Handle an Update Conflict.

The DisplayApplet run-time event starts a workflow process the first time it runs but not for subsequent runs of the workflow process.

If the DisplayApplet run-time event is a UI event, and if the default Web UI framework uses a cache, then Siebel only starts the event the first time it accesses a noncached view. It starts the workflow process only if the event starts and works correctly.

To make the field work in this situation, you can set the EnableViewCache parameter in the .cfg file to FALSE.

After Siebel CRM starts a workflow process from a run-time event, it does not get the Row Id of the record on which the event occurs.

Siebel CRM passes the run-time event to the Row Id of the primary business component and not to the Row Id of the business component on which the run-time event occurs. For more information, see Defining the Primary Business Component.

To get the Row Id of the active business component, you can use a search specification. For example: the Active_row-id process property is equal to [Id], defined as Type equals Expression and the business component equals the business component name.