Skip to main content


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

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.

Combining data from two sources

Updated on March 11, 2021

Combine data from two sources into a page or page list to have all the necessary data in one record. To combine data, you need to identify a property that is a match between the two sources. The data from the secondary source is appended to the incoming data record as an embedded data page. When you use multiple Compose shapes, the incoming data is appended with multiple embedded data pages.

  1. In a data flow, click the Plus icon on a shape, and select Compose.
  2. Double-click the secondary Source shape to configure it. For example, Subscriptions data set.
    Note: When you select a data set, it must be a data set that you can browse by keys, for example, Database Table, Decision Data Store, Event Store, HBase, or Interaction History data set.
  3. Click Submit.
  4. Double-click the Compose shape to configure it.
  5. In the Name field, enter a name for the shape.
  6. Select a property in which you want compose data from your sources. For example, .Subscriptions.
  7. Click Add condition and select a property that needs to match between two sources. You can add more than one condition. For example, When .CustomerID is equal to .CustomerID.
  8. Click Submit.
For example:

The Compose shape outputs one record for every incoming data record after it is enhanced with additional data. This data is mapped to an embedded page or a page list of the incoming record. The input and output class of the data record remain the same.

For example, to create a record that contains the full customer profile for a call center interaction, your compose conditions can look like this:

Compose Customer with data from Subscription into

Property .Subscriptions

When CustomerID is equal to .CustomerID

The Customers data set contains basic information about the customer that needs to be combined with data in the Subscriptions data set.

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