Question

Difficulty: HardQuick Actions, Custom Buttons, and Links

A Sales Operations Administrator at a global logistics firm is updating the Account Lightning record page. The business requires two specific capabilities for account managers: 1) Quickly create a child 'Shipment Audit' custom record automatically linked to the current Account, with default field values pre-populated from the parent record. 2) Launch an external third-party logistics portal in a new browser window, dynamically passing the Account's Shipping Account Number as a URL query parameter. Which two configuration choices should the administrator implement in Lightning Experience to satisfy these requirements? (Select 2 answers)

  1. An Object-Specific Quick Action of type 'Create a Record' on the Account object, configured with Predefined Field Values.Answer
  2. A Custom Detail Page Link on the Account object with a URL content source incorporating record merge fields.Answer
  3. C
    A Global Quick Action of type 'Create a Record' configured on the Account object layout with Component Visibility filter rules.
  4. D
    A Custom Detail Page Button on the Account object using an OnClick JavaScript content source to build the target URL.

Answer

The correct implementation requires configuring an Object-Specific Quick Action on the Account object to create the child record with predefined values, alongside a Custom Detail Page Link using a URL with merge fields to launch the external portal.
To create a child record from a parent page while automatically establishing the parent-child relationship and pre-populating field values, an Object-Specific Quick Action must be created on the parent object. Additionally, launching an external site with dynamic record parameters is natively solved by creating a Custom Link with a URL content source that references record merge fields.

Step-by-Step Solution

1
Evaluate record creation with parent context requirements.
Identify that an Object-Specific Quick Action on Account allows targeting child custom objects while passing context and pre-populating fields via Predefined Field Values.
Global actions do not automatically bind to the specific record context of the viewing page, whereas object-specific actions maintain relational context.
2
Evaluate external web page launching requirements.
Identify that a Custom Link on Account configured with a URL endpoint and dynamic field merge tokens ($Account.Shipping_Account_Number__c) fulfills passing parameters to external applications.
Custom links natively support URL parameterization with Salesforce object fields.
3
Eliminate incompatible Lightning customization options.
Reject OnClick JavaScript buttons due to lack of Lightning Experience support.
JavaScript custom buttons are legacy features restricted to Salesforce Classic.

Key Concept

Selecting appropriate button, link, and quick action mechanisms based on target object context and Lightning architecture support.
Rate this question