Soru

Zorluk: Çok zorQuick Actions, Custom Buttons, and Links

A System Administrator at Universal Containers needs to enable Sales Operations representatives working on Account records in Lightning Experience to complete two distinct tasks without navigating away from the page:
1. Rapidly create a child Case record pre-populated with specific parent Account field values (such as Account Owner and Account Type) and a default Priority set to 'High'.
2. Launch an interactive Screen Flow that calculates customer credit risk scores using the current Account record context.

Which TWO configuration steps should the System Administrator take to fulfill these requirements? Select 2 answers.

  1. Create an Object-Specific Create Record Quick Action on the Account object targeting the Case object, configure Predefined Field Values for the target fields, and add the action to the Account page layout or Dynamic Actions.Cevap
  2. Create an Object-Specific Flow Quick Action on the Account object referencing the credit score Screen Flow, and add the action to the Account Lightning page action bar.Cevap
  3. C
    Create a Custom Detail Page Button with OnClick JavaScript on the Account object to instantiate the Case record with default field values via API callouts.
  4. D
    Create a Global Quick Action targeting the Case object, because Global Actions automatically inherit parent Account field context when placed on the Account Lightning record page.

Cevap

The correct configuration requires creating an Object-Specific Create Record Quick Action on Account with Predefined Field Values for Case creation, and creating an Object-Specific Flow Quick Action on Account to launch the Screen Flow while passing record context.
To create a child record pre-populated with parent record data, an Object-Specific Create Record Quick Action must be created on the parent object (Account) targeting the child object (Case). This allows administrators to set Predefined Field Values using formulas (such as Account.OwnerId). To execute a Screen Flow while maintaining record context, an Object-Specific Quick Action calling the Flow must be configured and placed on the action bar.

Adım Adım Çözüm

1
Evaluate record creation requirements with field defaults from the parent record.
Identify that Object-Specific Quick Actions on Account targeting Case support Predefined Field Values derived from the source Account record.
Global Quick Actions do not have access to the underlying parent record context, whereas Object-Specific Quick Actions retain relationship context.
2
Evaluate Screen Flow invocation requirements from a Lightning record page.
Identify that an Object-Specific Quick Action of action type 'Flow' on Account can launch a Screen Flow directly.
Object-Specific Flow actions seamlessly pass the record's ID into the flow's recordId variable without requiring page redirects.
3
Verify Lightning Experience compatibility and component placement.
Confirm that Object-Specific Quick Actions are fully supported in Lightning Experience dynamic actions and publisher layouts, while JavaScript buttons are unsupported.
JavaScript custom buttons are legacy features restricted to Salesforce Classic.

Anahtar Kavram

Object-Specific Quick Actions vs Global Quick Actions and Custom Buttons in Lightning Experience
Tahmini Süre:2m 0s
Bu soruyu puanla