A layout section in the Vlocity Product Console functions as a Lightning user interface control. This means it serves as a structural component that can be used to organize and display information within the console effectively. Layout sections are part of the broader design and layout capabilities of the Lightning framework, allowing administrators to customize how data and options are presented to users in the Product Console, enhancing user experience and interface organization.

When Felix, a Vlocity CPQ administrator, finishes creating a new product bundle with child products in the shared product catalog, he must ensure that the product bundle displays correctly in the Vlocity Cart. To do this, he needs to first run the Product Hierarchy Maintenance job. This job updates the system's understanding of product relationships and hierarchy, which is critical when new bundles and product relationships are established. Following this, he should run the Refresh Pricebook job, which updates pricing information across the system to reflect any changes or new additions. This sequential process ensures that both the structural and pricing aspects of the new product bundle are correctly integrated into the CPQ system.

In Salesforce Industries CPQ (formerly Vlocity), to make a product not assetizable, two main settings can be adjusted within the Vlocity Enterprise Product Catalog (EPC) and Vlocity Cart:
* Check the Not Assetizable flag in Vlocity EPC: This option directly specifies that the product is not to be treated as an asset post-purchase, thereby excluding it from asset management processes.
* Check the Do Not Assetize flag in Vlocity Cart's line item configuration window: This flag can be set per transaction in the cart configuration, providing flexibility to override the default assetization behavior for specific sales scenarios.
These settings ensure that the product does not get converted into an asset in the Salesforce Industries CPQ system, which is crucial for items that are either consumed upon use or do not require ongoing service management.

To charge different prices for the same product within the context of different bundles, the pricing adjustments can be made in the price list where the price list entry is located. By managing different price list entries for the same product within different bundles, you can set unique prices that reflect the varying contexts in which the product is sold. This method provides the flexibility to tailor pricing based on the bundle's specific market or customer segmentation strategies.

Launching a guided selling process in Salesforce Industries CPQ can be effectively achieved using a Vlocity action. These actions are configured within the Salesforce Industries platform and can be directly linked to OmniScripts or other processes that initiate guided selling scenarios. Actions can be set up to start based on various triggers or user interactions within the Salesforce environment, providing a versatile entry point for guided selling processes.