Shared Catalog Exercise Guide

Enterprise Product Catalog
Exercise Guide
Version 1.0
Exercise Guide
TABLE OF CONTENTS
Preface 5
Overview 5
What You Will Learn 5
Prerequisites 6
Enterprise Product Catalog Overview 7

The Vlocity Product Console 8
Industries CPQ 8
Product Model 9
Exercise 3-1: Creating Picklists 10

What is a Picklist in EPC? 11
Task 1: Review the Vlocity Product Console 12
Task 2: Create a picklist 15
Task 3: Create picklist items 18
Task 4: Create additional picklists and picklist items 21
Exercise 3-2: Creating Product Attributes 24

What is a Product Attribute? 25
What is an Attribute Category? 25
Task 1: Create a Wearable attribute category 26
Task 2: Create a Band Type product attribute 29
Task 3: Create a Connectivity product attribute 33
Task 4: Review the product attributes in the Wearable attribute category 35
Exercise 3-3: Creating Product Object Types 36

What is a Product Object Type? 37
Task 1: Review the existing product object type hierarchy 39
How are attributes inherited within the object type hierarchy? 41
Task 2: Review the attribute and field assignments 42
What is an Object Type Layout? 43
How are Object Type Layouts inherited within the Object Type Hierarchy? 43
© Copyright 2022 Salesforce.com, inc. All rights reserved. 2

Exercise Guide
Task 3: Review an Object Type Layout 44

Task 4: Create a new product object type 46
Task 5: Add attributes for the product object type 48
Task 6: Set attribute metadata for the product object type 49
Task 7: Modify the product object type’s layout 51
Exercise 3-4: Reviewing Product Life Cycles 53

What is a Product Life Cycle? 54
What do product selling period dates allow? 54
Task 1: Review product selling periods on a product 58
Task 2: Use the Find References button 62
Task 3: Review product selling periods in the Cart 64
Exercise 3-5: Creating Products 68

Task 1: Create a product specification for the Apple Watch Series 5 69
Task 2: Set design-time attribute metadata values for the product 73
Task 3: Set run-time attribute metadata values for the product 78
Task 4: Add a product image as an attachment 82
Task 5: Add a base price to the product 84
Task 6: Review Layout Management and Debug facets 87
Exercise 3-6: Creating Product Bundles 89

What is a product bundle? 90
What is product cardinality? 90
Task 1: Create a product bundle 91
Task 2: Create the structure of the product bundle 92
Task 3: Override the cardinality of the child product bundle 96
Task 4: Create a price list entry for the product bundle 100
Exercise 3-7: Managing the Shared Catalog 102

What does it mean to manage the Shared Catalog? 103
Understanding Caching in Your Industry Cloud 104
Managing the Platform Cache 105

Exercise Guide
What other jobs should be run? 110

Task 1: Refresh the product hierarchy cache 113
Task 2: Confirm that batch jobs completed successfully 116
Exercise 3-8: Test the New Products in the Cart 123

Task 1: Review the new product and product bundle in the Cart’s product list 124
Task 2: Add the product bundle to the Cart and test the cardinalities 126
Exercise 3-9: Create Tablet Products Challenge 130

Task 1: Review product requirements 131
Task 2: Build products in EPC 133
Task 3: Test new products in the Cart 134

Exercise Guide
Preface
These training exercises are based on the Spring’ 22 release of Salesforce Industries
Communications, Media, and Energy & Utilities Clouds. For additional information about
the topics covered, see the documentation available in Vlocity Success Community at
https://success.vlocity.com.
Overview
This module covers fundamental features and functionality of the Enterprise Product
Catalog, a key product of the Salesforce Industries Communications, Media, and Energy &
Utilities Clouds. This module will introduce shared catalog capabilities including how to use
the Vlocity Product Console to create products and manage the shared catalog.
This is a hands-on course with practical lab exercises. The lab exercises are designed to be
used with the provided training playground.
What You Will Learn

When you complete this training, you will be able to:
● Navigate the Vlocity Product Console

● Create picklists and picklist items
● Create product attributes and attribute categories
● Create product object types and understand the inheritance architecture
● Define product selling periods and create products using them
● Set product attribute metadata and override attribute defaults
● Create product bundles and define product cardinality
● Calibrate product attributes
● Explain and set up the platform cache
● Build product hierarchies and initialize the cache
● Describe the CPQ Industries batch jobs and review their status

Exercise Guide
Prerequisites
The prerequisites for this training include a solid understanding of basic Salesforce concepts
and functionality. You should also have a working knowledge of telecommunications,
media, or energy and utilities industry business objectives.

Exercise Guide
Enterprise Product Catalog Overview

Our Enterprise Product Catalog, or EPC, revolutionizes the Industries CPQ and order
management space by providing the first enterprise catalog-driven application that:
● Integrates into your end-to-end ecosystem by combining a complete product,

service and resource model to drive sales, Industries CPQ, ordering and fulfillment
functions.
● Provides one user interface with common tools, enabling your teams to
collaboratively and rapidly create, manage and deliver offerings to market.
● Allows for an evolutionary approach to transform both front office and back office
systems to become catalog-driven over time. This supports the elimination of data
silos and the mastering of both commercial and technical entities in a single model.
EPC is powered by a shared catalog. The shared catalog uses a metadata-driven approach to
accommodate all of the incarnations of a product, as it travels from a twinkle in the
customer’s eyes to the physical implementation in the customer’s hands. EPC is informed by
the TMForum SID model. It supports all levels of product definition, including offers,
product specifications, services and resource specifications.
● Offers are designed by Marketing and sold to particular channels/customer

segments with specific pricing.
● The Product Spec is created by Product Management and describes all the product
components.
● Then, using Order Management, the Product Spec is translated into the various
technical and manufacturing specifications tuned for each of the downstream
systems that use them.

Exercise Guide
The Vlocity Product Console
The Vlocity Product Console provides a unified user experience to manage EPC elements in
a single, contextual interface. Using this interface, you will perform product management by
defining and maintaining product entities. You will also build foundational constructs like
attributes and picklists, and metadata constructs like product object types. You will see
many elements of Industries CPQ co-located in the Vlocity Product Console, to provide
seamless integration between the shared catalog and the ability to configure, price and
quote the products in the catalog.
Industries CPQ
Industries CPQ has a powerful rules engine which ensures that quotes and orders are valid
before they’re submitted. This minimizes order delays, customer confusion and
dissatisfaction. Industries CPQ picks up where CRM ends, providing real-time product,
pricing and business rules using natural language and declarative administration. Using
Industries CPQ, you can:
● Design basic and advanced availability, eligibility, compatibility and pricing rules.
● Standardize the introduction of new products and services.
● Ensure accurate capture of new, move, add, change and disconnect orders.
Industries CPQ supports both B2B and B2C lead-to-cash processes. The open architecture
allows you to use Industries CPQ components, services and user interfaces selectively as
individual components, and to integrate process flows with external systems, all using a
unified user interface.

Exercise Guide
Product Model
The product model of the product entities that you will build in this training module is
diagrammed below.

Exercise Guide
Exercise 3-1: Creating Picklists

Scenario
Following product modelling best practices, Devi builds the new smartwatch product model
in the Vlocity Product Console from the bottom up, which means his first step is to create
attribute picklists for Connectivity, Band Type, and Band Color. As Devi knows well, picklists
protect us from the human frailty of data entry errors, and thus the attributes he will create
rely heavily on picklists.
Goal
● Navigate the the Vlocity Product Console
● Create a picklist
● Create picklist items
Tasks
1. Review the Vlocity Product Console
2. Create a picklist
3. Create picklist items
4. Create additional picklists and picklist items
Time: 30 mins
ALERT:
If you’ve just received your training playground, add your email address to the
system administrator profile to ensure you receive all system notifications. In
the upper-right, click on the Avatar and select Settings. Enter your email
address in the Email field on the Personal Information page and click Save.

Exercise Guide
What is a Picklist in EPC?

When an attribute has multiple values, a picklist represents all of the defined values for that
attribute. Picklists in EPC perform a similar function to Salesforce picklists but they are
custom objects called picklists (API name: vlocity_cmt__Picklist__c). Picklists can be
created with data types of text, number, Boolean (True/False), date or date time. Picklists
are designed to be globally reusable across attributes assigned at the object type level or at
the product level.

Exercise Guide
Task 1: Review the Vlocity Product Console
1. Using the Lightning App Launcher , click Configure Price Quote (CPQ).
2. In the Lightning Navigation Bar, click the Vlocity Product Console.
3. Review the Dashboard, which provides a unified user experience to manage EPC
and Industries CPQ elements in a single contextual interface.
a. Notice the EPC elements: Product, Attribute, Picklist, Object, Facet, and
Section.
b. Notice the CPQ elements: Promotion, Discount, Offer Migration Plan, Pricing,
String Translations and Rules (Context Rules)
Notice the Switch to Salesforce link in the upper right, which allows you to
exit the Vlocity Product Console.

Exercise Guide
4. Under Product Management, next to Product, click the search icon.
5. Next to the Search Product… entry dialog, click the search icon. The list of all
products is returned.
6. Click the name of the 4G LTE Data Plan product in the list or click the Edit icon
to open the product for editing.
7. Notice the list of tabs in the Console’s tab navigation bar.
8. Notice the reload icon in the right corner.

