PDF Consumer-Goods-Cloud-Accredited-Professional Study Guide

Einstein for CG- Visit Recommendations is a feature that uses artificial intelligence to suggest optimal store visits for field reps based on predefined rules and criteria. By adopting this feature with the consumer goods cloud, professionals can focus on their work while having information served to them that will support them in being competitive. For example, they can prioritize the most profitable or strategic stores, avoid unnecessary or redundant visits, and optimize their routes and schedules. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 36.

The requirement is:

Product A should be included by default (default=1)

User can remove it (Min=0)

They cannot increase quantity beyond 1 (Max=1)

This exactly aligns with cardinality settings:

Min = 0 (optional)

Max = 1 (only one allowed)

Default = 1 (pre-included)

Auto Add (A) does not allow opt-out.

Recommend Rule (C) only suggests the product — does not auto-include.

Retail Store KPIs are key performance indicators that measure how well a retail store is performing against a specific goal or target. For a promotional end cap audit, Retail Store KPIs should be defined at the energy bar product category level, as this would capture all the energy bars that are included in the BOGO promotion and also minimize the number of records created. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 30-31.

This scenario involves managing the lifecycle of data stored in custom child objects (Object A attached to Order Items, and Object B attached to Assets). To ensure data integrity throughout the full commercial cycle—Sale (Assetization) and Change (MACD)—a bidirectional mapping strategy is required using the Custom Object Map feature (referred to as Object Mapper in the options).

Assetization (Order to Asset Flow):

When an order is completed, the system runs the "Assetize" process.

To move data from the custom object under the Order Item (Object A) to the custom object under the Asset (Object B), you must define a Source-to-Destination mapping.

This is the A $\rightarrow$ B mapping. Without this, the custom data entered during the sale would be lost and not stored on the customer's asset record.

MACD / Asset-Based Ordering (Asset to Order Flow):

When a customer requests a Move, Add, Change, or Delete (MACD), the system creates a new Order/Quote by reading the existing Asset data.

To ensure the new "Change Order" includes the current details from the Asset (Object B) back onto the line items (Object A) for the agent to view or modify, the system requires a reverse mapping.

This is the B $\rightarrow$ A mapping.

Why other options fail:

Option A (Apex Hook): While feasible for complex edge cases, using Apex is not the best practice when a declarative configuration tool (Object Maps) exists for this exact purpose. It increases maintenance debt.

Option B (Map A to B only): This handles the initial sale but fails during MACD. When the customer tries to change their service later, the data from Object B would not copy back to the new order, leading to data loss or errors.

Option C (Field Mapper): Field Mappers are typically used for mapping specific fields on the primary objects (e.g., OrderLineItem.Description to Asset.Description). For mapping entire related child objects, the Object Map mechanism is the correct architectural component.