Free Practice Questions for the Salesforce Consumer Goods Cloud AP-204 Exam (2026 Updated)

The Assessment Indicator Definition defines the KPI or measurable parameter that field representatives capture during Retail Execution. It provides the reusable definition of what must be measured, such as the number of products on a shelf, product facings, stock availability, promotional compliance, or another store-performance indicator.

Salesforce supports several data types for Assessment Indicator Definitions, including Number, Boolean, Date Time, Text, Decimal, and Picklist. The definition can then be associated with one or more Assessment Task Definitions covering products, product categories, promotions, planograms, or custom assessment scenarios.

The Assessment Indicator Definition works together with two additional KPI objects. A Retail Store KPI associates the indicator with its business context and defines the expected or target value. A Retail Visit KPI stores the actual result captured by the field representative during a specific visit. Salesforce therefore separates the reusable KPI definition, target configuration, and transactional result into distinct layers.

This design enables the same Assessment Indicator Definition to be reused across multiple store groups, products, locations, and visits while maintaining separate targets and actual values for each applicable context.

Study Guide Topics:Data Setup - > Assessment Indicator Definition - > Retail Store KPI - > Retail Visit KPI - > KPI Measurement

===============

The representative should edit the product tags so that the detected object is associated with the correct product classification. Accurate tagging is fundamental to maintaining reliable object-recognition results, particularly when two products have visually similar packaging.

Object detection identifies objects within an image and maps those detections to labels or product classes. If a competitor changes packaging so that its product resembles another SKU, the resulting classification can incorrectly increase the measured facings or share-of-shelf for the wrong product. Correcting the tag provides accurate classification information and helps maintain the integrity of the shelf measurement.

Salesforce ' s Einstein Vision architecture supports a feedback process for incorrectly classified objects. When an object-detection model misclassifies an image, corrected examples and labels can be added back to the dataset and used in subsequent training or retraining. Salesforce describes this feedback mechanism specifically as a way to improve models after misclassification.

Creating a new planogram would only alter the expected shelf arrangement and would not correct product identity. Turning competitor products around manipulates the physical merchandising environment rather than correcting the data. Canceling the task similarly fails to improve future recognition.

Study Guide Topics:Platform - > Einstein Object Detection - > Product Tags - > Classification - > Share-of-Shelf Accuracy

===============

The frozen food aisle should be modeled as an In-Store Location. In-Store Location represents a specific physical area inside a retail store where products are displayed, stored, or evaluated. Salesforce identifies aisles, shelves, checkout counters, endcaps, and back rooms as typical examples.

Once the Frozen Food Aisle record is created, products can be associated with that location through Store Product. Store Product establishes the relationship among the Retail Store, Product2, and the applicable In-Store Location. This gives the Inventory Check sufficient context to tell the field representative exactly where the product should be inspected.

The In-Store Location can also be assigned an In-Store Location Category. Categories make it possible to group equivalent locations across multiple stores and configure Retail Store KPIs consistently for a store group. For example, all frozen-food aisles could share a category and common inventory-assessment rules.

Adding a custom picklist or task/store record type would duplicate functionality already provided by the standard Consumer Goods data model. Product2 identifies the commercial product; it does not by itself describe the product ' s physical placement within an individual store.

Study Guide Topics:Data Setup - > In-Store Location - > Store Product - > Inventory Check - > Store Layout

===============

The Delivery Task is the Consumer Goods Retail Execution object specifically designed to support Direct Store Delivery activities during a visit. It represents the delivery activity assigned to the field or delivery representative and provides the execution context through which shipments and individual product transfers are processed.

Salesforce separates the delivery process into several related records. The Delivery Task defines the activity that must be performed as part of the Action Plan associated with the Visit. A Shipment is then associated with that Delivery Task to identify the inventory that must be delivered. Products and quantities within the Shipment are represented through Product Transfer records.