Exercise Guide
ALERT:
Do not use your browser’s refresh or back buttons while working in the Vlocity
Product Console. Using these buttons will cause you to exit from the Console,
and any changes that have not been saved will be lost. Instead, use the reload
icon to refresh the page when necessary, and the Console’s tab navigation bar.
9. Notice the Save button.
ALERT:
The Vlocity Product Console does not use an implicit save model. All changes
must be explicitly saved using the provided buttons in the user interface.
10. Notice the related items (like General Properties) listed on the left; these interface
elements are called facets.
11. In the Console’s tab navigation bar, click the Xs to dismiss the tabs that you opened
and return to the Dashboard.

Exercise Guide
Task 2: Create a picklist
In this task you are going to create a picklist called Connectivity.
1. On the Dashboard, under Foundation next to Picklist, click the new icon . This
launches the New Picklist dialog.
2. Notice the required fields: Name, Code, and Data Type.
NOTE:
Required fields for picklists and other EPC objects are not set within the
Salesforce Setup. Instead, they are set within the Vlocity Product Console
using Object Type Layout Management field requirements. You can configure
EPC object field requirements to your own unique specifications and
processes.

Exercise Guide
3. In the New Picklist dialog, enter the following information.

Field Value Notes
Name Connectivity
Code PKL_CONNECT Recommend using a PKL_

prefix to easily identify
picklists. This value is not
required to be unique.
Description Wearable connectivity

options
Data Type Text
Active ✓ Recommend setting the

Active flag, although it is
not currently enforced.
Effective From [today’s date] Recommend setting the

Effective From (and
Effective Until, if desired)
fields, although it is not
currently enforced.
NOTE:
The picklist fields above are only visible at design-time. In other words, none
of the information entered above will be visible at run-time to users during
order capture.
4. Click Save. You will see a green “Picklist created!” success message.

Exercise Guide
5. Once the picklist is saved, you will now see a panel on the left, listing all of the facets
for this object, which for picklists includes the General Properties facet and the
Picklist Items facet.

Exercise Guide
Task 3: Create picklist items
Now that you have created the picklist, it is time to add items for the end user to select.
1. Click the Picklist Items facet.
2. Under Picklist Items, click New Item. The new picklist item dialog will open in a
pane on the right.
3. In the New Picklist Item dialog under the reload icon, notice the resize and close
buttons on the right.

Exercise Guide
4. Enter the following information.

Field Value Notes
Text Value GPS This value will be evaluated programmatically,

such as in Industries Order Management
decomposition process. The data type of this
field is set by the picklist data type. Because you
specified a text data type on the picklist, you
have a text entry field on the picklist item.
Label GPS This value will be visible to the user at run-time

in the Cart.
Code PLI_GPS This value is not required to be unique.
Abbreviation This value is optional. It is used to abbreviate

the label text when needed.
Sequence 10 Recommend using sequences of 10, 20, 30 to

simplify later insertions.
Active ✓ Recommend setting the Active flag, although it

is not currently enforced.
Effective [today’s Recommend setting the Effective From (and

From date] Effective Until, if desired) fields, although they
are not currently enforced.
5. Click Save. You will see a green success message.
6. Under Picklist Items, click New Item.

Exercise Guide

Field Value
Text Value GPS Cellular
Label GPS + Cellular
Code PLI_GPS_CELL
Sequence 20
Active ✓
Effective From [today’s date]
8. Click Save. You will see a green success message.
9. In the Console tab navigation bar, click the X to close the Connectivity tab.

Exercise Guide
Task 4: Create additional picklists and picklist items
1. Create a picklist and picklist items for Band Type using the steps you’ve just learned.
BAND TYPE PICKLIST
Field Value
Name Band Type
Code PKL_BAND_TYPE
Description Wearable Watchband Options
Data Type Text
Active ✓
BAND TYPE PICKLIST ITEMS
Picklist Text Label Code Sequence Active Effective

Item # Value From
1 Sport Sport PLI_SPORT 10 ✓ [today’s date]
2 Stainless Stainless PLI_STEEL 20 ✓ [today’s date]

Steel Steel

Exercise Guide
2. Create a picklist and picklist items for Band Color.
BAND COLOR PICKLIST
Field Value
Name Band Color
Code PKL_BAND_COLOR
Description Wearable watchband color options
Data Type Text
Active ✓
BAND COLOR PICKLIST ITEMS
Picklist Text Label Code Sequence Active Effective

Item # Value From
1 Fog Fog PLI_CLR_01 10 ✓ [today’s date]
2 Pink Pink PLI_CLR_02 20 ✓ [today’s date]

Sand Sand
3 Gray Gray PLI_CLR_03 30 ✓ [today’s date]
4 Black Black PLI_CLR_04 40 ✓ [today’s date]
5 White White PLI_CLR_05 50 ✓ [today’s date]
6 Seashell Seashell PLI_CLR_06 60 ✓ [today’s date]

Exercise Guide
In the next exercise, you’ll put these picklists to work by linking them to product attributes.

Exercise Guide
Exercise 3-2: Creating Product Attributes

Scenario
Product Attributes are an important part of your industry cloud since they are used not only
to price and configure products at run-time but also to map commercial products to
technical products in order management processes. Devi is on board with the beauty of
product attributes, so he creates attributes to describe his new smartwatch wearable
products.
Goal
● Create attribute categories
● Create product attributes
● Link picklists to product attributes
Tasks
1. Create a Wearable attribute category
2. Create a Band Type product attribute
3. Create a Connectivity product attribute
4. Review the product attributes in the Wearable attribute category
Time: 15 mins

Exercise Guide
What is a Product Attribute?
Product attributes provide a powerful and flexible way to extend product entities. Product
attributes are stored in an aggregate JSON blob on the Product object and are used
extensively throughout Industries CPQ and Order Management. In Industries CPQ we can
use product attributes in a number of ways, including:
● to configure product specifications, allowing users to specify product colors, sizes,

and other options.
● to change product pricing using attribute-based pricing rules.
● in Order Management, to map commercial products, or the products that customers

see, with technical products that communicate with backend systems to fulfil the
products that are purchased.
What is an Attribute Category?

Attribute categories are used to group attributes. They also display as headings at run-time
in the Cart’s Configuration window. Attribute categories are required to create product
attributes.

Exercise Guide
Task 1: Create a Wearable attribute category
You’ll begin by creating a Wearables attribute category to group all smartwatch attributes.
NOTE:
Product attributes are to be created and managed through the Vlocity Product
Console not through the Salesforce Product tab.
1. In the Lightning Navigation Bar, click More, and then right-click Vlocity Attribute
Categories to open in a new browser tab.
2. Click New in the top right.

Exercise Guide
Field Value Notes
Name Wearables This value is displayed at run-time in the Cart’s

configuration window, so it should be
customer friendly.
Code ACAT_WEAR This value is required and must be unique.

This code is displayed only during
design-time.
Description For wearable This value is used only during design-time.

product
options
Applicable Types Product2 This value is required for product attributes.
Applicable Sub Type Product This value is required for product attributes.
Attribute
Display Sequence 40 This value is required and must be unique. It’s

used to sequence the attribute category in the
Cart’s configuration window. Recommend
using a 10, 20, 30 sequence to enable easy
insertions in the sequence at a later date.

Exercise Guide
4. Click Save.
5. Click on the Vlocity Product Console in the Lightning Navigation Bar to return to
the Dashboard.

Exercise Guide
Task 2: Create a Band Type product attribute
1. Make sure you are on the Vlocity Product Console Dashboard.
2. Under Foundation next to Attribute, click the new icon . This will launch the
New Attribute dialog.
3. In the New Attribute dialog, enter the following information.

Exercise Guide
Field Value Notes
Name Band Type This value is required and will be visible at run-time in
the Cart’s configuration window.
Code ATT_RT_BT This value is required, and only visible during

design-time. Recommend using an ATT_ prefix to easily
identify attributes. This value is not required to be
unique. In addition, if desired, you can code in the
type of attribute, such as RT for Run-Time, DT for
Design-Time, or DC for Decomposition (used in Order
Management).
Description Smartwatch This value is displayed only at design-time and can be

band types used to provide more information about the attribute.
Active ✓ The Active flag must be checked for the attribute to

display.
Attribute Wearables Using the lookup dialog, select the Wearables attribute
Category category that you just created.
Value Type Picklist Your end user will be selecting from a picklist
Value This field is used to enter a value for other value types
such as Text or Number. You are using a picklist, so no
value is needed because all values will come from the
linked picklist.
Picklist Band Type Using the lookup dialog, select the Band Type picklist
you created in the previous exercise.
Display 10 This value is required and must be unique within the

Sequence Attribute Category, although it is not enforced currently
during data entry.

Exercise Guide
4. Click Save.

Exercise Guide
5. Click the Applicable Objects facet on the left.
6. In the Applicable Objects list, verify the box next to Product2 Object is checked.
ALERT:
If the Applicable Object is not set, the attribute will not display when creating
an object type or a product.
7. In the Console’s tab navigation bar, click the X to close the Band Type window.

Exercise Guide
Task 3: Create a Connectivity product attribute
1. Under Foundation next to Attribute, click the new icon . This will launch the
New Attribute dialog.
2. In the New Attribute dialog, enter the following information.
Field Value
Name Connectivity
Code ATT_RT_CT
Description Smartwatch connectivity option
Active ✓
Attribute Category Wearables
Value Type Picklist
Picklist Connectivity
Display Sequence 20

Exercise Guide
3. Click Save.
4. Click the Applicable Objects facet on the left.
5. In the Applicable Objects list, verify the box next to Product2 Object is checked.
6. In the Console’s tab navigation bar, click the X to close the Connectivity window and
return to the Dashboard.

