Examkin

Question

Difficulty: HardQuick Actions, Custom Buttons, and Links

A Field Service Administrator at a manufacturing enterprise is configuring Lightning Experience for equipment maintenance operations. When service technicians view a custom object record for Equipment_Maintenance__c, they require a streamlined mechanism directly on the record page highlights panel to create a child Service_Ticket__c record. The new ticket must automatically populate the parent Equipment_Maintenance__c lookup field and pre-assign the ticket Priority field to 'High'. Which configuration solution should the administrator implement to meet these requirements?

  1. Create an Object-Specific Quick Action on Equipment_Maintenance__c that creates a Service_Ticket__c record, configure Predefined Field Values for the lookup and Priority fields, and add the action to the record page layout.Answer
  2. B
    Create a Global Quick Action of type Create a Record targeting Service_Ticket__c, set Predefined Field Values for the Equipment_Maintenance__c lookup, and add it to the Global Publisher Layout.
  3. C
    Configure Dynamic Forms component visibility rules on the Service_Ticket__c page layout to conditionally expose the Priority field and set its default value based on the parent record.
  4. D
    Create a Custom Detail Page Button on Equipment_Maintenance__c using a custom JavaScript OnClick behavior to execute an API insert call for Service_Ticket__c.

Answer

Create an Object-Specific Quick Action on Equipment_Maintenance__c targeting Service_Ticket__c, configure Predefined Field Values for the parent lookup and Priority fields, and add the action to the page layout.
An Object-Specific Quick Action created on the parent object (Equipment_Maintenance__c) inherently possesses context of the source record. Using Predefined Field Values within the action configuration allows administrators to automatically populate both the parent lookup field (linking the new Service_Ticket__c to the originating Equipment_Maintenance__c record) and standard picklist values such as Priority = 'High' without developer intervention or unsupported JavaScript.

Step-by-Step Solution

1
Analyze action context requirement
Creating a child record from a parent record requires object context to pass the parent ID.
Global actions lack record context, whereas Object-Specific Quick Actions carry the source record ID implicitly.
2
Evaluate field pre-population capabilities
Predefined Field Values on Object-Specific Quick Actions can set target fields (Priority = 'High') and relational fields (Service_Ticket__c.Equipment_Maintenance__c = Equipment_Maintenance__c.Id).
This avoids requiring custom code or unsupported JavaScript solutions in Lightning Experience.
3
Deploy action to user interface
Add the created action to the Salesforce Mobile and Lightning Experience Actions section of the Equipment_Maintenance__c page layout or Dynamic Actions panel.
This exposes the action directly on the record highlights panel for technicians.

Key Concept

Object-Specific Quick Actions with Predefined Field Values
Estimated Time:2m 0s
Rate this question

Topics

Quick Actions, Custom Buttons, and Links

More questions from this topic