You are here:
Context Definitions for Unified Catalog
Use context definitions to collect data for objects other than the primary process type: Case, Incident, or Service Request. Context definitions make detailed information available for fulfillment and reporting on the appropriate related records.
Process Types and Attributes
A context definition provides predefined attributes that you can add to a service process. The service process also includes attributes from the selected process type: Case, Incident, or Service Request.
Context-definition attributes appear as fields on the intake form. These fields collect the information required for fulfillment or for updating records outside the primary process type.
The fulfillment process uses the collected context-definition attributes to complete the request.
For more information, see Context Definitions.
This example shows how a context definition separates request tracking from detailed fulfillment data during a service request. The primary Service Request record tracks the request status and lifecycle. A secondary custom record contains the information required to fulfill and audit the access request.
When an employee requests access to a secure folder, Unified Catalog uses the
Folder_Access_CD context definition to collect these attributes through
the intake form:
Folder_NameRequired_DurationJustification_Text
The collected values populate a Project_Access__c record for
fulfillment and auditing. This custom record is separate from the primary Service Request
work item.
The context definition acts as a data blueprint that routes the intake information to the secondary record.
| Step | Action | Role of Context Definition | Outcome |
|---|---|---|---|
| 1. Intake | An employee submits the secure folder access request. | The context definition specifies the fields on the intake form, such as Folder Name and Duration. | The primary Service Request record is created. |
| 2. Record Creation | Request routing completes. | The context definition makes the collected data available to populate a record for a non-primary process type. | A Project_Access__c audit or fulfillment record is created and
populated with the access details. |
| 3. Fulfillment | The IT team completes the work. | The fulfillment process references the detailed
Project_Access__c record. |
The Service Request is closed, and the audit data remains on the secondary object. |
The service process uses the detailed data on the
Project_Access__c record to fulfill the request. The primary Service
Request record tracks the request’s overall status and lifecycle.
- Associate Context Definitions with Unified Catalog
Associate active context definitions with Unified Catalog to make their predefined attributes available when you build service processes for Case, Incident, or Service Request. If a flow sends custom context data to an invocable action, configure Apex-defined resources in Flow Builder.