Exercise Guide
Task 4: Review the product attributes in the Wearable attribute category
1. In the Lightning Navigation Bar, right-click Vlocity Attribute Categories to open in a

new browser tab. If you can’t see the Attribute Categories option, you will find it by
selecting the More option.
2. Under Recently Viewed, click Wearables.
3. Review the new attributes in the Wearables attribute category.
4. Select the Vlocity Product Console option in the Lightning Navigation Bar to return
to the Dashboard.
In case that wasn’t enough, there’s more to learn about product attributes. They have
additional metadata properties that are set when the attributes are assigned to an object
type or a product, which you will do in the next two exercises.

Exercise Guide
Exercise 3-3: Creating Product Object Types

Scenario
Now that Devi has the “foundation” of his product model built, he’s ready to develop the
“framing”. Using the power of product object types, he can streamline the creation of his
product catalog by creating classes of products that have similar characteristics. In his
model, he decides to add a new SmartWatch as an object subtype of the SmartPhone
object type, which will allow his new object type to inherit all of the fields and attributes
defined in the object hierarchy.
Goal
● Create product object types
● Understand the inheritance architecture of product object types
● Assign product attributes and attribute metadata to an object type
● Modify object type layouts
Tasks
1. Review the existing product object type hierarchy
2. Review the attribute and field assignments
3. Review an object type layout
4. Create a new product object type
5. Add attributes for the product object type
6. Set attribute metadata for the product object type
7. Modify the product object type’s layout
Time: 30 mins

Exercise Guide
What is a Product Object Type?
A product object type is a reusable entity that describes a common set of fields and
attributes as well as the layouts for all linked products. You can use object types to group
products with similar characteristics, to ensure consistent behavior and application of rules.
Object types are designed with an IS-A inheritance type architecture. For those familiar with
object-oriented programming and design, you’ll recognize that object types create
relationships between abstractions where one object type is a subtype of another object
type. The first level of abstraction is called simply an object type, and the subsequent levels
are called subtypes.
Then, when you apply this relationship to a product, the object type allows the product to
inherit all of the characteristics of its object type hierarchy.

Exercise Guide
It’s recommended to create a base object type for each layer of your SID model (Offer
Specs, Product Specs, Service Specs and Resources Specs) during initial setup. These are
essentially your product catalog’s “primordial objects” from which all other products
descend. You’ll assign all of the fields in the product catalog to the base product object
type, and then you can create object subtypes for all the product classes and products in
your catalog. They will then inherit the base product’s layout, fields, and any attributes. Note
that the base object type layouts must be created manually, which takes a few minutes, but
after that, all the subsequent object subtypes will inherit the layout when they are created.
NOTE:
In your training playground, an initial product object type hierarchy has
already been created for you, including all of the base product object types.
BEST PRACTICE:
Currently, it’s not recommended to move object types within the hierarchy.
Therefore, careful consideration is required when planning your object type
hierarchy and your product catalog design. Salesforce Industries Services can
assist with product catalog design and modeling best practices.

Exercise Guide
Task 1: Review the existing product object type hierarchy
1. You should be in the Dashboard of the Vlocity Product Console. Click X to close any
open tabs if necessary.
2. Under Metadata, click the search icon next to Object.
NOTE:
There is no new icon next to Object because the Vlocity Product Console
does not allow the creation of custom EPC or Industries CPQ objects. The
objects in the Vlocity Product Console are created during installation and are
part of the managed package.
3. Next to the Search Object… entry dialog, click the search icon . The list of
objects is returned.
4. Scroll down and click the Product2 Object.
5. On Product2 Object, click the Object Types facet.
6. Review the object type hierarchy that has been prebuilt for you.
a. Notice the BASE objects types for the four SID layers.
b. Notice that the BASE Offer Spec Type has no object subtypes.
BEST PRACTICE:
It’s recommended that object types in each of the SID layers are “tuned” to
the product entity as it is manifested within the current layer only. Product
entities can then be transformed from one layer to the next using Order
Management’s decomposition mappings. In keeping with this best practice,
you will notice that the BASE Offer Spec Type in EPC has no object subtypes
because “an offer is an offer” and should have homogenous characteristics.
However, the other BASE object types are not flat hierarchies because the
product entities they describe are fundamentally distinct from one another.

Exercise Guide
7. Click the > symbol to the left BASE Product Spec Type to expand the object type
name.
8. Select SmartPhone Product Spec from the list of BASE Product Spec Type child
object types or click the Edit icon next to the name to open the object type for
editing.

Exercise Guide
9. Notice the SmartPhone Product Spec’s parent object type is the BASE Product Spec
Type, which means that all its fields and its layout have been inherited by the
SmartPhone Product Spec.
BEST PRACTICE:
It’s recommended that any data element that is common across the catalog
be described using a field, and data elements that are unique to a subset of
products in the catalog be described using an attribute. Following this best
practice, all of the BASE object types in your training have no attributes
assigned, only fields.
How are attributes inherited within the object type hierarchy?
Within the object type hierarchy, attribute inheritance is a true dynamic inheritance. If you
assign new attributes to an object type, all object subtypes and products linked to the
object type hierarchy will dynamically be assigned those attributes. Importantly, however,
any attributes or fields that are inherited cannot be deleted from the object type, and
instead must be unassigned from the object type or deactivated at the product level.

Exercise Guide
Task 2: Review the attribute and field assignments
1. In the SmartPhone Product Spec, click the Attributes and Fields facet in the
sidebar.
2. Notice the six attributes and all the fields that have been assigned to this object type.

Exercise Guide
What is an Object Type Layout?
Object type layouts are like Salesforce page layouts, and they allow you to control the layout
and organization of an object type’s attributes and fields. Using object type layouts, you can
customize layouts for each class of product, so that the attributes and fields displayed at
design-time for a SmartPhone are different to those of a backpack, for example. An object
type layout is made up of facets, sections, and section elements.
As you have seen in the past few exercises, a facet displays on the left navigation menu, and
it contains sections and section elements.
A section is essentially a container for a Visualforce page, and a section can have either a
standard field layout view type or a custom view type. The Communications, Media, and
Energy & Utilities Clouds provide several common custom view types, and customers can
create their own custom view types by creating custom Visualforce pages.
Section elements are fields or attributes, and they are grouped in sections.
How are Object Type Layouts inherited within the Object Type
Hierarchy?
Unlike the attribute and field dynamic inheritance model, object type layouts use a “hybrid”
inheritance model. When a new object subtype is created, the Vlocity Product Console
creates a new layout for the object subtype via a deep copy. What this means is that any
subsequent changes to the object subtype’s layout will not be replicated down the hierarchy
after initial creation. This allows you to change the layout, adding or deleting fields for each
object type, without having to worry about your layouts being altered with the additions of
any fields on the object subtype.

Exercise Guide
Task 3: Review an Object Type Layout

1. Click the Layout Management facet.
2. Notice the facets, sections, and section elements for the SmartPhone Product
Spec.
3. Scroll down to the Attribute Properties facet.
NOTE:
We have configured your training playground to include two custom facets
and corresponding sections, and they are Attribute Properties and Debug.
These custom facets can be implemented in your own orgs, if desired.
4. Click on the Design Time Attributes Section. The section details window will display.
5. Notice the View Type is set to Field Layout. This is the standard field layout view
type, like a standard Salesforce page layout, and no View URI is needed.
6. Notice that this facet groups the six assigned attributes into design-time and
run-time attributes, for ease of data entry.
7. Scroll down to the Attributes and Fields Facet and click the Attributes and Fields
Section. The section details window will display.

Exercise Guide
8. Notice the View Type is set to Custom View, and the View URI specifies the
corresponding custom Visualforce page for this section.

Exercise Guide
Task 4: Create a new product object type
1. In the Console’s tab navigation bar, click the Product2 Object tab.
2. Click New Object Type.
3. In the New Object Type window on the right, enter the following information.
Field Value
Name SmartWatch Product Spec
Parent Object Type SmartPhone Product Spec
Is Active ✓

Exercise Guide
4. Click Save. You should now be able to see your new SmartWatch Product Spec
within the Product2 Object Types.
NOTE:
You might be wondering should smartwatches be created as a subtype of
smartphones; in other words, “IS-A” smartwatch a smartphone, following
product modelling best practices? In real life, probably not. But in our
simplified training playground, yes! And you will use it to have some fun with
inheritance.

Exercise Guide
Task 5: Add attributes for the product object type

1. Click the new SmartWatch Product Spec to open the object type for editing.
2. Click the Attributes and Fields facet.
3. Notice that the fields and attributes have been inherited from the SmartPhone
Product Spec.
4. Click Assign Attributes/Fields.
5. In the Assign Attributes and Fields window, click the checkboxes next to the Band
Type and Connectivity attributes that we created in the previous exercise.
6. In the Assign Attributes and Fields window, click Assign.
7. The two new attributes now display in the assigned attributes and fields list.

Exercise Guide
Task 6: Set attribute metadata for the product object type
Attribute metadata can be set during assignment at the object-type level and products
created from the object type will inherit both the attributes and their metadata. Attribute
metadata is overridable or non-overridable depending on which attribute metadata is
selected. Non-overridable metadata includes Run-time Configurable, Is Encrypted, Is Not
Assetizable, and Is Not Translatable. These attribute metadata flags must be set at the
object type level and cannot be changed at the product level. Overridable metadata
includes Has Rule, Hidden, Read Only and Required, and these can be changed at the
product level. Both are demonstrated later in this module.
1. Within the SmartWatch Product Spec, click on Band Type to open the Attribute
Metadata pane.
2. In the Attribute Metadata pane under BEHAVIORS, enter the following metadata
information.
Field Value Notes
Required ✓ This will require all users to select a value before

