Explanation:

In a Guided Selling OmniScript within Salesforce Industries CPQ, the Selectable Items element plays a key role in presenting product options to users based on predefined filters and logic. It’s designed to dynamically display products that match user selections or context criteria.

✅ Correct Answers:

A. Retrieves filtered products from the product catalog
The element uses filters (often passed via Integration Procedures or remote actions) to query the product catalog and return only relevant items.
This ensures users see a curated list based on their needs or eligibility.

B. Lists products retrieved by the remote action
After the remote action (e.g., getCartsProducts) fetches the filtered products, the Selectable Items element renders them in the UI for selection.
It acts as the visual layer that displays product cards, images, and pricing.

❌ Why the Other Options Are Incorrect:

C. Invokes the remote method postCartItems
This method is used after selection, typically to add items to the cart — not by the Selectable Items element itself.

D. Stores the filters for the products to be retrieved
Filters are usually passed via Integration Procedures or DataRaptors, not stored in the Selectable Items element.

Explanation:

When viewing the Orders tab in Salesforce Industries (formerly Vlocity), the default statuses typically displayed are:

C. Salesforce Status –
This reflects the standard Salesforce object status field such as Draft, Activated, or Completed.

D. Salesforce Industries Order Status–
This is a more granular, Industries-specific status (e.g., In Progress, Pending, Failed, Completed) that reflects where the order is in the CPQ or OM lifecycle.

Why not the others?

A. State of tasks within an Orchestration Plan –
This level of detail is part of orchestration monitoring, not visible by default on the main Orders tab.

B. State of the Orchestration Plan itself –
Like task state, this is visible in orchestration-specific views, not typically on the Orders tab.

E. PONR Status (Point of No Return) –
This is a lifecycle checkpoint for order orchestration but is not a default column or filter in the Orders tab.

Explanation:

In Vlocity (Salesforce Industries) CPQ, Vlocity Picklist definition fields are used to define the list of selectable options for attributes. However:

These picklist definition fields themselves are not directly exposed or visible to users during runtime (i.e., in the Cart UI during order capture).

What is visible are the attribute values rendered using those picklist definitions, not the actual fields that define the picklist structure.

So while picklists control the available choices, the picklist object fields are not shown in the runtime experience.

Explanation:

In Vlocity Document Templates (used in Industries Document Generation), document sections can be conditionally included or excluded based on logic tied to:

Products – You can configure conditions to include sections when certain products are present in the quote, cart, or order.

Advanced Entity Filters – These allow more complex, rule-based logic (e.g., based on account type, opportunity stage, or any other data entity).

❌ Why not the others?
C. Merge Codes – These are used to insert dynamic values into the document (like placeholders), not for conditional logic to include or exclude entire sections.
D. Browser Version – Not relevant in the context of server-side document generation logic.

Explanation:

Why Attribute-Based Pricing Fits This Scenario:

The pricing varies based on product attributes (bandwidth: 1GB/10GB, network: Internet/external).

Attribute-Based Pricing lets you define price matrices or rules that map these attributes to specific charges.

Example:

| Bandwidth | Network | Monthly Price | One-Time Charge |

|-----------|-----------|---------------|------------------|

| 1 GB | Internet | $10 | $5 |

| 10 GB | External | $20 | $0 |

Why Other Options Are Incorrect:

A. Usage Pricing: For metered services (e.g., pay-per-use data), not fixed attribute tiers.

B. Context Rules: Determine when pricing rules apply (e.g., by market), not the price itself.

C. Cost and Margin Pricing: Focuses on profit calculations, not customer-facing attribute pricing.