This architecture allows the same delivery task framework to control execution while shipment records manage the physical movement of inventory. Salesforce specifies the Lightning Direct Store Delivery permission for users who perform Delivery Task functionality. When an Action Plan Template containing a delivery task is assigned to a visit, Delivery Task records are created and can subsequently be associated with shipments.

Therefore, Delivery Task is the purpose-built Consumer Goods object for initiating and managing Direct Store Delivery execution.

Study Guide Topics:Visit Execution - > Direct Store Delivery - > Delivery Task - > Shipment - > Product Transfer

===============

The Product Performance dashboard is designed to help sales managers analyze how products, product categories, brands, and assortments are performing across the Consumer Goods organization. It provides detailed performance views that allow users to identify both strong and weak performers and then drill into the underlying metrics.

Salesforce states that the Product Performance dashboard analyzes product category, brand, product, assortment, and the impact of promotions on performance. Its Product page shows overall product trends and enables managers to identify high-performing products and analyze recently launched products. Its Category and Assortment pages provide equivalent analysis at those organizational levels.

Typical measures include revenue, quantity, average order value, store coverage, average compliance, and related sales-performance indicators. Salesforce specifically describes the dashboard as answering questions such as which products, categories, brands, and assortments are high-performing or least-performing. Managers can drill into individual entities to investigate performance trends and identify where intervention or additional investment is appropriate.

Therefore, the dashboard gives the Sales Manager the ability to identify top- and low-performing products, categories, and assortments and investigate their performance in greater detail.

Study Guide Topics:Analytics - > Product Performance - > Product Categories - > Assortments - > Performance Analysis

===============

Salesforce supports Promotion Checks at three defined levels: General Promotion, Individual Product, and Product Category. These levels determine the commercial context against which a field representative performs the promotional compliance assessment.

A Product Category-level Promotion Check is appropriate when the promotion applies across a category of products. For example, an organization may discount all beverages or energy bars and assess compliance collectively rather than creating an independent promotion check for each SKU.

An Individual Product-level Promotion Check is used when a promotion applies to a specific product, such as the launch of a new flavor or an in-store sampling activity. The field representative evaluates execution specifically for that product.

A General Promotion does not require association with a particular product or product category. It is suitable for store-wide activities such as coupons, signage, or general promotional conditions that apply across the outlet.

These three levels allow promotion configuration to match the intended scope while avoiding unnecessary duplication of promotional records and assessment tasks. Salesforce uses the same levels when defining the promotion and when executing the corresponding Promotion Check in the field.

Study Guide Topics:Visit Execution - > Promotion Check - > General Promotion - > Product - > Product Category

===============

Einstein Visit Recommendations provide decision support for sales managers and field representatives by helping them determine which stores should receive attention and when those visits should be scheduled. The capability supplements the expertise of the field organization by presenting prioritized information derived from business rules and prediction insights.

Salesforce describes the feature as a mechanism for scheduling the right stores at the right time in order to maximize profit and deliver brand value. Visit Recommendations can identify stores that have not been serviced recently and present recommended visits that users can review and schedule. Managers remain responsible for deciding which recommendations to accept and for coordinating execution.

The recommendation architecture can use configurable flow strategies or Next Best Action strategies. Organizations can tailor the logic to their own business requirements rather than relying on a mandatory external market-research dataset. This enables field professionals to focus their expertise on selling, merchandising, customer relationships, and execution while Salesforce surfaces relevant visit-planning intelligence.

The intended value is therefore workforce augmentation and improved prioritization-not replacement of experienced personnel.

Study Guide Topics:Visit Planning - > Einstein Visit Recommendations - > Recommendation Strategies - > Store Prioritization - > Field Productivity

===============

Users performing Consumer Goods Retail Execution activities require the appropriate combination of Retail Execution, Industries Visit, and Action Plans permissions.

Lightning Retail Execution Plus provides access to Consumer Goods Retail Execution capabilities for strategic-sales users. Salesforce lists Lightning Retail Execution Plus among the available Retail Execution permission set licenses used to enable Consumer Goods features.

