Custom Lightning components: LWC configuration and targets
What a developer configures so a custom component reaches admins: the js-meta.xml file (isExposed, targets, targetConfig properties, objects and form factors), Aura interfaces and design resources, record context for child components, LWC quick actions, and Lightning web components inside Visualforce.
Describe the programmatic customizations available for incorporating custom Lightning components in an application.
~7 min read · 9 practice questions ·
What the exam expects
- Identify the
js-meta.xmlsettings that make a Lightning web component appear in the Lightning App Builder, flow screens, tabs or quick actions, and limit it to objects and form factors. - Expose component properties to admins with
@apiandpropertytags, including picklists and numeric ranges. - Choose between LWC and Aura, and recognise the Aura equivalents (interfaces, design resources).
- Pass record context to nested components, and pick a screen or headless LWC quick action.
- Embed a Lightning web component in Visualforce and show Visualforce in Lightning Experience.
Key terms: js-meta.xml (the configuration file every LWC folder needs); target (a page or container type where the component can be used); targetConfig (per-target settings such as properties and objects); design resource (the Aura file that exposes attributes to builders); Lightning Out (the feature that embeds components in other pages, such as Visualforce).
Key facts
- Detail
isExposedtrue and at least one target
- Detail
- Boolean, Integer, String; the config file wins on mismatch
datasource picklist- Detail
- Type String only
objects tag- Detail
- Only inside a
lightning__RecordPagetargetConfig; no external objects
- Detail
- Can be increased, never decreased
- Detail
- Large only
- Detail
- Lightning Experience record pages only; not the mobile app
- Detail
actionTypeAction and a publicinvoke()
recordId- Detail
- Not set on children; pass it down
- Detail
- Users must allow third-party cookies
Sources for this section (7)
- XML Configuration File Elementsdeveloper.salesforce.com (opens in a new tab)
- lightning__RecordPage Targetdeveloper.salesforce.com (opens in a new tab)
- Form Factorsdeveloper.salesforce.com (opens in a new tab)
- Quick Actions (LWC)developer.salesforce.com (opens in a new tab)
- lightning__RecordAction Targetdeveloper.salesforce.com (opens in a new tab)
- Record Contextdeveloper.salesforce.com (opens in a new tab)
- Components in Visualforcedeveloper.salesforce.com (opens in a new tab)
- Why does an Aura component implementing
flexipage:availableForAllPageTypesshow up as a utility bar item? - When does a Lightning web component receive
recordIdautomatically? - Which
propertyattribute turns a String into a dropdown of fixed values? - Why might an LWC embedded in Visualforce render blank for some users?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Platform App Builder pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 26 lessons of the Platform App Builder guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (9 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams