9. Dynamic Pages
• Configure and add visibility rules for actions and forms on record pages, directly from within the
Lightning App Builder.
• Take advantage of a single assignment model for the Lightning page instead of the dual model of
assigning a Lightning page and a page layout.
Dynamic Forms
• Place fields and sections wherever you want.
• Put fields and sections into accordion components or tabs to significantly improve page load times.
• Use visibility rules to show and hide fields and sections.
• Reduce the number of page layouts you need with component visibility rules
Dynamic Actions
• Add, reorder, and remove actions directly from within the App Builder, with a modern UI and live
preview.
• Use visibility rules to show and hide actions to ensure users see only what is important to each of them,
at a given time.
• Manage the actions on your pages in the Lightning App Builder without touching the page layout editor.
• Reduce the number of page layouts you need with action visibility rules.
Overview
10. 1. Enable Dynamic Forms
2. Upgrade Record Detail Component
3. Add Field Section Component and Field Component
4. Set Field Section Component’s columns and visibility
5. Set Field Component’s UI behavior and visibility
6. Enable Dynamic Actions
7. Add Actions with visibility
How to
1 2
3
4
7
6
5
11. Applicable scenario
Dynamic Forms
• Dynamic visibility by specific field (eg. Dynamic form by Approval Status)
• Combine with Path Component (eg. Look like Path's key fields But can place over 5 fields)
• Visibility control depend to user's specific field value, profile, and permission set
(eg. Only Sales profile user can see specific field)
• UI behavior control with visibility
(eg. Can see the field with edit when status is Draft else see the field with read-only)
Dynamic Actions
• Actions you can use anytime (eg. New contact, new opportunity, new task/event)
• Actions that can be used only under certain conditions
Hidden clone some condition
Hidden approval when record can’t submit
Hidden edit some condition
13. Limitation / Consideration
• Only custom object
• Mobile doesn’t support yet
• Dynamic Action in Beta
• The new/edit screen is also under the control of the dynamic form
• Not supported during record editing
• For mobile, at least one managed page layout is required, and for user experience, the separated
page layout must still be managed
BETA - Features with successful Pilots will often transition to the BETA phase. This involves rolling the feature out publicly for testing.
BETA features might require additional enabling by a System Admin and are accompanied by verbiage that clarifies the feature is
in BETA status. BETA features are normally unsupported or given very limited Support as they are not yet fully functional or finished
features.
16. About Implicit Sharing, Record Locks & Skews
Implicit Sharing
• Parent, Child, Portal, Case, Share groups(High volume)
• Explanation / Demo
Record Locks & Skews
• Overview
• How to identify
• How to handle
* It can be divided into two weeks depending on the amount of content.