The Industries Visit permission provides access to industry-specific Visit functionality. Visits are fundamental to Retail Execution because they represent scheduled interactions between field representatives and Retail Stores. The permission set supplies access to objects involved in visit execution, including Visit, Assessment Task, Assessment Task Definition, Action Plan, Action Plan Template, and related records.

The Action Plans permission enables users to access and manage Action Plans. Action Plan Templates define the repeatable activities that are subsequently associated with Visits and executed by field representatives.

Salesforce ' s setup instructions direct administrators to assign a Retail Execution permission set together with Action Plans and Industries Visit to users who require access to visits, tasks, and related Retail Execution capabilities. Sales Quotations addresses a different commercial process.

Study Guide Topics:Platform - > Permission Sets - > Lightning Retail Execution Plus - > Industries Visit - > Action Plans

===============

For the Agentforce Consumer Goods visit-execution model, the appropriate Action Plan Type is Visit Execution. Action Plan Templates provide reusable collections of activities that field representatives repeatedly perform during visits to retail stores.

Salesforce ' s Consumer Goods data-model training identifies Visit Execution as the Action Plan Type used for Retail Execution templates and Visit as the Target Object. The template can then contain tasks such as inventory checks, planogram checks, promotion checks, asset checks, surveys, order-related activities, and other recurring work.

The Action Plan Template separates reusable task configuration from individual Visit records. Administrators define the common activities once, establish their order and mandatory status, and then associate the template with multiple visits. When the template is applied, Salesforce creates the necessary visit-level tasks so the field representative receives a consistent execution workflow.

This approach is particularly important in consumer goods organizations where representatives may perform essentially the same merchandising, inventory, promotion, order, and compliance activities across hundreds or thousands of stores. Visit Execution provides the action-plan classification aligned with that Retail Execution business process.

Study Guide Topics:Visit Planning - > Action Plan Template - > Visit Execution - > Visit Target Object - > Assessment Tasks

===============

Planogram analysis focuses on measurable shelf-compliance indicators such as Out of Stock, Share of Shelf, and product facings. These metrics allow a consumer goods organization to determine whether products are available, whether they occupy the expected proportion of shelf space, and whether the required number of product faces are visible to shoppers.

Salesforce defines Planogram Check as an assessment task used to track product displays and evaluate shelf execution. For planogram-related Retail Store KPIs, Salesforce explicitly maps Assessment Indicator Definitions to KPI types. Product-facing measurements use Facings, share-of-shelf measurements use Share of Shelf, and stock-availability measurements use Out of Stock. The facing measure is associated with individual products or SKUs when the organization needs to determine the number of visible product facings.

The underlying planogram model associates the reference Image with an In-Store Location and connects products to that location. During execution, those relationships provide the product-specific context required to assess whether the shelf configuration conforms to the intended merchandising arrangement. Shelf size itself is not one of the supported KPI types for this planogram-compliance configuration.

Study Guide Topics:Visit Execution - > Planogram Check - > Share of Shelf - > Facings - > Out-of-Stock Compliance

===============

The consultant must identify the hierarchy level that represents the stock keeping unit (SKU). In the Consumer Goods Retail Execution data model, individual products are represented through Product2 records, and Salesforce describes each Product2 record as a SKU or sellable unit. Consequently, the ERP hierarchy level that contains SKU-level information provides the appropriate product granularity for product-specific retail execution processes.

Share-of-shelf measurement requires Salesforce to identify precisely which products occupy shelf space so that actual shelf presence can be evaluated against configured targets. Retail Store KPIs can associate Assessment Indicator Definitions such as Share of Shelf with products, product categories, planograms, store groups, and in-store location categories. The underlying product master therefore needs a level that reliably represents the individual sellable products being measured.

Salesforce product master data can contain multiple hierarchy levels such as categories, subcategories, brands, and SKUs. The numerical position of a tier is not itself significant; what matters is the business meaning of that tier. For this requirement, the tier representing SKUs provides the required product-level data for shelf measurement and Retail Execution processing.

Study Guide Topics:Data Setup - > Product2 - > Product Hierarchy - > SKU - > Share-of-Shelf KPI

