Checklist progress
0/194Learned
Platform Developer
Study Checklist
Checklist progress
0/194Learned
Given a scenario, prevent user interface and data access security vulnerabilities.
0/11
Given a scenario, display and use custom user interface components, including Lightning components, Flow, and Visualforce.
0/15
Lightning components versus Flow versus Visualforce for custom UI
Learn this conceptVisualforce page hosting surfaces
Learn this conceptVisualforce expressions and merge fields
Learn this conceptVisualforce standard controllers
Learn this conceptVisualforce controller extensions versus custom controllers
Learn this conceptVisualforce standard list controllers
Learn this conceptVisualforce Lightning Experience container and navigation
Learn this conceptVisualforce features to avoid in Lightning Experience
Learn this conceptStandard action overrides with Visualforce or Lightning
Learn this conceptLightning component targets for App Builder pages
Learn this conceptLightning base record forms versus custom data UI
Learn this conceptScreen flow distribution surfaces
Learn this conceptEmbedding a flow in a Visualforce page
Learn this conceptEmbedding a flow in Lightning web and Aura components
Learn this conceptCustom Lightning components as Flow screen components
Learn this conceptDescribe the use cases and best practices for Lightning Web Components, including the framework, benefits, and events.
0/13
Given a scenario, implement Apex to work with various types of page components, including Lightning components, Flow, and Agentforce.
0/5
Prepare for the Exam
Study Community
Ask questions and get the latest info from other Platform Developer studiers.
Lightning Experience always displays a Visualforce page inside Lightning Experience chrome, in an iframe the Lightning app controls, so the page no longer owns the header, sidebar, or top-level browser window. Several Visualforce attributes, tags, JavaScript habits, and action overrides that work in Salesforce Classic have no effect, are blocklisted, or never fire in that container. Avoid those Classic-era patterns, or replace them, when the same page must run in Lightning Experience.