they can submit the order.

Exercise Guide
3. In the Attribute Metadata window, click Save.
4. Next, click on Color to open the Attribute Metadata pane, select the Required
checkbox under the BEHAVIORS section, and click Save.
5. Similarly, click on Connectivity to open the Attribute Metadata pane, and select the
Required checkbox under the BEHAVIORS section, and click Save.

Exercise Guide
Task 7: Modify the product object type’s layout
1. Within the SmartWatch Product Spec object, click the Layout Management facet.
2. Scroll down to the Attribute Properties facet.
3. In the Run Time Attributes section, click Add Section Element.
4. In the Add Section Element pane on the right, enter the following information.
Field Value
Field Band Type
Display Label Band Type
Sequence 30
5. Click Save.
6. In the Run Time Attributes section, click Add Section Element.

Exercise Guide
7. In the Add Section Element pane on the right, enter the following information.
Field Value
Field Connectivity
Display Label Connectivity
Sequence 40
8. Click Save.
9. In the Console’s tab navigation bar, click X on all the open tabs to close them. This
will bring you back to the Dashboard.

Exercise Guide
Exercise 3-4: Reviewing Product Life Cycles

Scenario
Devi is just about ready to enter the new products into the shared catalog. However, he
wants to make sure that the product life cycles are managed properly, and the selling period
dates are used correctly by his company, Infiwave.
Goal
● Define product selling periods
● Find product references
● Identify product selling period dates in the Cart
Tasks
1. Review product selling periods on a product
2. Use the Find References button
3. Review product selling periods in the Cart
Time: 15 mins

Exercise Guide
What is a Product Life Cycle?

The shared catalog supports the commercial product lifecycle by allowing you to define
current future, past and retired products. The stages defined below use Product Selling
Period dates.
● Current Product – is a product that is currently available for sale.
● Future Product – is a product that will be sold in the future. This product can be
configured and ordered but will be fulfilled once its selling period and fulfilment
begins. In order to ensure that future products are not assetized until they are
fulfilled, you must implement Future Date Ordering.
● Past Product – is a product that is no longer for sale but still can be fulfilled for
orders that have already been placed and changed for orders that have already been
assetized.
● Retired Product – is a product that is no longer supported, cannot be ordered or

fulfilled, or changed for orders that have been assetized.
What do product selling period dates allow?

Product Selling Period Dates allow you to set the selling period, fulfillment start date, and a
date to retire commercial products.
● Selling Start Date vlocity_cmt__SellingStartDate__c: defines when the

commercial product can be ordered and sold.
● Selling End Date vlocity_cmt__SellingEndDate__c: defines when the

commercial product can no longer be ordered. Changes to existing assets are
supported after the end of selling and before it is retired.
● Fulfilment Start Date vlocity_cmt__FulfilmentStartDate__c: defines

when the commercial product is ready to be fulfilled. By default, this is the same as
the selling start date but can be a future date.

Exercise Guide
● End Of Life Date vlocity_cmt__EndOfLifeDate__c: is the date on which the

commercial product is no longer supported.
NOTE:
The product selling period fields have a Data Type of Date/Time and are
intended for commercial products only. Technical products and promotions
do not use these fields and should use the existing effectivity and date fields.
Assets do not use these fields.
You set the product selling period date fields in the Vlocity Product Console in the General
Properties facet of the product.

Exercise Guide
Here you are looking at the effectivity dates of the Apple iPhone X.

Exercise Guide
Infiwave started selling the iPhone X on the Selling Start Date: October 1st 2017.
However, these were pre-orders, as the iPhone X wasn’t actually released by Apple until
November 3rd, 2017.
The Fulfilment Start Date is the date you can provide your customers with the iPhones.
You will stop selling the iPhone X to customers on the Selling End Date: December 1st
2024.
This is a year before Apple stops supporting the iPhone X, on December 1st 2025, by which
time you will also no longer be supporting it. This date is known as the End of Life Date.
The Vlocity Product Console validates all dates and times entered using the below rule and
will not allow you to save products until the dates are set correctly:
SellingStartDate<=FulfilmentStartDate<=SellingEndDate<=EndOfLifeDate
ALERT:
Product selling period data is stored in the platform cache. After you make
changes to product selling period fields, you must update the product
hierarchy data in the platform cache by running Product Hierarchy
Maintenance, Clear Managed Platform Cache, and Refresh Platform Cache in
this sequence.

Exercise Guide
Task 1: Review product selling periods on a product
1. You should be on the Dashboard of the Vlocity Product Console.
2. Under Product Management, click the search icon next to Product.
3. In the Search Product… entry dialog, enter Offer and click the search icon . The
list of products is returned.
4. Click on the Mobile Data Plan Offer.
5. Notice the Selling Start/End Date, Fulfilment Start Date and End of Life Dates are not
populated. This implies that the product will be available forever.

Exercise Guide
6. Click on the Product Structure facet. This shows all the child products that together
make up the Mobile Data Plan Offer.

Exercise Guide
7. Click on the 4G Data Plan link and notice the Effectivity dates for the 4G Data Plan
product.

Exercise Guide
8. Click on the Mobile Data Plan Offer tab to return to the product. Notice the selling
period dates for each product in the bundle.
NOTE:
When a product is used in bundles, it is the responsibility of the product
administrator to ensure the selling periods are consistent.

Exercise Guide
Task 2: Use the Find References button
Product administrators use the Find References button to find references to a given product
in active promotions, product bundles, assets, quote line items, order line items and
opportunity line items. The button helps administrators determine the effect of changing
product selling period and end of life dates.
1. Return to the open 4G Data Plan tab on the Dashboard. If you closed it, click on the
4G Data Plan link from the Mobile Data Plan Offer Product Structure.
2. On the General Properties facet, click the Find References button at the bottom of
the page.
3. The Partial List of Active References dialog box displays. Notice the types of
reference objects.
4. Click the > symbol to expand the Opportunity Item References, Asset Item
References, and Bundled Product References. The 4G Data Plan is an opportunity
item and asset on Carole White’s account. It’s also part of a bundled product for the
Mobile Data Plan Offer.

Exercise Guide
5. Click Close.
NOTE:
The default number of rows returned for each reference object is 20, but the
limit can be increased by setting the FindReferencesRowCountLimit
custom setting in the CPQ Configuration Setup in the Vlocity CMT
Administration dashboard. The maximum number of rows returned is 1000.
ALERT:
In order to find order, quote and opportunity line item references, each line
item's fulfilment status (vlocity_cmt__FulfilmentStatus__c) must be
set to Draft, In Progress, PONR, or Pending.
In order to find asset references, the asset's provisioning status
(vlocity_cmt__ProvisioningStatus__c) must be set to Active,
Changed or Deleted. These values are normally set by order management
processes. If the statuses have null or other values, the references will not
display.

Exercise Guide
Task 3: Review product selling periods in the Cart
1. In the Lightning Navigation Bar, click Orders.
2. On the Orders page, change the Recently Viewed list view to All Orders.
3. Select Carole White’s New Mobile Plan Order.
4. Click on the Power Launcher’s search field (just below the Order header) and select
Configure Order. This invokes the Cart.

Exercise Guide
5. Click the > symbol to expand the Mobile Data Plan Offer in the Cart.
6. Hover over the green clock icon for the 5G Data Plan product. Notice the selling
period start date.
7. Hover over the yellow clock icon for the 4G Data Plan product. Notice the selling
period end date.

Exercise Guide
8. Hover over the red clock icon for the 3G Data Plan product. Notice the end of life
date.
9. Notice the 4G LTE Data Plan product does not have a colored clock icon, this is a
current product.
NOTE:
To support MACD and asset-based ordering, the Cart can display current,
future, past and retired products based on the Order (or Quote or
Opportunity) Start Date.
● Current and future products display in the Cart normally, but future
products are indicated with a green clock icon.
● Past products are products that have passed their Selling End Date but
have not passed their End of Life date. They are indicated by a yellow
clock icon. They cannot be added to the Cart or configured for new
orders, but they can be configured or deleted during MACD or
asset-based ordering.
● Retired products are products that have passed their end of life date
and they are indicated by a red clock icon. In a new order, they cannot
be added to the Cart or configured but during MACD or asset-based
ordering they can be deleted.
10. Locate the 5G Data Plan in the Products list to the left of the Cart and hover over
the green clock icon.
Similar to the products added to the Cart, the product list also displays current and
future products based on the Order Start Date.

Exercise Guide
ALERT:
Product selling period functionality does not override other standard controls
for displaying products in the Products list. In order to display, products must
be marked Orderable, Active and have a price list entry. The price list entry
Effective From date must be current as well.
● Products that have reached the end of their selling period or are at
their end of life date will not display in the product list and can’t be
added to the Cart.
● You can add a future dated product to the Cart and submit the order
normally, however Future Dated Ordering functionality must be
implemented in order to manage the fulfilment of future products.

Exercise Guide
Exercise 3-5: Creating Products

Scenario
Devi can’t wait! It’s time to enter his new products into the shared catalog. All of his careful
planning and product modeling work now pays off!
Goal
● Create product specifications
● Set and override product attribute metadata
● Assign attributes and fields to products
● Add product images
● Add a base price
● Understand product layout management
Tasks
1. Create a product specification for the Apple Watch Series 5
2. Set design-time attribute metadata values for the product
3. Set run-time attribute metadata values for the product
4. Add a product image as an attachment
5. Add a base price to the product
6. Review Layout Management and Debug facets
Time: 30 mins