===============

Actual KPI values captured by a field representative during visit execution are stored in the Retail Visit KPI record. Salesforce separates KPI configuration from transactional execution data so that planned or target values remain distinct from values observed during individual visits.

The Retail Store KPI defines the target or expected value for a particular Assessment Indicator Definition. It provides the planning context, including the Retail Store Group, product or product category, In-Store Location Category, Custom Context, and target value. When an assessment task is generated for a visit, Salesforce creates the corresponding Retail Visit KPI records that represent the runtime measurements.

During execution, the field representative records the observed value. Salesforce stores fields such as the Actual Value, Target Value, Assessment Indicator Definition, Product, In-Store Location, and Custom Context on the Retail Visit KPI.

This architecture allows Salesforce to compare expected performance with actual field results across multiple visits. The custom object can supply the business context for a custom task, but it does not replace the Retail Visit KPI as the repository for actual assessment measurements.

Study Guide Topics:Data Setup - > Custom Tasks - > Retail Store KPI - > Retail Visit KPI - > Actual Values

===============

Inventory Check execution is scoped to the products associated with the specific Retail Store being visited. Salesforce Retail Execution uses this relationship to ensure that the field representative works only with products relevant to that outlet rather than searching the organization ' s entire Product2 catalog.

The Store Product object establishes the association between a product and a Retail Store or a specific In-Store Location. This relationship provides the product context used during store-level execution. Inventory Checks allow representatives to capture real-time information such as stock quantities, facings, share of shelf, product placement, and other assessment indicators for products sold in the store.

Product ownership or the identity of the user who created a Product record does not determine whether it should appear during an Inventory Check. Those attributes are unrelated to the commercial assortment or stocking relationship between a product and the retail location. Searching every product in the organization would also introduce irrelevant records and reduce mobile execution efficiency.

Therefore, product search during an Inventory Check is based on products associated with the Retail Store, ensuring the representative receives an operationally relevant product list for that visit.

Study Guide Topics:Visit Execution - > Inventory Check - > Store Product - > Retail Store - > Product Association

===============

For a product-level Inventory Check, the product must be associated with the Retail Store where the assessment will be executed. Retail Execution needs a store-specific product relationship so Salesforce can determine which products are available for assessment when the field representative opens the Inventory Check.

Salesforce ' s Inventory Check prerequisites explicitly require administrators to associate Products with the Retail Store and associate the applicable In-Store Locations with that same Retail Store. The Retail Store must also belong to the Retail Store Group selected on the Retail Store KPI.

The Retail Store KPI then defines the assessment target by combining the Retail Store Group, applicable In-Store Location Category, Assessment Indicator Definition, and Product or Product Category. Salesforce separately specifies that the Product field is required on a Retail Store KPI when inventory-check tasks are configured for the store group.

The Store Product relationship provides the standard data-model mechanism for associating an individual Product2 SKU with a Retail Store or particular In-Store Location. A Promotion or Product Category relationship serves a different business purpose, while an Assortment defines a collection of products eligible for sale rather than replacing the required store-product association for Inventory Check execution.

Study Guide Topics:Data Setup - > Inventory Check - > Product - > Retail Store - > Store Product - > Retail Store KPI

===============

A Delivery Task combined with SKU-level inventory tracking provides the appropriate operational model for tracking samples distributed through field representatives or distributors. Delivery Tasks represent delivery activities performed during store visits and are associated with Shipments that define which products must be delivered.

Within Salesforce inventory management, Product Item records represent quantities of specific products at inventory locations. A Product Item therefore provides the inventory relationship between the Product2 record and a location, with Quantity On Hand recording the current available quantity. For mobile inventory such as a distributor vehicle, Salesforce supports a Location configured as a mobile inventory location and allows Product Items to record the inventory carried in that vehicle.

Product Transfers associated with shipments identify the specific products and quantities being moved between locations. As delivery activities are performed, Salesforce can update inventory quantities accordingly. This provides operational traceability at the individual SKU level rather than merely reporting on shipping-document status.

