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

SAF Activity Workflow

This topic describes the SAF Activity workflow for Store-and-Forward Messaging. The workflow is shown in Figure 8.

Figure 8. SAF Activity Workflow

As shown in Figure 8, the SAF Activity workflow changes the owner of an Activity record. This Workflow is based on the Action business object and is invoked as a subprocess from the Dispatch Board - Generic workflow. This workflow consists of two steps that invoke the methods of the RTS Subscription Service so that an Activity can be subscribed to an owner and sent out using the Store-and-Forward communication channel.

This workflow has two process properties:

• ActivityId. This is the Row_Id of the Activity record that is being sent.
• EmployeeId. This is the Row_Id of the Employee who is being assigned to this Activity.

This workflow contains the following steps:

1. Unsubscribe Current Owner: This step calls the UnsubscribeAll business service method and is responsible for making sure that the current owner of the activity is unsubscribed as the owner. This step takes the following two input arguments:
   1. RowId. The ActivityId process property is passed to this input argument.
   2. TableName. This input argument has a hardcoded value of S_EVT_ACT (the table where Activities are stored).
2. Subscribe new owner: This step calls the SendSimple business service method and is responsible for subscribing the Activity to the new owner. This step takes the following three input arguments:
   1. RecepientId. The EmployeeId process property is passed to this input argument.
   2. RowId. The ActivityId process property is passed to this input argument.
   3. TableName. This input argument has a hardcoded value of S_EVT_ACT.