Using IS DELETED in the Conditions List

The example in this topic uses IS DELETED in the Conditions list. If a user deletes an activity from a service request that includes a Sub-Status of In Process, then Siebel CRM must notify the service request owner. The following table shows an example of the IS DELETED configuration in the Conditions list.

Policy	First Condition	Second Condition	Action
References the Service Request Workflow Policy object.	The first condition depends on each of the following situations being true: Field is Activity Component Comparison is IS DELETED Value is empty	The second condition depends on each of the following situations being true: Field is Service Request Sub-Status Comparison is equal (=) Value is In Process	Send an email to the service request owner.

If you use IS DELETED, then Siebel CRM cannot track the ROW_ID of the record that it deletes from the child Workflow Policy component. It cannot log this record in the S_ESCL_REQ table and the Workflow Monitor Agent cannot identify the deleted row. If you must use Siebel Workflow to capture the deleted row, then you must use a Workflow Process that a runtime event starts. The runtime event is the BusComp_PreWriteRecord event. For more information about the BusComp_PreDeleteRecord event, see Siebel Object Interfaces Reference. For more information, see Tables That Workflow Monitor Agent Uses.