Section 5 · User Interface · 17% of exam
5.2 Configure Buttons, Links, and Actions for Workflows
Exam objective
Demonstrate the capabilities and use cases for custom buttons, links, and actions.
Buttons, links, and actions let users initiate work from Salesforce. Object-specific actions operate in a record context and can create or update related records, launch flows, or perform other supported tasks. Global actions can be used outside a specific record context for common actions such as creating a record or logging an interaction. Custom buttons and links can navigate, launch supported functionality, or pass context. Select the mechanism that fits the user’s starting point and the information available at that point.
A quick action is useful when a user should complete a focused task without leaving the current record. A flow action can guide a longer interaction or apply branching logic. A standard action may already satisfy the requirement and is usually simpler to maintain. Custom buttons or links may be appropriate for navigation or specialized behavior, subject to current Lightning and mobile support. Legacy URL hacks and unsupported navigation patterns are fragile; use documented actions and navigation mechanisms.
Action layouts determine which fields appear in action dialogs and can be distinct from the main page layout. Predefined field values can reduce repeated entry, but they should not silently override business decisions. Context variables can pass a record ID into a flow. Test whether the action appears in the intended page, app, and form factor, and ensure it is available only to users who can perform the underlying operation. Visibility on a page is not a substitute for permissions. Salesforce Certified Platform App Builder | SU ·26 guide alignment 21 Keep an action’s label specific to the outcome and provide a clear confirmation when the operation is significant. For actions that create or update related records, decide what should happen on cancellation, validation failure, duplicate detection, or missing parent context. Review the end-to-end workflow so that the action does not bypass approval, audit, or required validation controls.
Applied scenario: An account manager wants to create a renewal opportunity while viewing an Account. Add an object-specific action or a flow action that receives the Account record ID, prepopulates only safe and stable values, and asks for the renewal date and amount. Place it where the manager performs the task, and ensure the user has Create access to Opportunity and access to the relevant fields. Test on an account with no existing renewal, one with an existing open renewal, and an account the user can view but not edit. The action should guide the user without creating duplicates or bypassing approval rules.
Design and risk review: An action can appear to work for an administrator while failing for ordinary users because of object, field, or record access. Predefined values can be stale or inappropriate for some record types. Avoid buttons whose URLs expose record identifiers or sensitive values in ways that violate security expectations. Check whether the chosen action is supported on mobile and whether its layout is separate from the page layout. Test cancellation and error feedback, not only the happy path.
Exam lens: First translate the stated requirement into a measurable outcome. Identify the actor, record or object in scope, timing, access boundary, and exception path. Eliminate choices that solve only the visible interface while missing the underlying data, security, or lifecycle requirement. Then compare the remaining supported features by fit, operational complexity, maintainability, and any dependency named in the scenario. A strong answer satisfies the stated need with the least fragile configuration and preserves the platform’s security and governance model. These are study heuristics, not additional official exam rules.
Extra concept: Treat configuration as a system rather than a list of settings. A field may participate in a formula, validation rule, flow, report, permission set, Lightning page, and deployment package at once. Before changing it, identify those dependencies, decide which are intentional, and test the full user journey. This dependency view explains why a locally correct change can still fail after deployment or for a different user. Use Setup dependency tools where available, source comparison, and focused regression checks; no single dependency view is guaranteed to reveal every runtime relationship.
Verification exercise: Turn the lesson scenario into a small test plan before calling the design complete. Record the starting data, the user permissions, the expected outcome, and the evidence that would confirm it. Test one ordinary path, one boundary condition, and one invalid or unauthorized path. Compare the result with the business requirement, then repeat after deployment in the target environment. This catches differences caused by data, activation, page assignment, sharing, or dependencies. Save the test cases with the release notes so another administrator can reproduce the result.
Key takeaways
- Demonstrate the capabilities and use cases for custom buttons, links, and actions
- Choose the platform feature that fits the requirement, data, access, and operating context.
- Test realistic users, exceptions, dependencies, and lifecycle effects before release.
- Official references: https://help.salesforce.com/s/articleView?id=005298964&language;=en_US&type;=1 https://trailhead.salesforce.com/content/learn/modules/lightning_app_builder https://trailhead.salesforce.com/content/learn/modules/flow-basics Salesforce Certified Platform App Builder
- SU ·26 guide alignment 22
