You are here:
Create Data Attributes for Service Process Studio
Create data attributes based on the kind of information to be stored. Data attributes can be of Base or Extended types and can be grouped into sections.
Required Editions
| Available in: Lightning Experience |
| Available in: all editions with the Industry Service Excellence licenses |
| User Permissions Needed | |
|---|---|
| To set up and use Service Process Studio: | Industry Service Excellence permission set AND |
Create data attributes in the Service Process Studio and specify the attribute type, parent attribute, display order, and field identifier details.
Data Attribute Fields
Use this list of Data Attribute fields for your reference.
| Fields | Description |
|---|---|
| Base | Create a data attribute of the type Base to enable security-related capabilities, such as encryption and field-level security. For example, to store a phone number or approved refund amount, create them as attributes of type Base. Additionally, create a data attribute of type Base if you want to map the data attribute to a relevant field of an object. For example, if you want to store data related to a disputed transaction amount, create a data attribute of type Base with the Base Object as Dispute and Field Identifier as Disputed Amount.
When a case is created for a service process request, the Connect API creates a record for the base object and populates the record with all the base attribute values as shown in this example.
If the selected Base Object is Service Catalog Request, the Connect API populates the Service Catalog Request object record with the case Id details and all the base attribute values as shown in this example.
|
| Base Object | The Base Object represents a standard or a custom object where you want to store the value of a base-type data attribute. By default, Service Catalog Request is selected as the Base Object. You can search for and select a different base object.
Before you select base objects, see Considerations for Selecting Base Objects. |
| Extended | Store Extended attributes in the Service Catalog Request Extd Attr Val object in the name-value format. When a case is created for a service process request, the Connect API populates the Service Catalog Request Extd Attr Val object record with the service catalog request record reference and all the extended attribute values. These values are saved as multiple records in the name-value pair format as shown in this example. The Service Catalog Request Extd Attr Val object design ensures that the table grows vertically when the number of extended attributes increase.
|
| Field Identifier (Applicable only to Base Attributes) | The Field Identifier represents the field of the Base Object. The base object’s field stores the value of the base-type data attribute. You can add custom fields to the base object using the Object Manager. When you add custom fields to the base object, they show up in the Field Identifier. |
| Derive attribute value at runtime (Applicable only to Base Attributes with the Data Type as Lookup) | To derive the value of a base-type data attribute automatically when a case is created for a service process request, and to establish a relationship between the base objects, select this checkbox along with an appropriate Reference Object.
To learn more about when to use derive attribute value at runtime in relationship with the base-type attributes, base objects, and reference objects, see Considerations for Selecting Base Objects. |
| Reference Object (Applicable only to the Data Attributes with the Data Type as Lookup) | The Reference Object is a standard or a custom object for which you need a lookup. Lookup-type data attributes maintain referential integrity by adding accurate references to object records. Both Extended Attributes and Base Attributes support lookups.
When the agents view the service process data attributes on the Case Details Lightning component, the lookup-type attributes show navigation links to related records.
|
| Display Order | Control the order in which the data attributes are shown within the section on the Case Details Lightning component. For example, in a section if you create three data attributes named A, B, and C with display order 20, 30, and 10 respectively, then the Case Details component shows the attribute C first, followed by attribute A and attribute B. |
| Parent | Use the Parent Attribute option to store an element that contains another element. Parent attributes are of the type Map or List of Map. A List of Map is a key-value table that can look up any entry by key efficiently. A Map stores key value entries, where each key in the map is associated with a value. For example, a fee reversal transaction has multiple parameters associated with it as shown in this example:
To associate these transaction details with a single transaction record, you can create a parent attribute of type List of Maps named Fee Reversal Transactions and associate this parent attribute with all the attributes representing transaction details as shown in this example.
|
| Default Value | You can specify a default value for a data attribute so that it can be used in case the customer doesn’t provide any relevant information. |
| Description | Provide details about the data attribute usage and its significance. |
| Required | If you specify a data attribute as mandatory, ensure that you send these attributes to the Connect API call that is used to create a case. |










