Click Apply, then OK. Click Apply, then OK.

9-10 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite copy assign assign name=B targets target linkName=AtoB targets copy fromconcatoutput.payload, Bfrom tooutput.payloadto copy assign flow -- link between simple activity and composite activity -- flow name=Flow_2 links link name=AtoB links scope name=scope1 sources source linkName=AtoB sources assign name=A copy fromconcatoutput.payload, Afrom tooutput.payloadto copy assign scope assign name=B targets target linkName=AtoB targets copy fromconcatoutput.payload, Bfrom tooutput.payloadto copy assign flow -- link between composite activities -- flow name=Flow_3 links link name=AtoB links scope name=scope2 sources source linkName=AtoB sources assign name=A copy fromconcatoutput.payload, Afrom tooutput.payloadto copy assign scope sequence name=Sequence_1 targets target linkName=AtoB targets Using Parallel Flow in a BPEL Process 9-11 assign name=B copy fromconcatoutput.payload, Bfrom tooutput.payloadto copy assign sequence flow sequence

9.2.6 What You May Need to Know About Join Conditions in Target Activities

You can specify an optional join condition in target activities. The value of the join condition is a boolean expression. If a join condition is not specified, the join condition is the disjunction that is, a logical OR operation of the link status of all incoming links of this activity. Oracle BPEL Designer does not provide design support for adding join conditions. To add a join condition, you must manually add the condition to the .bpel file in Source view in Oracle BPEL Designer. Example 9–4 provides an example of a join condition. Example 9–4 Join Condition in Target Activity flow links link name=linkStatus2 links empty name=E2 sources source linkName=linkStatus2 transitionConditionfalsetransitionCondition source sources empty empty name=E2 targets joinConditionbpws:getLinkStatuslinkStatus2=truejoinCondition target linkName=linkStatus2 targets empty flow

9.3 Customizing the Number of Parallel Branches

This section describes how to customize the number of parallel branches with the following activities: ■ A FlowN activity in a BPEL version 1.1 project ■ A forEach activity in a BPEL version 2.0 project

9.3.1 Customizing the Number of Flow Activities with the flowN Activity in BPEL 1.1

In the flow activity, the BPEL code determines the number of parallel branches. However, often the number of branches required is different depending on the available information. The flowN activity creates multiple flows equal to the value of N, which is defined at runtime based on the data available and logic within the