Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Branching a data flow

Suggest edit Updated on April 5, 2022

You create multiple branches in a data flow to create independent paths for processing data in your application. By splitting your data flow into multiple paths, you can decrease the number of Data Flow rules that are required to process data from a single source.

  1. In Dev Studio, click ResourcesData ModelData Flow.
  2. Click the Data Flow rule to branch.
  3. On the Data Flow tab, locate the Destination shape and click Add branch.

    You can add only one Branch shape in a data flow. The Branch shape radiates connectors that lead to each Destination shape that you created. In each of those connectors, you can add Filter, Convert, and Data Transform shapes to apply processing instructions that are specific only to the destination that the connector leads to.

    Caution: When you delete the branch pattern, you remove all additional destination patterns and the patterns that are associated with each branch.
  4. In the new data flow branch, right-click the new Destination shape and select Properties.
  5. In the Output data to section, expand the Destination drop-down list and select the destination rule type:
    • Activity
    • Case
    • Data flow
    • Data set
  6. Depending on the destination rule type, select the rule of that type to become a destination in this Data Flow rule or create a new rule by clicking the Open icon.
  7. Click Submit.
  8. Optional: Click on the branch and select Convert, Data Transform, or Filter to apply additional processing to the data in the new branch. These shapes are specific only to the branch on which they are added and do not influence data processing on other branches in the Data Flow rule. You can add multiple branch-specific shapes in a single branch.
  9. Optional: Repeat steps 1 through 8 to create additional branches in the Data Flow rule.
  • Previous topic Applying text analysis on the data records
  • Next topic Configuring a data flow to update a single property only
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us