Loading
Unified Catalog
Custom Context Definitions for Request Intake Forms

You are here:

  1. Salesforce Help
  2. Docs
  3. Unified Catalog

Custom Context Definitions for Request Intake Forms

Custom context definitions support objects, relationships, and fields that aren’t available in the existing context definition and mappings for a request intake form. Their mappings determine which context attributes appear on request records.

Required Editions

Unified Catalog Editions and Permissions.

Create a custom context definition to support industry-specific data or related-record hierarchies that aren’t available in an existing context definition.

If your intake form uses attributes from a custom context definition, configure Apex-defined resources to send the custom data. See Associate Context Definitions with Unified Catalog. To prefill context attribute values when requestors update service catalog requests, see Configure Flow Intake Forms to Prefill Context Attribute Values.

Context Attributes on Request Records

Service reps and requestors can view context attributes from the parent level and one child level on the request record page. Context attributes appear only when the context attribute root node maps to the object used as the service process type.

The context definition mapping must meet these requirements:

  • If you map a child node, also map each parent node up to and including the root node. Mapping the complete path preserves the node hierarchy.
  • Map each node in the hierarchy to the same object as the service process type. For example, if the service process uses Case, map the root node and each parent node to Case.
  • Don’t map nodes in the same hierarchy to different objects. For example, if some nodes map to Case and others map to Product or Account, the context attributes don’t appear on the request record page.
 
Laster
Salesforce Help | Article