PCM Hub Guide

PCM Hub covers the full lifecycle of your product catalog - creation, setup, configuration, management, and quick-viewing - across every core catalog object, in one simple-to-use screen:

• Products
• Attribute Definitions
• Attribute Categories
• Attribute Picklists
• Catalogs
• Categories
• Classifications
• Product Qualifications
• Product Disqualifications
• Selling Models

Most of these objects also expose relationship tabs - related data you’d otherwise have to visit a separate record page to see (e.g. a product’s price book entries, or an attribute definition’s picklist values) - right alongside the record itself. The two exceptions are Product Qualifications and Product Disqualifications, which are simple enough that they only need an Overview and a Detail tab.

Open the App Launcher, search for Deal Forge, and open the PCM Hub app.

Layout

• Left nav - the object selector and the record list for whichever object is currently selected
• Header bar - the selected record’s name and action buttons
• Tab strip and detail area - Overview, Detail, and any relationship tabs for the selected record

Header bar - action buttons

These buttons are gated by your actual object permissions (create, read, edit, delete) for whichever object is currently selected - not by whether you’re an admin. There’s no “admin only” restriction on creating, editing, cloning, or deleting catalog records themselves (that restriction only applies to Public list views - Section 5).

The header title reads “{Object} : {Record Name}” (e.g. “Product : Acme Widget”). When the selected record is a Bundle product, a bundle icon appears next to the title with a “Bundle Product” tooltip.

At the top of the left nav, an icon button opens the List Source panel on hover - a list of every supported object, each with its own icon. Selecting one switches the whole nav and detail area over to that object’s records. Switching objects clears any active search or filter and reloads the list fresh.

Bundle indicator on Product tiles

When Products is the selected object, any product whose Type is Bundle shows a small bundle icon in the bottom corner of its tile in the list, with a “Bundle Product” tooltip on hover. A simple (non-bundle) product shows no icon there. This is the fastest way to tell bundles apart from simple products while browsing the list, before you even open one.

Just like Deal Packages, the Filter control lets you build and save a reusable filter for the object you’re currently viewing - filters are scoped per object, so a filter you save while viewing Products won’t show up while viewing Categories.

• Click Filter, then New List View to build one
• Choose Private (only you see it) or Public (everyone with a PCM Hub seat sees it)

The Overview tab always shows a tile for the record itself, plus one tile per relationship the object supports.

The self tile (e.g. “Product”) shows a few key fields directly on the tile - for a Product, that’s Name, Product Code, Family. Hover the tile’s summary icon to open its Quick View popover for more detail - for a Product, Quick View adds Type, Description, Active, and Assetizable, with the name as a clickable link to the record.

Relationship tiles (e.g. “Pricebooks”) show a live count and a short preview instead of fixed fields - for Pricebooks, the count of assigned price book entries and a preview of their names. Quick View expands this into one row per related record, with its own key fields (for Pricebooks: Pricebook, List Price, Active) and row-level actions like Edit and Delete directly on each row.

Tile-level actions

Each relationship tile also carries the same actions as its full tab’s title bar, for example, the Pricebooks tile/tab shows Add Standard Price and Add to Price Book instead of a generic New button, since adding a price book entry needs a price book context. You can trigger any of these either from the tile on Overview, or from the tab itself - whichever is more convenient in the moment.

Hovering a tile highlights its tab

Hover anywhere on a relationship tile (not just its buttons) and the matching tab in the tab strip below highlights, so you always know which tab that tile’s data lives in before you click into it. Clicking the tile’s Open Tab button (forward-arrow icon) jumps straight there.

Every record has an Overview and a Detail tab, plus relationship tabs that depend on the object - and, for Products specifically, on whether that particular product is a Bundle or a Simple product.

Detail tab

A plain view/edit form for the record’s own fields, built on Salesforce’s native record form technology (not a custom Deal Forge form) - so whatever field-level security applies to you in the rest of Salesforce applies here too. For a Product, the fields appear in this order: Name, Product Code, Based On, Type, Owner, Created By, Last Modified By.

Relationship tabs by object

The two bolded tabs - Product Component Groups and Child Components - only appear for Bundle products. Selecting a Simple product hides both from the tab strip and from the Overview tab’s tile set at the same time, since a simple product has no bundle structure to show.

A relationship tab’s data loads the first time you click into it, not before - but its count (shown on the Overview tile) is fetched upfront so you always know how many related records exist without opening anything.

Every relationship tab has its own tab-level actions (in the tab’s title bar) and row-level actions (per record in the table):

Manage Picklist Values only appears for an attribute whose data type is Picklist - it opens a dedicated screen for adding, editing, and reordering that picklist’s values, separate from editing the attribute record itself.

Adding bundle child components uses a two-step flow instead of the generic New form: first pick which product(s) to add as children, then edit them together in a table (quantities, scaling, etc.) before confirming - since a single record form can’t create several related rows at once.

Any user with a PCM Hub seat can create, edit, clone, or delete a record for any object they have the underlying Salesforce object permission for - there’s no separate “admin only” layer on top of that for catalog records themselves (unlike Deal Packages, PCM Hub’s catalog objects don’t have a Public/Private visibility concept of their own - only saved list views do, see Section 5).

• New opens a form for the selected object’s own fields
• Clone (with a record selected) pre-fills a new record from the selected one
• Edit switches the Detail tab into an editable form
• Delete removes the record after a confirmation

PCM Hub is built so that your Salesforce permissions are the actual source of truth, not just something the interface tries to imitate:

• Every list, search, and record query only ever returns records and fields you’re permitted to see, enforced by Salesforce itself at query time - not filtered after the fact.
• Every field you view or edit goes through Salesforce’s native record form technology, the same engine standard Salesforce pages use. A field you don’t have access to is never shown as editable, and a field you can’t see at all is never shown.
• Every New, Edit, Clone, and Delete button is enabled or disabled based on your real create/edit/delete permission for that object - if you can’t actually perform the action in Salesforce, the button won’t let you either.
• Creating a Public (org-wide) saved list view is restricted to PCM Hub administrators, and that restriction is checked on the server, not only hidden in the button.

• See the Deal Packages Guide for building and applying Deal Packages.
• See the Install Guide for permission sets and license setup.