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

Continue

Continue

BPMN Implementation: None
This is a Process Developer extension activity. When you save the process, a message appears informing you that the process contains an activity that is not in the BPEL specification.
You can use the continue activity inside a while, repeat until, or
forEach
container. The continue activity causes its immediately enclosed looping activity to stop the execution of the current iteration and move on to the next iteration. In the case of a while, the while's condition expression is evaluated to see if another iteration is possible. In the case of a serial
forEach
, the next iteration in the sequence executes or the loop completes if the current iteration is the final one. In the case of a parallel
forEach
, the continue only affects its enclosed iteration, allowing any parallel iterations to complete normally.
The continue activity allows the root scope of a
forEach
to complete normally so that it is compensatable. Early termination through a continue activity is not considered a faulting state, and therefore does not prevent compensation.
Required Properties
Optional Properties
none
Name. See
Selecting Activity Labels
 
Join Condition. See
Creating a Join Condition for an Incoming Link
 
Suppress Join Failure. See
Process Properties
 
Comment. See
Adding Comments to a Process
 
Documentation. See
Adding Documentation to a Process
 
Setting Visual Properties and Using Your Own Library of Images
 
Execution State. See
Viewing the Execution State of an Activity or Link
 
Extension Attributes and Extension Elements. See
Declaring Extension Elements and Attributes
.
To add a continue activity:
You must use the BPEL-Centric palette to use the continue activity.
  1. On the Process Editor canvas, select a while, repeat until, or
    forEach
    container.
  2. From the
    Event
    palette, drag a continue activity to it.
The following illustration shows an example.
XML Syntax
<continue standard-attributes> standard-elements </continue>


Updated March 30, 2020