LEARN. PRACTICE. GROW.Concept and mechanism
A quick action should reduce effort without losing context. Object-specific actions can create records associated with the source object and appear through the relevant layout. Global actions serve entry points independent of a specific record, with their corresponding publisher layout. Each action can present a reduced form and predefined values. These defaults improve input but do not enforce universal rules across every channel. If request source must be controlled, analyze validation, permissions, and other write paths. A button’s existence does not establish that it creates the right record or that the user can access the outcome.
Guided application
Dynamic Forms adds presentation behavior, but hiding fields does not remove data access. Field and field-section visibility are evaluated at different times, which can explain behavior while editing. Confirm mobile support and configuration instead of treating desktop as sufficient proof. A saved Lightning page needs activation and assignment appropriate to app and audience. If a custom component is necessary, agree inputs, outcomes, permissions, error handling, and acceptance with the developer. Test the entire task on the intended device using representative roles, including the created relationship and subsequent access. This evidence supports handover to support better than a privileged demonstration.
A technician opens a service on mobile and creates an assessment. Acceptance checks automatic association, required fields, saved data, and subsequent access. A service name copied into text does not replace the required relationship.
Common pitfalls
Global action assumed contextual; default treated as universal rule; visibility treated as FLS; saved page treated as assigned page.
Related topics: Requirements, access, and platform extensions · Relationships, lifecycle, and reporting · Fields, migrations, and external data
Design the task and confirm its result in the actual usage context. UI, data, and authorization must work together.
Reference: Create Object-Specific Quick Actions · Platform App Builder guide SU 26