Siebel Business Process Framework: Workflow Guide > Reference Materials for Siebel Workflow > Predefined Business Services >
About the Outbound Communications Manager Business Service
The Outbound Communications Manager business service can be used to send notifications through fax and email, such as notifications to contacts or employees. For information on methods and arguments, see Siebel Communications Server Administration Guide. Specifying a Substitution With the Outbound Communications Manager Business Service
You can specify a substitution variable when calling the Outbound Communications Manager business service from a workflow process. To create a test workflow process that uses a substitution variable when calling the Outbound Communications Manager
- In Siebel Tools, create a new workflow process object definition using values described in the following table:
|
|
Process Name |
Send SR Notification |
Workflow Mode |
Service Flow |
Business Object |
Service Request |
To view an example, see Creating a New Workflow Process Object Definition.
- Add steps and connectors until your workflow process resembles the workflow illustrated in the following diagram:
For more information, see About Workflow Process Steps and Connectors, and Diagramming a Workflow Process.
- Click the Send Notification business service step, then use the Properties window to define values described in the following table:
Property |
Value |
Business Service Name |
Outbound Communications Manager |
Business Service Method |
SendMessage |
- With the Send Notification step still chosen, click the MVPW, then add a new input argument using values described in the following table:
|
|
|
|
MsgBody |
Expression |
"The Service Request Number [SR Number] has been created with the abstract [SR Abstract]" |
Service Request |
For more information, see About Process Properties.
- Add another input argument to the Send Notification step using values described in the following table:
|
|
|
CommProfile |
Literal |
(Enter the appropriate profile. The profile must correspond with a profile that appears in the Administration - Communications > All Configurations > Profiles view in the Siebel client. Type in the profile name exactly as it appears in the client.) |
- Validate then simulate the workflow process.
For more information, see Process of Testing a Workflow Process.
- Implement this technique in your production workflow.
Sending an Email to the Owner of a Product Defect
You can use the Outbound Communications Manager to send an email to the owner of a product defect. This technique involves setting up a recipient group. To send an email to the owner of a Product Defect using a workflow process, you start by creating the custom recipient group for a product defect owner. To create the custom recipient group for a Product Defect Owner
- In the Siebel client, navigate to Administration - Data > List of Values, then create a new record using values described in the following table:
|
|
Type |
COMM_RECIP_SRC |
Display Value |
Product Defect |
Language - Independent Code |
Product Defect |
Parent LIC |
(Leave this field empty.) |
- Create a second record using values described in the following table:
|
|
Type |
COMM_RECIP_SRC |
Display Value |
Product Defect Owner |
Language - Independent Code |
Comm Employee |
Parent LIC |
Product Defect |
.
- In Siebel Tools, from the application level menu choose View > Options, click the Object Explorer tab, expand the Applet tree, make sure the Applet Toggle object type has a checkmark, then click OK.
- Navigate to the Applets OBLE, then query the Name column for Comm Source List Applet.
- From the application-level menu, choose Edit > Copy Record, then specify properties using values described in the following table:
|
|
Name |
Comm Source Product Defect List Applet |
Class |
CSSFrameListCommSrc |
- In the Applets OBLE, query the Name column for Comm Source List Applet, right-click the record, then choose Lock Object.
- In the Object Explorer, expand the Applet object type, choose the Applet Toggle object type, then add a new record in the Applet Toggles OBLE using values described in the following table:
|
|
Applet |
Comm Source Product Defect List Applet |
- In the Object Explorer, choose the Link object type, then add a new record in the Links OBLE using values described in the following table:
|
|
Name |
Comm Request/Product Defect |
Parent Business Component |
Comm Request |
Child Business Component |
Product Defect |
Inter Table |
S_COMM_REQ_SRC |
Inter Parent Column |
COMM_REQ_ID |
Inter Child Column |
SRC_ROW_ID |
Make sure you define properties in the order as they appear listed in the table.
- Navigate to the Business Objects OBLE, query the Name column for Comm Request, right-click the record then choose Lock Object.
- In the Object Explorer, expand the Business Object object type, then add a new record in the Business Object Components OBLE using values described in the following table:
|
|
BusComp |
Product Defect |
Link |
Comm Request/Product Defect |
The work you have performed thus far is required to create a custom recipient group for a product defect owner. For more information, see Siebel Communications Server Administration Guide. Next, you create the product defect/employee link. To create the Product Defect/Comm Employee link
- In the Object Explorer, choose the Link object type, then add a new record in the Links OBLE using values described in the following table:
|
|
Name |
Product Defect/Comm Employee |
Parent Business Component |
Product Defect |
Child Business Component |
Comm Employee |
Source Field |
Owned By Id |
Destination Field |
Id |
- Navigate to the Business Objects OBLE, query the Name column for Product Defect, right-click the record then choose Lock Object.
- In the Object Explorer, expand the Business Object object type, then add a new record in the Business Object Components OBLE using values described in the following table:
|
|
BusComp |
Comm Employee |
Link |
Product Defect/Comm Employee |
- Compile your changes.
Next, you create a template that defines the email message that is sent. To create a template that defines the email message
- In the Siebel client, navigate to Communications > My Templates, then add a new record using values described in the following table:
|
|
Name |
eMail Notification - Product Defect |
Channel Type |
Email |
- Click the Advanced view tab, then set the Recipient Group property to Product Defect Owner.
- Specify other information in the Advanced form, as required.
For a detailed explanation of the available fields, see Siebel Communications Server Administration Guide.
Next, you can create a test workflow process that calls the template. To create a test workflow process that calls the template
- In Siebel Tools, in the Workflow Processes OBLE, create a new workflow process object definition with the following values:
Property |
Value |
Process Name |
Email Notification of Product Defect |
Business Object |
Service Request |
Workflow Mode |
Service Flow |
To view an example, see Creating a New Workflow Process Object Definition.
- Open the Process Designer for the workflow process you created in Step 1, then create a workflow that resembles the workflow in the following diagram:
For more information, see About Workflow Process Steps and Connectors, and Diagramming a Workflow Process.
- Click the Call Template step then use the Properties window to define values described in the following table:
|
|
Business Service Name |
Outbound Communications Manager |
Business Service Method |
CreateRequest |
- With the Call Template step still chosen, in the MVPW define three new input arguments using values from the following table:
|
|
|
PackageNameList |
Literal |
eMail Notification - Product Defect |
RecipientGroup |
Literal |
Product Defect Owner |
RequestName |
Literal |
Comm Request created by AP Send Updated CR Email |
For more information, see About Process Properties.
- With the Call Template step still chosen, in the MVPW define one more input argument using values from the following table:
|
|
|
SourceIdList |
Process Property |
Object Id |
- Validate then simulate the workflow process.
For more information, see Process of Testing a Workflow Process.
- Implement this technique in your production workflow.
|