Because the requirement is to monitor samples that remain available to distributors in the field, tracking the sample SKU ' s on-hand quantity together with the Delivery Task provides the most appropriate inventory-management approach.

Study Guide Topics:Visit Execution - > Direct Store Delivery - > Delivery Task - > Product Item - > Quantity On Hand - > SKU

===============

Promotion Check functionality is intended to allow field representatives to validate whether a planned promotion has been executed correctly at a retail location. Two important execution capabilities are reviewing the products included in the promotion and capturing photographic evidence of the promotional display.

Salesforce supports promotions at Product Category, individual Product, and General Promotion levels. When performing the check, the representative needs visibility into the promotion context so the correct products or categories can be inspected. Product information establishes exactly what must be evaluated and prevents the representative from auditing unrelated merchandise.

Photo capture provides supporting visual evidence of the in-store execution. This is particularly useful for validating display placement, promotional materials, shelf presentation, or other compliance requirements. The recorded observation can then be evaluated together with applicable assessment indicators and Retail Store KPI targets.

Planning dates and discounts are part of promotion configuration and commercial planning rather than field compliance execution. The field representative ' s responsibility during the visit is to observe, validate, and record execution rather than modify the underlying promotional terms.

Therefore, viewing promoted products and taking photographs are the applicable standard field-execution capabilities.

Study Guide Topics:Visit Execution - > Promotion Check - > Products - > Compliance - > Photo Capture

===============

Custom assessment tasks use the Consumer Goods Custom Task Measures component to expose KPI information on the related object ' s record page. For this experience to appear, the administrator must both place the component on the relevant Lightning Record Page and ensure that the intended users receive that page through the correct page assignment.

Salesforce instructs administrators to open the custom or standard object ' s Lightning Record Page in Lightning App Builder, drag the Consumer Goods Custom Task Measures component onto the page, configure its properties, and save the page. If the component has not been added, users naturally see the object ' s standard record-page experience instead of the custom KPI interface.

Lightning Record Pages must also be activated for the appropriate application, record type, and user profile. Salesforce ' s page activation framework supports assignments by app, record type, and profile, allowing different users to receive different record-page experiences. If the custom task page is not assigned to the field representative ' s profile, Salesforce can display another assigned or standard record page instead.

These two configuration layers-component placement and profile/page assignment-are therefore required for the KPI component to appear.

Study Guide Topics:Platform - > Lightning App Builder - > Custom Tasks - > Consumer Goods Custom Task Measures - > Record Page Assignment

===============

An Action Plan Template can contain multiple Inventory Check, Planogram Check, and Promotion Check assessment tasks. These are KPI-based Retail Execution activities that may need to be repeated within a single store visit for different products, categories, promotions, or in-store locations.

Salesforce explicitly states that administrators can add multiple Inventory Check, Planogram Check, and Promotion Check tasks to one Action Plan Template. By contrast, Salesforce restricts the template to only one Order Creation task or one In-Store Survey task.

This flexibility is important because a typical consumer-goods visit can involve several independent merchandising objectives. A representative might perform separate inventory checks for different store areas, validate several planograms, and verify multiple promotions during the same visit. The Action Plan Template provides a reusable framework that groups these activities and controls their required status and display sequence.

Templates must also progress through the appropriate lifecycle before operational use; simply defining the structure does not substitute for making the template available for visit execution. Salesforce further supports extensibility through flows, component tasks, and other Action Plan mechanisms.

Therefore, the ability to include multiple planogram, inventory, and promotion checks is the accurate statement.

Study Guide Topics:Visit Planning - > Action Plan Templates - > Inventory Check - > Planogram Check - > Promotion Check

===============

Promotions can be defined at the Product Category level or the individual Product level when the promotion has a product-specific commercial context. Salesforce also supports a general promotion with no product or product-category context, but among the listed options, Product Category and Product are the applicable promotion-definition levels.

