Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Adding join conditions in event strategies

Updated on July 5, 2022

You configure how data from multiple paths in an event strategy rule is combined by developing a join logic. The join logic is configured in the Join shape on the basis of a when condition, where one property from the primary path equals another property from the secondary path. Every join logic can have multiple join conditions.

Note: Each join can be done only on the basis of events that come from the shapes that immediately precede the Join shape.
  1. In an event strategy rule, access the Properties panel of a Join shape by double-clicking the shape.
  2. Specify the join condition by performing the following actions:
    1. Expand the drop-down list that is to the left of the equal sign and select an event property from the primary path.
    2. Expand the drop-down list that is to the right of the equal sign and select an event property from the secondary path.
    Note: When you join events, the property values from events that are on the primary path always take precedence over the property values from events that are on the secondary path. To preserve property values from the secondary path, you can create additional properties for storing those values.
  3. Optional: Create additional properties to store property values from the secondary path by performing the following actions:
    1. In the Output section, expand the drop-down list and select the property from the secondary path whose values you want to store in another property.
    2. Enter the name of the new property.
  4. Click Submit.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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