To automate the update of related records (Opportunity Products) based on a change to a parent record (the Opportunity), Flow Builder is the most powerful and app7ropriate tool. Specifically, a
"Record-Triggered Flow" can be configured to fire whenever an Opportunity is updated to the
"Closed Won" stage. The flow can then use a "Get Records" element to find all Opportunity Product records associated with that specific Opportunity and an "Update Records" element to apply the discount value from the parent to each line item. Formula Fields are insufficient here because they are "read-only" and cannot physically push data into other records for permanent storage. Approval Processes manage status changes but are not designed for bulk child-record updates. Flow Builder provides the logic necessary to handle this "one-to-many" update scenario, significantly reducing manual data entry for sales reps and ensuring that the financial data on the products accurately reflects the agreed-upon deal terms.

According to Agentforce best practices, action instructions must be highly specific regarding the action's purpose, the expected goal, and the conditions under which it should be triggered. Option D is the strongest set of instructions because it defines the Action (Update shipping address), the Goal (Modify address on a record), and a clear Constraint/Guardrail (Only use when the user explicitly requests it). This prevents the AI from accidentally triggering a data change based on a vague inquiry. Option B is also good but more restrictive than necessary unless the business logic specifically forbids updates during active orders. Option D provides the best balance of context and intent, ensuring the Large Language Model (LLM) understands the "why" and "when" of the action.

Profiles in Salesforce serve as the foundation for what a user can "do" with records, specifically defining Object-Level Security (Create, Read, Edit, Delete permissions). The standard Marketing User profile typically does not include full "Edit" access to the Opportunity object by default, as marketing roles are traditionally focused on Leads and Campaigns. To fulfill the requirement of allowing marketers to maintain campaign relationships on Opportunities, the administrator must ensure the profile has the necessary object permissions. If the organization is using a custom profile based on the Marketing User template, the admin should edit the object permissions directly on that profile to include "Read" and "Edit" for Opportunities. This allows the marketers to view the records and update the "Primary Campaign Source" field. While a Permission Set could also grant this access, the question implies the admin is currently configuring the profile itself.
Adjusting the profile's object permissions is the direct way to align the user's capabilities with the business's functional requirements.

When an AI agent like Agentforce transfers a conversation to a human support representative, the goal is a "warm handoff" where the rep can see exactly what the customer and the AI discussed. If reps are complaining about a lack of context, the most common administrative cause is that the Conversation History component (or Agent History component) has not been added to the Case Lightning Record Page. Without this component on their page layout, the rep sees the newly assigned case but cannot see the transcript of the preceding chat session. To resolve this, the Platform Administrator should use the Lightning App Builder to add the relevant history component to the Case page used by the support team. Option D is less likely if escalation is working but context is missing. Option A would prevent users from using Agentforce features but wouldn't specifically hide the transcript of a finished AI interaction. Ensuring the UI includes the conversation history is critical for maintaining high customer satisfaction during handoffs.

To allow users to post snapshots of dashboard components and engage in discussions about data directly on the dashboard, the Platform Administrator must enable Feed Tracking for dashboards. In Salesforce, Chatter Feed Tracking allows changes to records and interactions to be tracked and shared in the Chatter feed. For dashboards specifically, enabling this feature allows users to "Follow" a dashboard and use the "Post to Feed" functionality on individual dashboard components. This is highly effective for management teams who want to call out specific successes or areas of concern by tagging team members in a post that includes the visual chart. Reporting snapshots (Option A) are used for historical trend reporting, not social sharing. Downloading charts (Option B) is a manual file-handling process rather than an integrated social feature. Setting the "View Dashboard As" (Option C) determines data visibility but does not control Chatter functionality.