This webinar covered migrating a Visualforce page to Lightning Web Components (LWC), using events for inter-component communication, and exposing the LWC application through a Visualforce page using Lightning Out. Specifically, the presenters took an existing Visualforce page and recreated it with LWC. They used events to refresh parent components when data changed. They then built an Aura component to wrap the LWC application and exposed it via a Visualforce page, allowing it to be used in a public site. The key takeaways were that LWC are useful, events enable communication between components, and wrapping LWC in Aura allows exposure via Visualforce.
1. Live Coding with Salesforce Developers
Oct 15, 2019
Visualforce to Lightning Web Components: Events and Lightning Out
with Brian Kwong and Kevin Poorman
2. Have Questions?
● Don’t wait until the end to ask your question!
● Technical support will answer questions starting now.
● Respect Q&A etiquette
● No need to repeat questions. The support team is working their way
down the queue.
● Please take the pop-up survey at the end of the webinar.
● Close out of the webinar and rejoin if you experience audio/visual issues.
3. This session is being recorded! The video will be posted to YouTube & the
session recap page (same URL as registration).
Salesforce Developers
Salesforce Developers
Salesforce Developers
@salesforcedevs
Go Social
4. This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the
assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we
make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber
growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief,
any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services.
The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new
products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays
in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the
immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth,
new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger
enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form
10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important
disclosures are available on the SEC Filings section of the Investor Information section of our Website.
Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be
delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available.
Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
Statement under the Private Securities Litigation Reform Act of 1995
Forward-Looking Statement
5. Introductions
Explanation of the problem
Coding our solution
Recap
Talking about what we’re gonna talk about. #meta
What’re we coding today?
6. Brian Kwong
Developer Evangelist, Salesforce.com
Plays guitar badly
Live Coding with Brian Kwong & Kevin Poorman
Kevin Poorman @codefriar
VP of Delivery and Operations at
Better Partners
Didn’t attend Hogwarts
7. Visualforce to LWC
Migrating visualforce pages to app pages with Lightning Web Components
Exposing the new apps through Lightning Apps
Inter-component communication using events
What does that mean?
9. This way to the code
In case Kevin forgets, this is where we (finally) get away
from the slides and to the coding bits.
10. Today we
Took a Visualforce page and re-created it with Lightning Web Components
Used events to refresh parent components
Built a lightning out Aura component, and exposed our LWC app via a Visualforce page
mAd3 n0 Tyops.
11. Key Takeaways
Lightning Web Components are cool.
Communicating between components is done via events
Wrapping your LWC in an aura component allows you to expose your LWC apps in a public site
page via visualforce
Remember this!
13. Next week on #CodeLive
Until then, catch up on previous episodes
Code Reviews with Ryan Headley
Until then, hit https://trailhead.salesforce.com for past episode videos!
Do you have what it takes to defeat Iron Coder Winkelmeyer?
http://bit.ly/2MuPDTd
14. Q & A
Try Trailhead: trailhead.salesforce.com
Join the conversation: @salesforcedevs
15. Survey
Your feedback is crucial to the success of our
programs. Please fill out the survey at
the end of this session. Thank you!