Exercise Guide
Task 1: Create a product specification for the Apple Watch Series 5

1. In the Lightning Navigation Bar, click the Vlocity Product Console.
2. Under Product Management next to Product, click the new icon . This will
launch the New Product dialog.
NOTE:
We have configured your training playground to simplify the New Product
dialog. This configuration can be implemented in your organization’s orgs, if
desired, by modifying the Product2 object layout.
3. In the New Product dialog, enter the following information.

Field Value Notes
Object Type SmartWatch Recommend (but not require) that all products
Product Spec are created with an object type in order to
benefit from the powerful inheritance
architecture.
Name Apple Watch This value will be visible and searchable at

Series 5 run-time in the Cart.
Specification Product Specification Type is aligned with the four SID

Type layers of Offer, Product, Service and Resource.
Although it is possible to configure this picklist,
it’s not recommended to change these picklist
values because future functionality will be
designed to utilize them.
Product Code C-WAT-005 This value will be visible at run-time in the

Product Details window of the Cart.
4. Click Save to continue.

Exercise Guide
5. Now you can complete the rest of the General Properties for the Apple Watch Series
5, using the information shown below.
Field Value Notes
Product Monitor your This value will be visible at run-time in the

Description heart rate, noise Product Details window of the Cart, and
levels and
searchable in the Search dialog.
fitness goals
with the Apple Notice the expand icon which allows
Watch Series 5. you to increase the size of the entry
And do it all dialog.
while leaving
your phone
behind!
Product Family [leave blank] The product family is the group of

products to which this specification
belongs. You are not going to use product
families in this exercise, so leave this
blank.
Status Active This value is not used in any current

functionality, but it will be! Recommend
setting this value in anticipation of future
functionality.
Orderable ✓ The Orderable flag must be set for a

product to be visible in the Cart’s product
list.

Exercise Guide
Non [leave blank] It may be that this product is something

Assetizable that you do not want displayed in the
customer’s asset list. This could include,
for example, a promotional t-shirt that is
given to each new customer who places
an order. In this case, you would check
the Non Assetizable flag.
Type [None] This is a customer-defined field that you

can use to classify products. We are not
using this so leave the default value None
as is.
Sub Type [None] Together with the Type field (above) you
can select a sub-type to help classify your
product. We are not using this so leave the
default value None as is.
Help Text [leave blank] Here you can enter helpful information
related to the product that displays at
runtime when the user hovers over the i
icon.
Active ✓ The Active flag must be set for a product

to be visible in the Cart.
Selling Start [today’s date] This date defines when a commercial

Date product can be ordered and sold.
Fulfilment [today’s date] This date defines when a commercial

Start Date product is ready to be fulfilled. By default,
this is the same as the selling date, but
can be a future date to support
pre-orders.

Exercise Guide
6. Click Save, and a green saved! message will display.

Exercise Guide
Task 2: Set design-time attribute metadata values for the product

1. Click the Attribute Properties facet.
2. Notice the Band Type and Connectivity attributes that we added to this facet in the
last exercise.
3. Under Design Time Attributes, click the Details link next to Brand to open the
Attribute Metadata window.

Exercise Guide
NOTE:
Using the Attribute Metadata window, you can set overridable attribute
metadata behaviors that control whether the attribute value is active, editable
or required as well as default values. In addition, you can override the
attribute data type and picklist that has been inherited from the object type.
Notice the non-overridable behaviors inherited from the product object type
that are not editable.
4. In the Attribute Metadata window, enter the following information.

Field Value Notes
Value Apple This will set Apple as the value for this attribute.
Read Only ✓ This will cause this attribute to be not editable.

Exercise Guide
ALERT:
When making changes to attribute metadata, be sure to click Save in the
Attribute Metadata window and not the Attribute Properties facet. Otherwise,
your metadata changes will not save!
6. Notice that the Brand attribute value is now set to Apple.
7. Under Design Time Attributes, click the Details link next to Size to open the
Attribute Metadata window.
8. Notice that this is a Text attribute with no picklist defined.

Exercise Guide
9. In the Attribute Metadata window, enter the following information.

Field Value
Value 38mm
Read Only ✓
11. Using the steps above, enter the following metadata information for the Capacity
attribute.
Field Value
Value 8 GB
Read Only ✓
12. Enter the following metadata information for the Mobile OS attribute.
Field Value
Value watchOS 4
Read Only ✓

Exercise Guide
Now you will override an attribute picklist that has been inherited from the object type.

Exercise Guide
Task 3: Set run-time attribute metadata values for the product

1. Under Run Time Attributes, click the Details link next to Color to open the Attribute
Metadata window.
2. In the Attribute Metadata window under DATA INFO, click the delete icon next
to the Colors picklist.
3. Using the Picklist Lookup dialog, select the Band Color picklist you made earlier.

Exercise Guide

Exercise Guide
5. Hover over the Color attribute and notice how the cursor turns to a no-go icon. This
indicates that the attribute is not available for editing during design-time because it
is run-time configurable only. It also has a red asterisk next to it indicating that it is
required. These metadata attributes were assigned at the product object type in the
previous exercise.
6. Using the steps you’ve learned, enter the following metadata information for the
Payment Type attribute. Click Save.
Field Value
Value Pay in Full
Read Only ✓
7. Click the Attributes and Fields facet.
8. Click the Assign Attributes/Fields button.

Exercise Guide
9. Notice the list of attributes (and fields) that can be assigned directly to the product.
ALERT:
When you assign attributes and fields directly to a product, you “break” the
dynamic attribute inheritance from the object type, and all subsequent
attribute assignment changes must continue to be directly managed at the
product level.
10. Click the X to close the Assign Attributes and Fields window on the right without
saving.

Exercise Guide
Task 4: Add a product image as an attachment

1. Click the Attachments facet.
2. Click New Attachment.
3. In the General Properties window, enter the following information.

Field Value Notes
Name Apple Watch Series 5 Image This value is only visible at

1 design-time in the
Attachments facet of the
Console.
Description Image of two watches This value is only visible at

design-time in the
Attachments facet of the
Console.
Content Type Image
Url https://www.salesforce.com
/content/dam/web/en_us/www
/images/resources/training
-images/AppleWatch.png
Default Image ✓ If the default flag is

checked, the image will
display as the default
image in the Product
Details window in the Cart.
Sequence 10 The sequence value is used

to order multiple images in
the Gallery in the Product
Details window in the Cart.

Exercise Guide
NOTE:
EPC does not have the capability to upload files, therefore it only supports
product images via an absolute URL.
4. In the Attachment General Properties window, click Save.
5. In the attachment list, click the view icon to display the new attachment.
6. Click OK to close the image viewer.

Exercise Guide
Task 5: Add a base price to the product
NOTE:
In this task, you will add a simple base price to your new product, so that the
product will display in the Cart.
1. Click the Pricing facet.
2. Within the CHARGES tab, click New.
3. In the PRICE LIST ENTRY General Properties dialog, enter the following information.
Field Value Notes
Price List B2C Price List This indicates the price list which will be used
to provide the pricing for the product.
Display Text $349.99 This is the price displayed to the end user.
Base Price ✓ Selecting this option means the base price will
be displayed along with the product in the
Products list of the Cart.
4. In PRICE LIST ENTRY Pricing Variable section, enter the following information.
Field Value Notes
Charge Type One-time This is a one-time purchase charge for the

customer.
Sub-Type Standard Select the standard charge rather than a fee.
5. Just below the Sub-Type, click Search.
6. Beneath Select a Pricing Variable, click One Time Std Price.
7. In the Pricing Element section, click $349.99 OT.

Exercise Guide
8. In the PRICE LIST ENTRY Effectivity dialog, enter the following information.
Field Value
Active ✓
9. Click Save.

Exercise Guide
10. In the left sidebar, click the Context Rules facet. This is where you can create context
rule sets for a product.
NOTE:
For more information on Context Rules, see the Context Rules training
module.

Exercise Guide
Task 6: Review Layout Management and Debug facets

1. Click the Layout Management facet.
2. Notice the Create Custom Layout button.
ALERT:
When you click the Create Custom Layout button, the Vlocity Product
Console will perform a “deep copy” of the object type layout and then “break”
the link to the object type’s layout. All subsequent layout changes must be
directly managed at the product level.
3. Click the Debug facet.
4. Notice the JSONAttribute field. This is the field on the product object that stores the
attribute metadata.
5. Click the Reload icon in the upper right corner to refresh the page and
product data.

Exercise Guide
6. Click the Debug facet.
7. Notice that the JSONAttribute field now displays the attribute metadata that you
created earlier in this exercise.
ALERT:
Do not directly edit the JSONAttribute field, no matter how much you love
writing in JSON notation! This data is intended for debugging purposes only.

Exercise Guide
Exercise 3-6: Creating Product Bundles

Scenario
Devi has just learned from the marketing department that they’ve introduced a whole slew
of product bundles, and the first one they want includes the new Apple Watch Series 5
product. Of course, they did it yesterday, and are wondering when he’ll have the new
bundles available to their sales and service teams—with a not-so-subtle hint that there’s no
time like the present. Devi is excited to release his new smartwatch product specification
into the wild, so he creates a product bundle for it.
Goal
● Create product bundles
● Explain product cardinality
● Override the cardinality of child product bundles
Tasks
1. Create a product bundle
2. Create the structure of the product bundle
3. Override the cardinality of the child product bundle
4. Create a price list entry for the product bundle
Time: 15 mins

