Siebel Store-and-Forward Messaging Guide for Mobile Web Client > Siebel Store-and-Forward Messaging Sample Workflows > Transaction Delete Message Workflows >

About the Transaction Delete Message Workflows

When a record is deleted, either manually by a user action or automatically by a system process, the system invokes the Delete method. This method triggers a PreDeleteRecord runtime event and a DeleteRecord runtime event. When a FS Invoice record is deleted from an Activity in the Action business object, those runtime events trigger two of the SMQ Delete sample workflows (SMQ PreDelete FS Invoice Record and SMQ Delete FS Invoice Record).

The SMQ Delete sample workflows can delete a child business component record while leaving its parent business component records undeleted. The workflows generate a Transaction (TXN) type Delete message. A transaction message delivers an action; in this case, a Delete action. The workflows send this TXN Delete message to a queue. The message will eventually be sent to the client application to delete the record. Each message deletes only one record.

The format of the TXN Delete message identifies the to-be-deleted record. The last <BC> is the record to be deleted. In the following example message, the child BC record is the one to be deleted.

<smq>
<TXN mid=" " act="D">
<BO nam=" ">
<BC nam=" " rid=" "/>
...
<BC nam=" " rid=" "/> //grand parent BC
<BC nam=" " rid=" "/> //parent BC
<BC nam=" " rid=" "/> //child BC
</BO>
</TXN>
</smq>

All <BC>s above the last one are parent records. They identify the to-be-deleted record's position in the parent-child hierarchy. The message does not specify whether the delete is a cascading delete.

NOTE:  These workflows function in the Action Object when a FS Invoice record is deleted from an activity parent record. You can custom-configure them for other business components or business objects. The workflows are capable of deleting any record whose business component is within a business object that has a primary business component defined. The restriction comes from the workflows.