Table of Contents

Search

  1. Preface
  2. Understanding Data Types and Field Properties
  3. Designing Processes
  4. Using and Displaying Data
  5. Designing Guides
  6. Designing Process Objects
  7. Designing Service Connectors
  8. Using Connectors
  9. System Services, Listeners and Connectors
  10. Designing Human Tasks

Design

Design

Subprocess Step

Subprocess Step

A Subprocess step embeds one process within another process. When the Subprocess step executes, the embedded process executes.
When you have a process that contains numerous steps, consider splitting the orchestration logic across multiple smaller processes. You can then simplify the design by using the Subprocess step to embed the smaller processes in the parent process. This not only leads to modular design, but also helps with faster loading when you open the process for editing.
The Subprocess step name can contain only alphanumeric characters, underscores (_), spaces, and Unicode characters.
You can define the Input and Output associated fields for the Subprocess step, if any, based on the embedded process.
The following image shows the JMS Dequeue subprocess properties:
 You can view the input and output associated fields for the JMS Dequeue subprocess.

Iteration Rule

The iteration rule applies when the selected process in the Subprocess step has the
Applies To
field set to an object type.
You can configure the subprocess to run on a single object or on all objects in a specified list.
If you select
Run on a single object
, the subprocess runs on the specific object it receives as input. When execution completes, the subprocess passes control to the step that follows in the subprocess.
If you select
Run on each object in list until
, you also choose an event that controls the subprocess execution.
You can select one of the following values to define the event that controls the subprocess execution at run time:
  • Field
    : Available for both the options,
    Run on a single object
    and
    Run on each object in list until
    , that is, when a single object or a list of objects is passed to the subprocess based on the selected Run choice. It contains the process objects or the salesforce connection fields available in the Connection Properties and Input Parameters.
  • Query
    : Available only when you select the
    Run on a single object
    option. You can define a WHERE condition that selects the object passed to the subprocess.
  • List
    : Available only when you select the
    Run on each object in list until
    option. You can define a WHERE condition that selects the objects passed to the subprocess.
The following image shows the iteration rule properties:
You can view the Iteration Rule where the Run on each object in list until option is set to End of list, and On Object List is set to Field.

0 COMMENTS

We’d like to hear from you!