Exercise Guide
What is a product bundle?
A product bundle is a set of products sold together. Products are bundled using a “Has-A”
Containment relationship as either a child or a realization. A product can have one or more
product child items (or PCIs), and you can define cardinalities for each. PCIs can be a single
product or a product bundle, which allows you to create product bundles within product
bundles.
What is product cardinality?
Product cardinality defines the default, minimum and maximum quantities of the product
that are allowed in the product bundle. You can also override the cardinalities of product
bundles when they are included within another product bundle.

Exercise Guide
Task 1: Create a product bundle
1. In the Console’s tab navigation bar, click Dashboard.
2. Under Product Management next to Product, click the new icon . This will
launch the New Product dialog.
3. In the New Product dialog, enter the following information. We will create this
product bundle as an offer.
Field Value
Object Type BASE Offer Spec Type
Name Get Smart iPhone + Watch Bundle

Offer
Specification Type Offer
Product Code C-OFF-004
4. Click Save, and a green Product created! message will display.
5. Now you can complete the rest of the General Properties using the information
shown below and click Save.
Field Value
Product Description Get smart with the best phone and

watch bundle ever created!
Status Active
Orderable ✓
Active ✓
Selling Start Date [today’s date]
Fulfilment Start Date [today’s date]

Exercise Guide
Task 2: Create the structure of the product bundle
1. Click the Product Structure facet.
2. Click the Add icon to add a product child item (PCI) to the product bundle.
3. In the product child item window on the right, enter the following GENERAL
PROPERTIES information.
Field Value Notes
Child Product Apple iPhone X Use the lookup dialog to select the
child product.
Relationship Type Child Realization relationships are reserved

for future functionality.
Sequence 10 This value determines the order the

child products will display in the
bundle. Use a sequence such as 10,
20, 30 to ensure additions can be
easily inserted.

Exercise Guide
4. In the product child item window on the right, enter the following CARDINALITY
information.
Field Value Notes
Min Quantity 1 This value determines the minimum quantity

required for a valid order.
Default Quantity 1 This value determines the default number of child

products that will be included in the bundle when it
is added to the Cart.
Max Quantity 2 This value determines the maximum quantity

required for a valid order.
NOTE:
The Virtual Item flag, when checked, makes the product item not assetizable.
This is customarily used as a grouping mechanism, and to set cardinality for
the parent product nodes.
The Collapse Hierarchy flag, when checked, enables a Search Item dialog in
the Cart’s line items pane, allowing users to search items within the bundle
and then add additional products to the bundle. This is intended for use with
very large product bundles.

Exercise Guide
5. Click Save.
NOTE:
Product Child Items can be added to any product in the bundle, not just the
current parent product.
6. Click the Add icon next to the Get Smart iPhone + Watch Bundle Offer.

Exercise Guide
7. Using the steps learned above, add the following child products to the bundle with
the cardinalities defined below.
Relationship Collapse
Product Type Sequence Min Default Max Hierarchy
Apple Watch Series 5 Child 20 1 1 2
NumberSync Child 30 0 0 1
Individual Simple Child 40 1 1 1 ✓

Choice Plan

Exercise Guide
Task 3: Override the cardinality of the child product bundle
1. In the Product Structure window, expand the Individual Simple Choice Plan
product bundle by clicking the toggle arrow > to its left. Click in the white space of
the line for the 4G LTE Data Plan. Do NOT click the product name link because that
will navigate you to the product record.
2. The product child item window will display on the right. Notice the existing
CARDINALITY settings that were set when the 4G LTE Data Plan product was added
to the Individual Simple Choice Plan product bundle.
3. Click Override Mode.
4. Click Create Override.
NOTE:
Cardinality overrides must be equal or greater than the minimum limit set by
the original cardinality. For example, if the minimum original quantity is 2, you
cannot create a minimum override quantity of 1; the override must be greater
than or equal to 2.
5. In the CARDINALITY section, change the following values.

Product Min Max
4G LTE Data Plan 1 2

Exercise Guide
This override will change the minimum quantity to 1 and the maximum quantity to 2 only
when it is bundled in the Get Smart iPhone + Watch Bundle Offer.
6. Click Save.
7. Now you want to exclude Netflix from the bundle altogether. Click in the white
space of the line for Netflix to view the association details. Do NOT click the product
name link because that will navigate you to the product record.
8. Click Override Mode.

Exercise Guide
9. Click Create Override.
10. Set the minimum, maximum and default cardinalities for the Netflix product within
the Get Smart iPhone + Watch Bundle offer to 0.
Product Min Max Default
Netflix 0 0 0
This override will exclude the Netflix product from the Individual Simple Choice Plan
bundle only when it is bundled in the Get Smart iPhone + Watch Bundle Offer.
11. Click Save at the bottom of the pane.

Exercise Guide
NOTE:
You may have noticed the Exclude Item button when you switched into
override mode. Unfortunately, although this works beautifully when excluding
items from bundles for new orders, you may run into difficulties when it
comes to updating existing orders. Instead, we suggest you play it safe by
adding an override to set the minimum, maximum and default cardinality to 0
when you want to exclude an item, as you have done in the example above.
12. In the upper right corner, click the refresh icon .
13. In the left sidebar, click the Product Structure facet.
14. In the product structure window, expand the Individual Simple Choice Plan
product bundle.
15. Notice the cardinality override notations.

Exercise Guide
Task 4: Create a price list entry for the product bundle
NOTE:
As discussed earlier, a bundle must have a price list entry for it to be available
to customers. However, in your exercise, the bundle price is the sum of all the
product child items’ prices. Therefore, you need to add a price list entry for $0
to your new product bundle, so that it will roll up prices for the product child
items when it’s displayed in the Cart.
1. Click the Pricing facet.
2. Click New.
3. In the PRICE LIST ENTRY General Properties dialog, enter the following information.
Field Value
Price List B2C Price List
Display Text Bundle pricing
Base Price ✓
4. In the PRICE LIST ENTRY Pricing Variable dialog, enter the following information.
Field Value
Charge Type One-time
Sub-Type Standard
5. Just below the Sub-Type, click Search.
6. Beneath Select a Pricing Variable, click One Time Std Price.
7. In the Pricing Element section, click FREE.

Exercise Guide
8. In the PRICE LIST ENTRY Effectivity dialog, enter the following information.
Field Value
Active ✓
9. Click Save.

Exercise Guide
Exercise 3-7: Managing the Shared Catalog

Scenario
Devi has been busy creating picklists, product attributes, object types, and products and
product bundles. Devi is quickly realizing he needs to understand the housekeeping tasks of
managing the shared catalog to keep everything running smoothly and quickly!
Goal
● Specify what the Salesforce Industries batch jobs do, when to run them and why
● Describe how the platform cache is used and when you need to refresh it
● Explain why and when you need to calibrate product attributes
Tasks
1. Refresh the product hierarchy cache
2. Confirm that batch jobs completed successfully
Time: 20 mins

Exercise Guide
What does it mean to manage the Shared Catalog?

Enterprise product catalogs always require administration and management. In the case of
EPC’s shared catalog, there are several tasks that must be completed when you are creating
or updating elements in the Catalog. These tasks are designed to ensure top performance
and faster speeds at run-time.
Salesforce Industries have created several administrative jobs to help you complete these
tasks. The jobs primarily do three things:
Transform catalog entities into flattened or streamlined records that are

easier and faster to read and load.
Cache catalog data into memory rather than having to request data from
the database.
Regenerate metadata that is critical for Industries CPQ operations.
When changes are made to the shared catalog, you need to determine when to run each
job. Some jobs can be run without affecting live production environments, but others, such
as the Clear Managed Platform Cache and Refresh Managed Platform Cache must be run
during downtimes or low usage. If you run the Product Hierarchy Maintenance or Refresh
Platform Cache jobs while people are using CPQ, the maintenance jobs can disturb the CPQ
APIs. This means that CPQ may produce incorrect data whilst the maintenance jobs are in
progress. From the Fall ‘20 release onwards, there is a Delete Old Data checkbox beneath
the Product Hierarchy Maintenance option, which allows you to clear old data, or keep it. If
you choose to keep it, the APIs will run off the old data until the new data is in place, so
there is no downtime whilst the batch jobs are running. These jobs do not impact Industries
Order Management order decomposition or order orchestration, and will not affect
decomposition or orchestration that is happening as the jobs are run. In this lesson, you will
learn about the most common administrative jobs used in managing the shared catalog
and when you should use them.

Exercise Guide
Understanding Caching in Your Industry Cloud
Caching of data is primarily a performance optimization technique for situations where the
same data will be required across multiple transactions. Rather than recalculating or
re-retrieving the information, data can be stored in an easy-to-access place and reused in
later transactions.
Industries CPQ primarily caches data in a Salesforce platform cache called the
“CPQPartition.” The CPQPartition is created when your Salesforce Industries Cloud is
installed, but you will need to enable it and ensure that it has enough space allocated. You
can allocate a minimum of 10 MB for the platform cache or a maximum of whatever is your
Salesforce platform cache limit.
RESOURCE:
For more information on Salesforce platform caches, please see the following
Salesforce Trailhead:
https://trailhead.salesforce.com/modules/platform_cache/units/platform_ca
che_get_started
The CPQPartition, just like all platform caches, is made up of a session cache and an org
cache.
The session cache, as the name implies, is cache space for an individual user session. The
session cache is currently not used.
Besides caching within each user session, you also need to cache items for use by any user
across the application. In the CPQPartition, the org cache performs this function by storing
product hierarchy properties (JSON key-value pairs), rules, and line item properties for your
entire organization. For example, when a user creates a product bundle containing child
products, the org caches the product hierarchy. So, when any user adds the product bundle
to the Cart, the Cart actually retrieves the product hierarchy data from the cache.

