Click OK. Drag a Signal activity into the designer. Double-click the Signal activity.

15-12 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite a. Specify the bpelx:detailLabel attribute for correlating with the receive signal activity, as shown in Example 15–12 . Example 15–12 bpelx:detailLabel Attribute invoke name=MyInvoke partnerLink=DetailProcess portType=dp:DetailProcess operation=initiate inputVariable=detail_input bpelx:detailLabel=detailProcessComplete0 bpelx:invokeAsdetail name=true b. Specify the same label value of detailProcessComplete0 in the receive signal activity of the master process, as shown in Example 15–13 . Example 15–13 detailProcessComplete0 Label Value bpelx:receiveSignal name=waitForNotifyFromDetailProcess0-1 label=detailProcessComplete0 from=details c. Repeat these steps as necessary for additional detail processes, ensuring that you specify a different label value.

10. From the File main menu, select Save All.

Master and detail coordination design is now complete. 16 Using the Notification Service 16-1 16 Using the Notification Service This chapter describes how to send notifications from a BPEL process using a variety of channels. A BPEL process can be designed to send email, voice message, instant messaging IM, or short message service SMS notifications. A BPEL process can also be designed to consider an end users channel preference at runtime for selecting the notification channel. This chapter includes the following sections: ■ Section 16.1, Introduction to the Notification Service ■ Section 16.2, Introduction to Notification Channel Setup ■ Section 16.3, Selecting Notification Channels During BPEL Process Design ■ Section 16.4, Allowing the End User to Select Notification Channels

16.1 Introduction to the Notification Service

Various scenarios may require sending email messages or other types of notifications to users as part of the process flow. For example, certain types of exceptions that cannot be handled automatically may require manual intervention. In this case, a BPEL process can use the notification service to alert users by voice, IM, SMS, or email. The contact information email address, phone number, and so on of the recipient is either static such as adminyourcompany.com or obtained dynamically during runtime. To obtain the contact information dynamically, XPath expressions can retrieve it from the identity store LDAP or extract it from the BPEL payload. This chapter uses the following terms: ■ Notification An asynchronous message sent to a user by a specific channel. The message can be sent as an email, voice, IM, or SMS message. ■ Actionable notification A notification to which the user can respond. For example, workflow sends an email to a manager to approve or reject a purchase order. The manager approves or rejects the request by replying to the email with appropriate content. ■ Human task email notification layer Note: The fax and pager notification channels are not supported in 11g Release 1 11.1.1.