Tutorial: Creating an Empty Synchronous Orchestration Workflow for Automatically Adding Catch Branches for Named Faults

Prerequisites:

You performed the steps in Tutorial: Practicing With the Scope Step to Handle Named Web Service Faults.

In this exercise, you add an empty synchronous orchestration workflow to the FaultHandlingOrch in the FaultHandlingProcApp.

To create an empty orchestration workflow for automatically adding Catch branches for named faults:

  1. In App Explorer, under Application Workflows, click NamedFaultAWF.
  2. In the application workflow editor, right-click the GetBuyRating transition, and then select Show Actions on the menu.
  3. On the Actions tab of the Property Editor, click New.

    The Action Wizard opens and asks, "Which type of action do you want to execute?"

    Under Step 1, Orchestration Workflow should be selected.

  4. Under Step 2, click the and continue executing (asynchronous) link, and then select and wait for reply (synchronous).
  5. Click Next.

    The Action Wizard asks, "When do you want to call the orchestration workflow?"

  6. Under Step 1, select After.

    Step 2 should read Invoke an orchestration workflow and wait for reply (synchronous), after this transition occurs.

  7. Click Next.

    The Action Wizard asks, "Which orchestration workflow do you want to call?"

  8. Under Step 1, select (Add new workflow...). The Event With Reply dialog box opens.
  9. In the Name box, type NamedFaultWFWR2.
  10. In the Workflow box, type NamedFaultOWF2.
  11. In the Fields used by event list, select the Description and Title check boxes.
  12. In the Fields returned by event list, select the Description and Title check boxes.
  13. Click OK.

    Under Step 1, NamedFaultWFWR2 is selected on the menu and EventNoticeWithReply appears in the list. Step 2 now reads Invoke an orchestration workflow and wait for reply (synchronous), after this transition occurs, Call NamedFaultWFWR2.EventNoticeWithReply.

  14. Click Finish.

    NamedFaultWFWR2 appears below NamedFaultWFWR1 under Orchestration Links, and NamedFaultOWF2 appears below NamedFaultOWF1 under Orchestration Workflows in App Explorer.

Related Topics

Tutorial: Creating a Practice Process App for Fault Handling