Codescience is a founding partner of the Salesforce Product Development Outsourcer program, supporting clients through the full lifecycle of building solutions on the Salesforce AppExchange. The document introduces dynamic interactions, a feature allowing lightning components to communicate and build interactive pages without tight coupling. It discusses benefits, implementation considerations, and future roadmap features while inviting questions and engagement from the audience.

2. Who is CodeScience?
● Founding partner of the Salesforce Product
Development Outsourcer (PDO) Program
● We partner with clients to build solutions on
the Salesforce AppExchange
● Named first Master PDO in 2017
● From design to build to implementation, we
support our clients through the full lifecycle

3. Client success: 300+ Builds

4. Today’s Presenter
Victor Abraham
Technical Architect
CodeScience

5. Agenda
● Introduction to Dynamic Interactions
● Benefits
● Demo
● Considerations
● Roadmap

6. Introduction

7. Introduction
● Provides a point-and-click way for Lightning components to talk to
each other in a Lightning page
● Allows Lightning components to be loosely coupled at run time
without strong dependencies
● Enables administrators to to build interactive Lightning app pages

8. Building blocks of Dynamic Interactions
○ Source : Component that triggers the event
○ Targets : Components that are the targets of the interactions
○ Event: Custom event that is triggered from source component
○ Interaction: Activity that transforms source event and assigns
target component attributes

9. Dynamic Interactions Flow
Source
Component
Dynamic
Interaction
in lightning
pages
Target
Components
Fires custom event with
a payload of relevant
attributes
Event payload attributes
are transformed and
passed as attributes to
target components

10. Dynamic Interactions Implementation
Account List Component
Route Planner

11. Benefits

12. Benefits
● Enables administrators to build highly interactive Lightning pages
● Provides ability to link components at design time in app builder
interface
● Avoids tightly coupling components
● Simpler than alternative ways to get similar result like Lightning
message service, platform events etc.
● Aligned with Salesforce Roadmap. Out of the box components like
listview will soon start firing dynamic interaction events that can
be leveraged to build interactive apps.

13. Demo

14. Considerations

15. Considerations
1. Relatively new feature, roadmap might change
2. Custom components need to include target event configuration to
enable admins to leverage dynamic interactions
3. Try to define dynamic interaction events during planning/
requirement gathering phase
4. Aura components re-render when an interaction targeting them
is triggered
5. After a component’s event metadata is used on a Lightning page
or released as part of a managed package, certain breaking
changes aren’t allowed

16. Roadmap

17. Roadmap (Safe harbor)
● Ability to invoke quick actions
● Navigate to a record
● Trigger custom services
● Out of the box support for standard components
● Support for more types of pages like Lightning record page

18. Mission:
Ensure that no company
navigates Salesforce alone

19. Thank you!
Questions? Feel free to contact us at info@codescience.com.