A Product Category promotion applies the promotional activity to a collection of related products. This design is appropriate when the same commercial offer applies across an entire category, such as discounted beverages or energy bars. A Product-level promotion applies to one or more specific products, such as a new-product launch, sampling campaign, or SKU-specific discount.

Salesforce stores the relationship between a promotion and its individual products through Promotion Product. For category-based promotions, the relationship is represented through Promotion Product Category. Account, Retail Store Group, and Retail Store describe the reach or channel through which a promotion is distributed rather than the product level at which the promotion itself is defined. These destinations are associated through the Promotion Channel model.

This separation allows administrators to independently define what products a promotion concerns and where the promotion applies.

Study Guide Topics:Data Setup - > Promotions - > Product Level - > Product Category Level - > Promotion Product

===============

Frequently purchased products can be prioritized for a specific outlet by associating them through Store Product and marking the appropriate products as Favorite. Store Product represents the relationship between Product2 and a Retail Store or specific In-Store Location, which allows Salesforce to maintain outlet-specific merchandising and ordering attributes.

The Store Product data model includes both Is Favorite and Default Order Quantity. These attributes are designed to streamline recurring order capture. Salesforce explains that field representatives can prioritize favorite products when creating orders so commonly purchased items are replenished efficiently and remain in stock. Default Order Quantity can further reduce data entry by predefining the quantity normally ordered for the product.

Salesforce ' s Retail Execution configuration also allows products associated with a store to be marked as favorites. The Inventory and ordering user interfaces can expose favorite products as a focused subset, reducing the time required to create routine orders.

This makes Store Product the correct outlet-specific mechanism for modeling frequently ordered products rather than creating artificial Order records with a template status.

Study Guide Topics:Visit Execution - > Order Capture - > Store Product - > Favorite Products - > Default Order Quantity

===============

For a scalable Visit Recommendation strategy, Salesforce recommends implementing the selection logic through an Apex class. Visit Recommendations can use programmable logic to determine which stores should receive recommendations based on organization-specific criteria, and Apex is appropriate when the strategy must operate at business scale.

Salesforce allows an Apex class to select the stores for which Einstein should provide Visit Recommendations. The Apex method is exposed to automation by using @InvocableMethod, after which the class can be invoked from the Visit Recommendation strategy or from an autolaunched flow.

Salesforce also supports a Flow strategy for Visit Recommendations, but its documentation specifically notes that the flow-only method is not scalable for a business use case and recommends using Apex for scalable implementations. An Apex implementation gives developers greater control over bulk processing, complex filtering, reusable business logic, and Salesforce governor-limit considerations.

The strategy can return the recommended Store IDs and recommendation reasons so sales managers and field representatives understand both which stores should be visited and why those stores have been prioritized.

Workflow and Process Builder are not the architecture Salesforce defines for this Visit Recommendation capability.

Study Guide Topics:Visit Planning - > Einstein Visit Recommendations - > Apex - > Invocable Methods - > Scalable Recommendation Strategies

===============

An Einstein object-detection implementation depends on three essential elements: a suitable training dataset, a properly trained and evaluated model, and appropriate user access to the functionality.

The implementation begins by collecting representative images of the products or objects that must be detected. For object detection, the training images require labeled bounding boxes identifying the position and dimensions of each object. These examples are uploaded as a dataset and used by the training process to create an object-detection model.

The trained model should then be evaluated before deployment. Salesforce ' s model-training architecture reserves data for testing and provides model information that allows implementers to evaluate the model ' s detection performance. Reviewing model quality before exposing the capability to field representatives is essential because representative training data and adequate model performance directly affect detection results.

Finally, the field users who execute the functionality require the relevant access and permissions. Permissions are part of the Salesforce security model and determine whether users can access the required Consumer Goods and Einstein functionality.

OCR configuration and competitor-suppression datasets are not baseline requirements for this object-detection setup.

Study Guide Topics:Platform - > Einstein Vision - > Object Detection - > Dataset - > Model Training - > User Permissions

===============

