Close popover

Table of Contents

Converting the class of the incoming data pages


You change the class of the incoming data pages to another class when you need to make the data available elsewhere. For example, you want to store data in a data set that is in a different class than your data flow and contains different names of properties than the source data set. You might also want to propagate only a part of the incoming data to a branched destination, like strategy results (without customer data) to the Interaction History data set.

  1. In a data flow, click the Plus icon on a shape, and select Convert.

  2. Double-click the Convert shape to configure it.

  3. Select a conversion mode.

    • Top-level - Converts the class of the top level data pages to another class in your application. When you select this option, the Convert shape outputs a data record for every incoming data record.
    • Embedded - Extracts and converts a property that is embedded in the top-level page list property. The type of the property can be Page or Page List. The page that is the source for the unpacked property can be preserved and propagated to another destination in the data flow through a different branch. When you select this option, the Convert shape outputs as many data records as the number of properties in the Page or Page List.
  4. For the Top-level mode, select the Auto-copy properties with identical names option to overwrite properties in the target class with properties that have the same name in the source class.

  5. Click Add mapping to map properties that do not have the same name between the source class and the target class.

  6. Click Submit.

When you select the Embedded mode to convert a .Customer data record with three appended pages that are called .Subscription_1,.Subscription_2, and .Subscription_3, the Convert shape outputs three data records.

  • Branching a data flow

    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.

  • Creating a data flow

    Create a data flow to process and move data between data sources. Customize your data flow by adding data flow shapes and by referencing other business rules to do more complex data operations. For example, a simple data flow can move data from a single data set, apply a filter, and save the results in a different data set. More complex data flows can be sourced by other data flows, can apply strategies for data processing, and open a case or trigger an activity as the final outcome of the data flow.

  • Types of data flows

    Data flows are scalable data pipelines that you can build to sequence and combine data based on various data sources. Each data flow consists of components that transform data and enrich data processing with business rules.

  • Types of Data Set rules

    Learn about the types of data set rules that you can create in Pega Platform.

Have a question? Get answers now.

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