Skip to main content

Creating an activity to ingest customer data

Suggest edit
Updated on February 3, 2022

This content applies only to Pega Cloud environments

Create an activity to define a sequential set of steps to perform the required processing and run the ingestion data flows.

The goal of this procedure is to complete the following tasks:

  1. Create the following rule with sample parameter values:
    Rule typeRule nameRulesetClass
    ActivityExecuteIngestionDFUPlusCDH-Rules:01-01-01UPlus-Work-Ingestion
    Important: When you configure this rule in your system, use the values that are appropriate for your system.
  2. Add the rule to the Execute ingestion utility shape in the process flow in the Ingestion case type.
Before you begin: Create the Ingestion case type. For more information, see Creating a case type to ingest customer data.

The starting point for this procedure is the process flow that you added to the Ingestion case type, as shown in the following figure:

UploadToXCAR flow
The UploadToXCAR flow.
  1. On the Edit Flow: UploadToXCAR tab, double-click the Execute ingestion utility shape.
  2. Clear the Rule field.
  3. Click the Crosshairs icon to the right of the Rule field.
  4. On the New tab, configure the following parameters:
    1. In the Label field, enter ExecuteIngestionDF.
    2. In the Apply to and Add to ruleset fields, leave the default values.
  5. Click Create and open.
  6. Click the Pages & Classes tab.
  7. Add the RunOptionsPage with the following parameters:
    1. In the Page name field, enter RunOptionsPage.
    2. In the Class field, enter Data-Decision-DDF-RunOptions.
  8. Add the Progress page with the following parameters:
    1. Click the Add item icon to add a new row.
    2. In the Page name field, enter Progress.
    3. In the Class field, enter Data-Decision-DDF-Progress.
    RunOptionsPage and Progress page configuration
    Run Options Page and Progress page are paired with their respective classes.
  9. Click the Parameters tab.
  10. In the Parameters section, add a parameter with the following settings:
    1. In the Name field, enter sleepTime.
    2. In the Data type field, select Integer.
    3. In the Required, ensure that No is selected.
    4. In the In/Out, ensure that In is selected.
    SleepTime parameter configuration
    The sleep Time parameter is configured as an integer.
  11. In the Local variables section, add a variable with the following settings:
    1. In the Name field, enter dfstatus.
    2. In the Data type field, ensure that String is selected.
    dfstatus parameter configuration
    The dfstatus parameter is configured as a string.
  12. On the Steps tab, configure the following steps:
    Tip: The activity uses the DataFlowClassName and DataFlowNameproperties that you configured earlier.
    Step numberMethodStep pagePropertiesNamePropertiesValue
    1Page-NewRunOptionsPage
    2Property-Setparam.sleepTime30
    RunOptionsPage.pyAppliesTo.DataFlowClassName
    RunOptionsPage.pyRuleName.DataFlowName
    3Call pxRunDDFWithProgressPageRunOptionsPage
    4Property-SetProgresslocal.dfstatus@(PegaMKT-Engine:PegaMKTUtilities).monitorDFProgress(tools,param.sleepTime)
    Param.DataFlowIDProgress.pyWorkItemID
    5Page-RemoveRunOptionsPage
    Steps configuration in the ExecuteIngestionDF activity
    An activity configuration with five steps.
  13. Click Save.
  14. Go back to the UploadToXCAR tab.
  15. In the Rule field, select the ExecuteIngestionDF activity that you created.
    Adding the activity rule to the utility shape
    The Execute Ingestion DF rule is selected in the Rule field.
  16. Click Submit.
  17. On the Edit Flow: UploadToXCAR tab, click Save.
    • Previous topic Creating a decision table to ingest customer data
    • Next topic Creating a Parse XML rule to ingest customer data
    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