Skip to main content

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

Creating a case type to ingest customer data

Updated on August 3, 2022

This content applies only to Pega Cloud environments

Manage the data ingestion process by configuring an ingestion case type. In the case type, you can specify when to start the ingestion process and how to handle errors.

The goal of this procedure is to create the following rules with sample parameter values:

Rule typeRule nameRuleset
Case typeIngestionUPlusCDH-Rules:01-01-01
Important: When you configure these rules in your system, use the values that are appropriate for your system.
  1. In the navigation pane of Dev Studio, click Case types.
  2. Click Add a case type.
  3. In the Name field, enter Ingestion.
  4. Expand the Advanced Settings section, and then configure the following parameters:
    1. In the Ruleset field, select UPlusCDH-Rules.
    2. In the Ruleset version field, select 01-01-01.
  5. Click Submit.
  6. Add stages to the case type with the following settings:
    SettingsStart stageUploadToXCAR stageFinish stageErrorHandling stage
    When all processes in this stage are completeAutomatically move to next stageResolve the caseResolve the case
    Set case status on stage entryNewPending-ImportingCompletedResolved-Failed
    Resolution statusResolved-CompletedResolved-Failed
    Adding stages to the ingestion case type
    The ingestion case type with four stages.
  7. Hover over the UploadToXCAR process, click the Configure process icon, and then click Open process.
  8. On the Create Flow tab, configure the following parameters:
    1. In the Label field, enter a short description of the flow, for example, Upload to XCAR.
    2. In the Apply to field, select the ingestion work class, which in this example is UPlus-Work-Ingestion.
    3. In the Add to ruleset field, select UPlusCDH-Rules.
  9. Click Create and open.
  10. Add components to the process flow and connect them as shown in the following figure:
    Configuring the UploadToXCAR flow
    A flow with two decision shapes, a utility shape, and a change to a specific stage shape.
    Note: The second Decision shape and the Change to a specific stage shape are optional. You can use them to configure error handling in your ingestion case type.
  11. Double-click and rename each component as follows:
    Decision (first)Process type?
    UtilityExecute ingestion
    Decision (second)Error?
    Change to a specific stageChange to ErrorHandling
    UploadToXCAR flow
    The UploadToXCAR flow.

    In the case workflow view, the process flow in the UploadToXCAR stage contains the following steps:

    Ingestion case type
    The ingestion case type with four stages.
  12. Click Save.
What to do next:

Configure the components of the UploadToXCAR flow:

  1. Create the processType, DataFlowClassName, DataFlowName, and ManifestDetails properties that are required to configure other rules for data ingestion (a decision table, an activity, and a Parse XML rule). For more information, see Creating properties to ingest customer data.
  2. Configure the Process type? decision shape in the UploadToXCAR flow.

    Use this decision shape to select the ingestion data flow to run based on the value of the processTypeproperty. This property identifies the type of files to be loaded, for example, files that contain customer data for the Account, Subscriber, or Product Holding class. The system obtains the value of the processType property from the manifest file. For more information, see Creating a decision table to ingest customer data.

  3. Configure the Execute ingestion utility shape in the UploadToXCAR flow.

    Use this utility shape to define an activity to perform the required processing and run the ingestion data flows. For more information, see Creating an activity to ingest customer data.

  4. Optional: Configure the Error? and Change to ErrorHandling shapes in the UploadToXCAR flow.

    You can configure these two shapes to handle errors that might occur while the files are ingested into the target data set. The configuration of these components is not covered in this tutorial.

    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. is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us