For a custom object to support Tasks and Events, the "Allow Activities" setting must be enabled in the object's properties. When a Platform Administrator creates a custom object, this checkbox is often left unchecked by default35. Enabling this feature allows the "Related To" (WhatId) field on a Task or Event to be linked to records of that custom object type36. While adding the related list to the page layout (Option C) is a necessary step for visibility, it will not work if the underlying feature isn't enabled first37. Sharing rules (Option A) and profile permissions (Option D) manage access to existing records but do not control whether the object is technically capable of having activities associated with it.

Tasks and Events are both part of the Activity object, but they often require different picklist values for the standard Subject field. To achieve this, the Platform Administrator must manage the picklist values for the Subject field specifically for each record type or activity type. In the Object Manager, under the Activity object (or Task/Event objects individually in some setups), the admin should edit the Subject field. Because Task and Event are distinct entities with their own picklist value sets for the Subject field, the admin can add "Schedule Site Visit" and "Send Contract" to the Task Subject list and "Site Visit" and "Ride Along" to the Event Subject list. This ensures that when a user creates a Task, they only see task-related subjects, and when they create an Event, they see event-related subjects. Option D is incorrect because it would mix all values together, causing confusion for the users. Option A (Predefined Field Values) is used to set a single default value for a field when an action is clicked, but it does not manage the available list of options in a picklist.

In the Salesforce Lightning Experience, the fields displayed in the "header" of a record and on the cards in the Kanban view are controlled by the Compact Layout. Each object has a System Default compact layout, but a Platform Administrator can create custom ones to prioritize the most important information, such as "Account Name" and "Close Date." By editing the primary compact layout for the Opportunity object, the admin directly controls which fields the sales team sees as they drag and drop deals through the Kanban stages. While Page Layouts (Option C) control the main record detail page and Kanban Settings (Option D) control which field is used for columns and summaries, the individual "card" content is always driven by the Compact Layout. This ensures that users can quickly gather key context without needing to open every individual record.

When naming actions for an AI agent, consistency is key to helping the Large Language Model (LLM) categorize and understand the available tools. Following a consistent naming convention, such as starting all retrieval actions with the verb "Get," allows the agent to more easily map user intent (e.g., "I need information about...") to the appropriate action. This reduces ambiguity during the reasoning phase of the agentic loop. Using inconsistent verbs like Find, Retrieve, or Identify (Option D) can confuse the model regarding which action is most appropriate for a given task. Removing verbs entirely (Option A) makes it harder for the model to distinguish between an action (doing something) and a data object (a thing). Adding "Salesforce" (Option B) is generally redundant as the agent's context is already within the Salesforce environment.

Creating effective Agentforce prompts requires a focus on clarity and simplicity to ensure the Large Language Model (LLM) follows instructions accurately. According to Salesforce best practices, administrators should use natural, easy-to-understand language and provide clear, concise instructions1919. This approach helps the AI accurately reason through the task without becoming confused by overly complex or nested logic (Option A). While technical accuracy is important, relying heavily on jargon or abbreviations (Option B) can sometimes lead to unexpected results if the LLM interprets those terms differently in various contextsFurthermore, providing high-level theoretical concepts (Option C) often results in vague or "creative" answers that may not be helpful for technical troubleshooting, which requires specific and actionable steps22. Using direct instructions like "Summarize the issue in three bullet points" is more effective than broad guidelines.