Exercise Guide
In addition to the CPQPartition platform cache, there are other caches used in the
Communications, Media, and Energy & Utilities Clouds, such as the Digital Commerce API
Caching. To learn more about the Digital Commerce solution, please refer to your
documentation or the Digital Commerce training course.
The graphic provides a visual of Industries CPQ operations and when those transactions are
reflected in the org cache.
Managing the Platform Cache

When you need to initialize or refresh the platform cache, you use a three-step process.
1. Run the Product Hierarchy Maintenance job.
2. Run the Clear Managed Platform Cache job.
3. Run the Refresh Platform Cache job.

Exercise Guide
To access these jobs, go to the Vlocity CMT Administration tab then, under Admin Console,
select Maintenance Jobs.
The Product Hierarchy Maintenance, Clear Managed Platform Cache and Refresh Platform
Cache jobs are the bottom three jobs on the Maintenance Jobs list.

Exercise Guide
The Product Hierarchy Maintenance job builds a streamlined version of the product
hierarchies in the data store sObject. Separately but related, Refresh Platform Cache invokes
an Apex job that uses the product hierarchy data from the data store to build a cached
version of the product hierarchy using key-value pairs.
Check the Delete Old Data option in the Product Hierarchy Maintenance job if you want to
delete the older, inactive dataset. This saves storage space as only the new, rebuilt dataset is
available. However, this option should be used with caution. If you run the Product
Hierarchy Maintenance or Refresh Platform Cache jobs while people are using CPQ, the
maintenance jobs can disturb the CPQ APIs. This means that CPQ may produce incorrect
data whilst the maintenance jobs are in progress. If you choose to keep the old data, by
leaving the Delete Old Data checkbox unchecked, the APIs will run off the old data until the

Exercise Guide
new data is in place, so there is no downtime whilst the batch jobs are running.
Ok, so what does all that mean? Let’s take a look at when you would run these jobs.
Any time you make changes to product bundles (such as product cardinality), you must
rebuild the product hierarchy data store and cache, which means you must run the Product
Hierarchy Maintenance job, followed by the Clear Managed Platform Cache job and the
Refresh Platform Cache job. Otherwise, you will not see your cardinality changes applied at
run-time in the Cart.
You probably noticed the Clear Managed Platform Cache job that sits between the Product
Hierarchy Maintenance and Refresh Platform Cache. The Clear Managed Platform Cache
job deletes all data in the org cache in the platform cache. This creates a “fresh slate” for the

Exercise Guide
Refresh Platform Cache job to deliver its revised product hierarchy data to the org cache.
Pricing plan steps and their parameters, in addition to context and advanced rules data, will
be repopulated when pricing and rules are invoked at run-time.
When making changes to a rule or pricing plan step, it’s not necessary to run the Product
Hierarchy Maintenance job. Why? Simple, you don’t need to rebuild the product hierarchy
data store.
NOTE:
When you run the Clear Managed Platform Cache job, all product hierarchy,
pricing plan steps and rules data will be deleted from the org cache, which
may affect run-time performance, so it’s recommended that these jobs be run
during times of low usage or system downtime.

Exercise Guide
What other jobs should be run?

Another job that is frequently used to manage the shared catalog is
EPCProductAttribJSONBatchJob, which is used to calibrate product attributes. We did this
for you when we created your training playground.
Your training playground is a copy of our master TSO (Trial Source Org), and it contains
products and product attributes that have been seeded in support of the lab exercises. Each
product’s attributes are stored in JSON format in a field called JSONAttribute. The
JSONAttribute field contains attribute record ids, which allow faster direct access for system
processes.
However, when we create new orgs from our master TSO, the Salesforce copy process is
unable to detect those record ids embedded in the JSONAttribute field, and so they remain
coded as the original attribute record ids from the TSO. Left as it is, this will create errors in
other attribute processes.
You can see a sample JSONAttribute field in the screenshot with the record ids highlighted
in yellow.

Exercise Guide
Salesforce Industries Communications, Media, and Energy & Utilities Clouds developed an
Apex batch job called EPCProductAttribJSONBatchJob to reprocess these product attributes
and save the JSONAttribute field with your new org’s attribute record ids.
NOTE:
For convenience, from the Attributes tab within the CME Admin app we built a
Process Attributes button in your training playground to invoke the batch job,
otherwise, you would run this job from the Developer Console.
ALERT:
Never edit your product attributes through this interface. You manage them
through the Vlocity Product Console, as you saw earlier in this module.
NOTE:
If your org contains migrated product attribute overrides from promotions,
you must also run EPCFixCompiledAttributeOverrideBatchJob to correct the
attribute record ids. This training playground does not contain attribute
overrides, so you do not need to run it.
Let’s take this concept outside of a controlled training scenario and put this concept to work
in the real world. Any time you spin an org or import data that contains product attributes,
such as creating a sandbox environment, you must correct the product attribute record ids.

Exercise Guide
Do all these words have your head spinning and seem like mumbo jumbo? The graphic
below provides a visual representation of when to run this Apex job and the update that
occurs in the JSONAttribute field.
NOTE:
This job also can be helpful when troubleshooting product attribute issues. For
example, an updated attribute or value that is not displaying at run-time. Run
this job to reprocess the product attributes saved to the JSONAttribute field.
Once the job completes, the updated attribute or value will display in the
JSONAttribute field and at run-time.

Exercise Guide
Task 1: Refresh the product hierarchy cache

Now that Devi has an understanding of how to manage the shared catalog, he needs to put
what he’s learned into action.
In the previous exercise Devi created a product bundle and made a change to the cardinality
of that bundle. So, the product hierarchy data in the platform cache must be updated, or the
new product bundle will not display properly in the Cart.
1. Build the product hierarchy data store by running the Product Hierarchy
Maintenance job.
a. In the Lightning Navigation Bar, click More, and then select Vlocity CMT
Administration.
b. Under Admin Console, click Maintenance Jobs.
c. On the Maintenance Jobs page, find the PRODUCT HIERARCHY

MAINTENANCE job and click Start.
d. Click OK to accept the notification that the job may affect your org settings
and items.
e. Messages display indicating that the job completed successfully.

Exercise Guide
NOTE:
A successful job completion report will also be emailed to the email address
registered for your training playground.
2. Clear the platform cache.
a. On the Maintenance Jobs page, find the CLEAR MANAGED PLATFORM

CACHE job, and click Start.
b. Click OK to accept the notification that the job may affect your org settings
and items.
c. A message displays that the job completed successfully.

Exercise Guide
3. Populate the platform cache.
a. On the Maintenance Jobs page, find the REFRESH PLATFORM CACHE job,
and click Start.
b. Click OK to accept the notification that the job may affect your org settings
and items.
c. You will see messages indicating that the job completed successfully.

Exercise Guide
Task 2: Confirm that batch jobs completed successfully
1. Click on the Salesforce Setup icon in the top right of your screen to open
Salesforce Setup.
2. In the Quick Find box on the left, type Apex Jobs.
3. In Environments under Jobs, click Apex Jobs.
4. In the list of Apex jobs, notice the listings for the following batch jobs. You can see
the most recent listings by looking at the Submitted Date, which shows you the jobs
that were run. Ensure that the job status shows no errors. The rest of the listings were
copied from the master training org.

Exercise Guide
Batch Job Purpose
ResolveProductHierarchyBatchJob Copies product data to the data store sObject.

Is invoked using the Product Hierarchy
Maintenance job and should be run before
Refresh Platform Cache job.
DeleteProdHierDataStoreRecords This is run as part of the Product Hierarchy

BatchJob Maintenance job if you select the Delete Old
Data flag. It clears the duplicated product
data created as part of the
ResolveProductHierarchyBatchJob.
ProductHierarchyBatchProcessor Copies the data store sObject and builds the

product hierarchy and product selling data in
the platform org cache. Is invoked using the
Refresh Platform Cache.
The Refresh Platform Cache job should be run
after the Product Hierarchy Maintenance job.
DeleteSObjectBatchProcessor Invoked as part of the Refresh Platform Cache

job, this purges the Platform Cache.
ProductAttributesBatchProcessor Copies the filterable product attributes to the

Cached Filterable Attribute sObject used by
the Cart. Is invoked using the Refresh Platform
Cache job.
EPCProductAttribJSONBatchJob Regenerates product attribute fields for data

that has been migrated from an external
source or another org.

Exercise Guide
NOTE:
The EPCProductAttribJSONBatchJob should be run as needed for these

situations:
1. Attributes are not displayed as expected in Industries CPQ.

2. Data has been imported to EPC from an external source.
3. The JSON values displayed for an attribute are incorrect.
By default, the batch job runs for all product attributes, but can be amended
to run for a specific subset of data. Refer to your documentation for details.
ALERT:
If the ProductAttributesBatchProcessor displays an
INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY error, the
EPCProductAttribJSONBatchJob did not run successfully. Rerun this job by
navigating to Lightning App Launcher--> Vlocity Attributes-->List View
All-->Process Attributes --> Start Processing.

Exercise Guide
5. In the Quick Find box, type Platform Cache.
6. Under Custom Code, click Platform Cache.
7. Click Recalculate.

