Salesforce Docs Portal

Configure Context Definitions as Data Sources

Read data from a context definition into Data Processing Engine definitions to transform and pass it for downstream processing.

Required Editions

View supported editions.
User Permissions Needed
Create and save definitions View permissions information.
To run definitions on-demand: Run Data Processing Engine Definitions On Demand
To configure a context definition as a data source Context Service Admin

Considerations

  • When you launch DPE builder from Context Service, the Data Source and Data Source Subtype nodes are preconfigured automatically based on the selected context definition.
  • DPE prepopulates aliases from their corresponding field names and doesn’t support double underscores in aliases. If your context definition field names include double underscores, DPE automatically converts them to single underscores in the alias field.

Prerequisite

Context definition and mapping must exist and be active.

Steps to configure a context definition as a data source:

  1. In the DPE builder, click New Node, provide the node details, and select node type as Data Source.
  2. In Configuration, set Source Type as Context.
  3. For Source Object, select the context definition.
  4. Provide a context instance identifier, or use an input variable to provide the identifier during runtime.
    Note
    Note The input variable must be of the type Context Instance Identifier.
    Configure context as data source
  5. Save the node configuration.
  6. Create a Data Source Subtype node for each node in the context definition.
    1. Click New Node.
    2. Provide the node details and select the node type as Data Source Subtype.
    3. In Configuration, for Source Node, select the context data source.
    4. For Subtype, select the context node.
    5. Click Select Fields and choose required fields. Aliases auto-populate and are used by downstream nodes.
    Configure context nodes as data source subtypes
  7. Save your node configuration.

Perform the needed transformations on the subtype nodes except for forecasting and statistical functions, such as variance and standard deviations. See Add Transformation Nodes to Your Definition for more details.