Siebel Communications Server Administration Guide > Using Wireless Messaging > Using One-Way Wireless Messaging Workflows >

Configuring One-Way Wireless Messaging Workflows for Siebel Wireless

This section describes various ways you can configure the one-way workflows listed in Table 72. These configurations are applicable to using these workflows with the Siebel Wireless application.

If a message is sent using WAP Push with one of the workflows listed in Table 72, the workflow adds to the text of the message a URL link to the relevant view from the relevant Siebel Wireless application.

For example, when an activity with the description ABC is created and assigned to user TSMYTHE, the Wireless Activity Policy workflow pushes a wireless message to TSMYTHE with text that reads "You have a new Siebel Activity. View it Now?" If the message recipient (TSMYTHE, in our example) has a browser that supports WAP Push and links to view this message, the recipient's browser is launched and displays the view Siebel Wireless Activity Detail View for ABC.

Depending on how your company uses wireless messaging, you may need to make one or more of the following modifications to the preconfigured workflows.

Specifying a Base URL for Siebel Wireless

If wireless messages are sent to Siebel Wireless application users through WAP Push, as described above, the ChangeMe text of the Base URL parameter of the workflow action should be set to the external static IP address of the Siebel Server that supports Siebel Wireless.

NOTE:  For the WAP V1.2 driver, if no URL is provided from the workflow, then a URL specified with the Default URL parameter is used instead. For more information about this parameter, see Table 75.

Enabling Recipient Access to Views in Siebel Wireless

If you want to send wireless messages to recipients that do not have access to a Siebel Wireless application that includes the view name defined in the SWEView workflow action argument for a particular policy, the HasViewResponsibility step of the appropriate workflow processes should be eliminated.

Alternatively, if the view defined in the SWEView argument is added to another responsibility held by the message recipient, the recipient can link to the URL to access that view, even though the recipient does not have the responsibility shown in Table 72.


 Siebel Communications Server Administration Guide 
 Published: 23 June 2003