Table of Contents

Search

  1. Preface
  2. Welcome to Informatica Process Developer
  3. Using Guide Developer for the First Time
  4. Getting Started with Informatica Process Developer
  5. About Interfaces Service References and Local WSDL
  6. Planning Your BPEL Process
  7. Participants
  8. Implementing a BPMN Task or Event in BPEL
  9. Implementing a BPMN Gateway or Control Flow
  10. Using Variables
  11. Attachments
  12. Using Links
  13. Data Manipulation
  14. Compensation
  15. Correlation
  16. What is Correlation
  17. What is a Correlation Set
  18. Creating Message Properties and Property Aliases
  19. Adding a Correlation Set
  20. Deleting a Correlation Set
  21. Adding Correlations to an Activity
  22. Rules for Declaring and Using Correlation Sets
  23. Correlation Sets and Engine-Managed Correlation
  24. Event Handling
  25. Fault Handling
  26. Simulating and Debugging
  27. Deploying Your Processes
  28. BPEL Unit Testing
  29. Creating POJO and XQuery Custom Functions
  30. Custom Service Interactions
  31. Process Exception Management
  32. Creating Reports for Process Server and Central
  33. Business Event Processing
  34. Process Central Forms and Configuration
  35. Building a Process with a System Service
  36. Human Tasks
  37. BPEL Faults and Reports

2. Designer

2. Designer

Extensions and Extension Activities

Extensions and Extension Activities

Open a B-unit file in the B-unit editor, and select
Extensions
or
Extension Activities
from the Outline view. To add an extension, right-mouse click on BPEL Unit.
Extensions
Extensions specify context information required to run a B-unit that are typically defined in a process deployment description. Currently, extensions specify Logical People Groups that are WS-HT Extensions, and can be used within People activities.
You can define the value for a Logical People Group exactly as you define it in the People tab of the Process Deployment Descriptor Editor. For details about static, dynamic and People Query values.
Extension Activities
Extension Activities refer to People activities. You can assert what goes into a People activity and also to specify a response from the People activity if it includes a task (and not a notification).
You can define a People activity for a B-unit test as follows:
  1. Select or add an Extension Activity (a People activity). If this activity is within a loop (for example, a For Each), you can specify a Count for the expected number of times to execute the activity.
  2. Add at least one iteration that is the Default iteration. This is the default for how each iteration should run.
  3. For each iteration, add the Response type that is the outcome of a task:
    • Completed.
      Specify the Output data returned from the task. The data can be Imported or created Inline. By default, the data is set to be imported. You can set a preference for inline, if desired.
      If the data is imported, and if desired, you can add your own XSL files to transform the XML data returned from the task. This allows you to reuse the commonality within the data for different iterations while changing only a few elements of the data. See Tips on Using Parameterized XSL for Input and Assert Data.
      If desired, specify the context data; that is, the names of task initiator, actual task owner, and other assignments for the task.
    • Failed
      . Select a Fault to return.
    • Expired
      . The task reached its expiration date, if the expiration is set.
    • Skipped
      . The task was skipped, if the Skippable option is selected in the task.
  4. Add Asserts
    • Assert Match
      . Specify a Label that is documentation for this Assert, message part and query for the assert, and a pattern to match on. An example might be to match on data returned from one of the B4P custom functions.
    • Assert Equal
      s. Specify the data that should match the data returned.
    • Assert Task
      . Asserts the task details (for example, subject, presentation, and escalations).


Updated March 30, 2020