Exercise Guide
8. In the Platform Cache Partition page, under Name, click CPQPartition.

Exercise Guide
9. Notice that your org cache is now populated.

Exercise Guide
ALERT:
The Clear Cache button shown in this screen will delete the contents of the
CPQPartition cache. There is also a CLEAR MANAGED PLATFORM CACHE
button accessible from the Vlocity CMT Administration Maintenance Jobs
screen that performs the same function. However, neither of these buttons
rebuilds the cache. The cache should never be cleared while orders are being
created.

Exercise Guide
Exercise 3-8: Test the New Products in the Cart

Scenario
Devi has a new swagger in his step. With his new product specification and product bundle
added to the product catalog, he’s ready to check them out in the bright lights of the Cart.
Goal
● Understand how product bundles display in the Cart
● Understand how product cardinalities are used in the Cart
Tasks
1. Review the new product and product bundle in the Cart’s product list
2. Add the product bundle to the Cart and test the cardinalities
Time: 15 mins

Exercise Guide
Task 1: Review the new product and product bundle in the Cart’s
product list
1. In the Lightning Navigation Bar, click Orders.
2. Click New.

Field Value
Order Name New Product Test Order
Account Name White, Carole
Order Start Date [today’s date]
Price List B2C Price List
4. Click Save.
5. From the Power Launcher, click Configure Order. This invokes the Cart.
6. In the search dialog, enter apple watch.
7. In the product list pane, find the Apple Watch Series 5 product, and click More to
invoke the Product Details modal window.

Exercise Guide
8. Review the product image.
9. Click Close.

Exercise Guide
Task 2: Add the product bundle to the Cart and test the cardinalities
1. In the search dialog, enter get smart.
2. In the product list pane, find the Get Smart iPhone + Watch Bundle Offer product,
and click Add to Cart.
3. Click the red Messages notification.
4. Click any of the Take Me There “eye” icons on the right side of Messages.
5. In the Line Item Details modal window, click the Color attribute for the Apple
iPhone X.
6. Notice the two iPhone X colors from the standard color picklist. Select one.
7. In the Line Item Details modal window, click the Color attribute for the Apple
Watch Series 5.

Exercise Guide
8. Notice the standard color picklist has been overridden by the Band Color picklist.
Select one.
9. Scroll down and set the Wearables Band Type and Connectivity to any values from
their picklists.
10. Scroll down and set the Mobile Plans – Data Plans attribute to Unlimited.
11. Notice the design-time attributes such as the Mobile OS and Capacity of the watch
that are read-only.
12. Click Close.
13. Back in the Cart, notice the Recurring Total and One Time Total prices for the Get
Smart iPhone + Watch Bundle Offer. Pricing from the product child items has been
rolled up into these totals, while the Recurring Charge and One Time Charge prices
for the parent product remain $0.

Exercise Guide
14. In the Apple iPhone X line item, click into the Total Quantity field and type 0.
Notice the error message resulting from the minimum quantity set in the product
cardinality.
15. Set the quantity for the Apple iPhone X to 5. Notice the error message resulting
from the maximum quantity set in the product cardinality.
16. Set the quantity for the Apple iPhone X to 2.

Exercise Guide
17. Notice the Add to Cart button for the NumberSync line item. This is because the
default quantity set for this product child item was 0.
18. Under the Individual Simple Choice Plan product bundle, notice the Search Item
dialog. This dialog was included because the Collapse Hierarchy flag was checked.
Notice also that the Netflix product is excluded from the bundle.
19. Click in the Search Item dialog, and type data. Notice that you can search for
products within the product bundle, which is helpful for very large and complex
product bundles.

Exercise Guide
Exercise 3-9: Create Tablet Products Challenge

Scenario
Infiwave has been so focused on introducing new products for mobile devices and data
plans they realized they are missing out on the tablet market. In an effort to increase
revenue and attract additional customers, marketing reached out to Devi, once again, to
create the products to address the need for tablets and their accessories in EPC based on
the requirements below.
Goal
● Challenge exercises solidify what you learned in the exercises, build your skills, and
allow you to make mistakes -- which is how you will master this application
Tasks
1. Review product requirements
2. Build products in EPC
3. Test new products in the Cart
Time: 45 mins

Exercise Guide
Task 1: Review product requirements
Marketing Requirements - Tablet
Product Apple iPad Pro 12.9”
Product Code C-TAB-001
Object Type Tablet Product Spec
It’s all new, all screen, and all powerful.

Completely redesigned and packed with our
Product Description
most advanced technology, it will make you
rethink what iPad is capable of.
Effectivity Sellable and fulfillable immediately
64GB
256GB
Product Capacities
512GB
1TB
Silver
Product Colors
Space Gray
Wifi
Product Connectivity
Wifi + Cellular
Product Pricing $1149
Configurable at design Apple = Brand

Behavior Read-only
Color
Configurable in the cart and
Capacity
required
Connectivity

Exercise Guide
NOTE:
For this challenge, assume pricing is the same for all capacities, connectivity
and price lists. Want to challenge your pricing skills further? Consider using
Attribute-Based Pricing.
Marketing Requirements – Styluses
Product Apple Pencil
Product Code C-ACC-001
Object Type Accessory Product Spec
Accessory Type Styluses
Product Description The Apple Pencil delivers pixel-perfect precision and

industry-leading low latency, making it great for drawing,
sketching, coloring, taking notes, marking up email, and
more.
Effectivity Sellable and fulfillable immediately
Product Pricing $129
Behavior at design Read-only
Marketing Requirements – Bundle
Product Work Smart iPad Pro Bundle Offer
Product Code C-OFF-030
Product Description Work smarter with the Apple iPad Pro bundle.
Effectivity Selling period begins 1 month from today
Product Pricing Rolled up pricing

Exercise Guide
Minimum Default Maximum

Bundle Products Orderable Orderable Orderable
Apple iPad Pro 12.9” 1 1 1
Apple Pencil 1 1 2
4G LTE Data Plan 0 0 1
Task 2: Build products in EPC

Exercise Guide
Task 3: Test new products in the Cart
TIPS:
● Is the product active?
● Did you create and assign correct attributes to the product?
● Assign appropriate attribute metadata?
● Was the correct object type selected?
● Is the cardinality correct?

Exercise Guide
Yay! All done!

Shared Catalog Exercise Guide

Uploaded by

Copyright:

Available Formats

You might also like

Shared Catalog Exercise Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Shared Catalog Exercise Guide

Uploaded by

Copyright:

Available Formats

Enterprise Product Catalog

Enterprise Product Catalog Overview 7

Exercise 3-1: Creating Picklists 10

Exercise 3-2: Creating Product Attributes 24

Exercise 3-3: Creating Product Object Types 36

© Copyright 2022 Salesforce.com, inc. All rights reserved. 2

Task 3: Review an Object Type Layout 44

Exercise 3-4: Reviewing Product Life Cycles 53

Exercise 3-5: Creating Products 68

Exercise 3-6: Creating Product Bundles 89

Exercise 3-7: Managing the Shared Catalog 102

© Copyright 2022 Salesforce.com, inc. All rights reserved. 3

What other jobs should be run? 110

Exercise 3-8: Test the New Products in the Cart 123

Exercise 3-9: Create Tablet Products Challenge 130

© Copyright 2022 Salesforce.com, inc. All rights reserved. 4

What You Will Learn

● Navigate the Vlocity Product Console

© Copyright 2022 Salesforce.com, inc. All rights reserved. 5

© Copyright 2022 Salesforce.com, inc. All rights reserved. 6

Enterprise Product Catalog Overview

● Integrates into your end-to-end ecosystem by combining a complete product,

● Offers are designed by Marketing and sold to particular channels/customer

© Copyright 2022 Salesforce.com, inc. All rights reserved. 7

The Vlocity Product Console

© Copyright 2022 Salesforce.com, inc. All rights reserved. 8

© Copyright 2022 Salesforce.com, inc. All rights reserved. 9

Exercise 3-1: Creating Picklists

© Copyright 2022 Salesforce.com, inc. All rights reserved. 10

What is a Picklist in EPC?

© Copyright 2022 Salesforce.com, inc. All rights reserved. 11

Task 1: Review the Vlocity Product Console

2. In the Lightning Navigation Bar, click the Vlocity Product Console.

© Copyright 2022 Salesforce.com, inc. All rights reserved. 12

4. Under Product Management, next to Product, click the search icon.

7. Notice the list of tabs in the Console’s tab navigation bar.

8. Notice the reload icon in the right corner.

© Copyright 2022 Salesforce.com, inc. All rights reserved. 13

9. Notice the Save button.

© Copyright 2022 Salesforce.com, inc. All rights reserved. 14

Task 2: Create a picklist

In this task you are going to create a picklist called Connectivity.

2. Notice the required fields: Name, Code, and Data Type.

© Copyright 2022 Salesforce.com, inc. All rights reserved. 15

3. In the New Picklist dialog, enter the following information.

Code PKL_CONNECT Recommend using a PKL_

Description Wearable connectivity

Data Type Text

Active ✓ Recommend setting the

Effective From [today’s date] Recommend setting the

© Copyright 2022 Salesforce.com, inc. All rights reserved. 16

© Copyright 2022 Salesforce.com, inc. All rights reserved. 17

Task 3: Create picklist items

1. Click the Picklist Items facet.

© Copyright 2022 Salesforce.com, inc. All rights reserved. 18

4. Enter the following information.

Text Value GPS This value will be evaluated programmatically,

Label GPS This value will be visible to the user at run-time

Code PLI_GPS This value is not required to be unique.