A Store Product represents the relationship between a Product2 record and a particular Retail Store or In-Store Location. This relationship supplies the store-specific product context required by several Retail Execution processes.

For Inventory Checks, Salesforce must determine which products are relevant to the store being visited. Store Product records provide that relationship, allowing the Inventory Check experience to present applicable products rather than the entire enterprise product catalog. The same store-level product context supports the Search and Scan experience, where field representatives locate a product directly or scan its barcode while performing an inventory assessment.

Store Products also contribute to order capture. Salesforce stores operational attributes on the Store Product relationship, including the associated Product, Retail Store, In-Store Location, default order quantity, and favorite-product indicator. These fields allow the order experience to identify products that are relevant to a specific outlet and facilitate efficient repeat ordering.

Salesforce distinguishes Store Product from Store Assortment: Store Product represents products directly associated with a store or in-store location, while assortments define broader groups of products eligible for sale.

Study Guide Topics:Data Setup - > Store Product - > Inventory Check - > Search and Scan - > Order Capture

===============

Photos captured during an asset-compliance activity are maintained within the assessment-task content framework, allowing the evidence to remain associated with the task that generated it. For an asset check implemented as a custom Assessment Task, this provides the most direct relationship between the compliance observation and its supporting photographic evidence.

Salesforce provides the Assessment Task Content Document object specifically for associating Content Documents with assessment activities. Its data model includes a reference to the parent Assessment Task and a Content Document reference, allowing files generated during execution to remain connected to the task. Salesforce also supports a content-context reference that can identify contextual business records such as an Asset or Visit.

Within Retail Execution, Salesforce uses Assessment Task Content Document records for notes and pictures captured by field representatives while performing assessment activities. This preserves the evidentiary relationship between the field observation and the work performed, enabling managers to review photographs alongside the associated compliance task.

The photo therefore remains accessible through the asset check Assessment Task, where the manager can review the evidence in the same operational context as the captured asset-compliance measurements.

Study Guide Topics:Visit Execution - > Asset Checks - > Assessment Task - > Content Documents - > Photo Evidence

===============

The Action Plan Template must use Visit as the Target Object and must be published before it can be used to generate an Action Plan for a retail visit.

Salesforce defines the Action Plan Template as a reusable framework for activities that remain consistent across multiple visits. During template creation, the administrator specifies Visit as the Target Object and configures the required Action Plan Type. Assessment tasks, flows, delivery-related activities, or other supported work items are then added before the template is published.

Publishing is an essential lifecycle step because Salesforce permits only published templates to be used when associating an Action Plan with a Visit. To create the association, the user opens the Visit, navigates to the Action Plan related section, selects New Plan, and chooses the required published template. Salesforce displays the tasks defined by the template and creates the Visit-specific Action Plan after the configuration is saved.

The process therefore does not depend on activating the Visit or separately activating an Action Plan. The key configuration is ensuring that the reusable template is explicitly designed for Visit records and has been published for use.

Study Guide Topics:Visit Planning - > Action Plan Template - > Visit Target Object - > Publish Template - > Action Plan Association

===============

Flow-based tasks operate within the Visit and Assessment Task execution context and require the business context necessary to determine the applicable KPI configuration. The Retail Store KPI represents the target definition for an Assessment Indicator Definition and provides information such as store group, product, location category, target value, and other assessment context.

The flow also operates with the relevant Assessment Task and Visit identifiers so that automation can execute against the correct task instance and scheduled retail visit. This maintains the relationship between the reusable configuration and the transaction generated for an individual field visit.

Salesforce ' s broader assessment architecture reflects the same hierarchy: assigning an Action Plan Template to a Visit creates Assessment Tasks based on Assessment Task Definitions, while Retail Visit KPIs are generated using the applicable Retail Store KPI configuration.

This separation is essential. Retail Store KPI supplies expected business targets, Assessment Task provides the executable activity, and Visit supplies the store-engagement context in which the Flow runs.

Study Guide Topics:Visit Execution - > Flow-Based Tasks - > Retail Store KPI - > Assessment Task - > Visit Context

===============