Summer 23 - French Gathering

1. Summer ʼ23
French Gathering
Le 29/06/2023 18H30

2. This presentation contains forward-looking statements about the Company’s financial and operating results, which may include expected GAAP and non-GAAP financial and other operating and
non-operating results, including revenue, net income, earnings per share, operating cash flow growth, operating margin improvement, expected revenue growth, expected current remaining
performance obligation growth, expected tax rates, stock-based compensation expenses, amortization of purchased intangibles, shares outstanding, market growth, environmental, social and
governance goals, expected capital allocation, including mergers and acquisitions, capital expenditures and other investments, expectations regarding closing contemplated acquisitions and
contributions from acquired companies. The achievement or success of the matters covered by such forward-looking statements involves risks, uncertainties and assumptions. If any such risks or
uncertainties materialize or if any of the assumptions prove incorrect, the Company’s results could differ materially from the results expressed or implied by the forward-looking statements it
makes. The risks and uncertainties referred to above include those factors discussed in Salesforce’s reports filed from time to time with the Securities and Exchange Commission, including, but not
limited to: risks associated with our ability to successfully integrate Slack Technologies, Inc.’s operations; our ability to realize the anticipated benefits of the Slack Technologies, Inc. transaction; the
impact of Slack Technologies, Inc.’s business model on our ability to forecast revenue results; disruption from the transaction making it more difficult to maintain business and operational
relationships; the impact of, and actions we may take in response to, the COVID-19 pandemic, related public health measures and resulting economic downturn and market volatility; our ability to
maintain service performance and security levels meeting the expectations of our customers, and the resources and costs required to avoid unanticipated downtime and prevent, detect and
remediate performance degradation and security breaches;
our ability to secure and costs related to data center capacity and other infrastructure provided by third parties; our reliance on third-party hardware, software and platform providers; the effect of
evolving domestic and foreign government regulations, including those related to the provision of services on the Internet, those related to accessing the Internet, and those addressing data
privacy; current and potential litigation involving us or our industry, including litigation involving acquired entities such
as Tableau; regulatory developments and regulatory investigations involving us or affecting our industry; our ability to successfully introduce new services and product features, including any efforts
to expand our services beyond the CRM market; the success of our strategy of acquiring or making investments in complementary businesses and strategic partnerships; our ability to compete in
the market in which we participate; the success of our business strategy and our plan to build our
business; our ability to execute our business plans; our ability to continue to grow unearned revenue and remaining performance obligation; the pace of change and innovation in enterprise cloud
computing services; the seasonal nature of our sales cycles; our ability to limit customer attrition and costs related to those efforts; the success of our international expansion strategy; the demands
on our personnel and infrastructure resulting from significant growth in our customer base and operations; our dependency on the development and maintenance of the infrastructure of the
Internet; our real estate and office facilities strategy and related costs and uncertainties; fluctuations in, and our ability to predict, our operating results and cash flows; the variability in our results
arising from the accounting for term license revenue products; the performance and fair value of our investments in complementary businesses through our strategic investment portfolio; our
ability to protect our intellectual property rights; our ability to develop our brands; the valuation of our deferred tax assets and the release of related valuation allowances; uncertainties regarding
our tax obligations in connection with potential jurisdictional transfers of intellectual property; uncertainties regarding the effect of general economic conditions; and risks related to our debt and
lease obligations.
Forward-Looking Statements
031621

3. Margaux Canales
Bertrand Rousset
(Lyon - Admin Group)
Mohamed EL Moussaoui
(Paris - Architect Group)
Hugo Rosario
Marjolaine Colmart
(French Riviera - User Group)
Simon Lafont
Benjamin Serra
(Montpellier - Admin Group)
Julie Boncour
Yohann Chevreux
(Nantes - Admin Group)
Jean-Michel Mougeolle
(Paris - Admin Group)
Yosra Saidani
Doria Hamelryk
(Paris - WIT Group)
Thierry Trouin
Fabrice Challier
(Toulouse - User Group)
Frédérique Mounier
(Lyon - WIT Group)
Fabien Taillon
Thomas Paraiso
(Paris - Developer Group)
Julien Lemaire
(Lille - Admin Group)
Elodie Loiseau
(Aix-en-Provence - Admin Group)
Arnaud Sourdillon
(Lyon - Architect Group)
Julien Coatelen
(Paris - Marketing Cloud Group)
Jean-Marie Vital
(Paris - Non Profit User Group)
Alexandre Riuz
Francois Perret
(Paris - Marketer Group
-Pardot)

5. Identify Features
by User
Pardot
Admin
Developer

6. Visit salesforce.com/releases
Watch the demo videos
Take the Release Highlights Trail
(Coming soon)
Dive into the detailed Release Notes
Join the Release Readiness
Trailblazers Community Group
1
2
3
4
5
How do I Learn More?

7. Table of Contents
Sales Service Marketing Commerce Analytics
MuleSoft Platform - Build Platform - Automate Platform - Secure
Financial Services Health Manufacturing
Automotive
Public Sector
Communications
Media
Energy & Utilities
Education
Consumer Goods
Net Zero Customer Success
Slack
Data Cloud
Nonprofit

8. Development

9. Syntax :
● System.Label.get(namespace, label, language)
Access Labels in Apex Dynamically
1
2
If not found throw an exception! (not return null)
3

10. This ability is limited to SOQL queries via the REST and SOAP query calls on standards
and custom objects (API Only)
SELECT Name,
(SELECT LastName,
(SELECT AssetLevel,
(SELECT Description,
(SELECT LineItemNumber FROM WorkOrderLineItems)
FROM WorkOrders)
FROM Assets)
FROM Contacts)
FROM Account
Query Five Levels of Parent-to-Child Relationships in
SOQL Queries

11. SELECT Name,
(SELECT LastName,
(SELECT Subject,
(SELECT CommentBody FROM CaseComments)
FROM Cases)
FROM Contacts)
FROM Account
Query Five Levels of Parent-to-Child Relationships in
SOQL Queries (four for the sample) ?q=SELECT Name,(SELECT LastName, (
SELECT Subject,
(SELECT CommentBody FROM CaseComments) FROM Cases)
FROM Contacts) FROM Account

12. import { RefreshEvent} from 'lightning/refresh';
//Call this event to refresh Apex without reload the page
this.dispatchEvent(new RefreshEvent());
RefreshView API (lightning/refresh)

13. ● Light DOM -> Enable Third-Party Integrations
● RefreshView API (lightning/refresh)
● Track the Publishing of Platform Events with Apex Publish Callbacks
● Transfer Package Ownership to a Different Dev Hub
● Lightning Web Security (LWS) for Aura components
● Quickly Create Full Sandboxes (hyperforce)
Generally Available

14. LWC : Set Dynamic Values for the Slot Attribute

15. LWC : Set Dynamic Values for the Slot Attribute (Avec un exemple)
Child LWC
<template>
this part is filled within my child lwc
<slot name="part1">Default value</slot>
this part is filled within my child lwc
<slot name="part2">Default value 2</slot>
this part is filled within my child lwc
<slot name="part3">Default value 3</slot>
this part is filled within my child lwc
</template>
Parent lwc (before summer 23)
<template>
<c-named-slots>
<template if:true={part1}>
<span slot="part1">{information}</span>
</template>
<template if:true={part2}>
<span slot=" part2">{information}</span>
</template>
<template if:true={part3}>
<span slot="part3">{information}</span>
</template>
</c-named-slots>
</template>
Parent lwc (after summer 23)
<template>
<c-named-slots>
<span slot={partName}>{information}</span>
</c-named-slots>
</template>

16. Track the Publishing of Platform Events with Apex Publish Callbacks
Tracking failure
Tracking Success

17. Platform Event tracking ( Enfin !!!!) 1/3
Evolution de l’objet PlatformEventUsageMetric
Nouveaux champs :
- Client : un id par client s’abonnant à un event
- EventName : le type de l’événement
- EventType : custom ou standard event
- UsageType : Delivery or publish
Nouveau Filtre :
TimeSegment : Daily , Hourly ou FifteenMinutes (permet de grouper les
informations plus finement si besoin)
Nouveau Timing pour les snapshot
( qq minutes d’attente désormais et plus 1 jour)

18. Platform Event tracking ( exemples) (2/3)
Avant la summer : select EndDate,Name,StartDate,Value FROM PlatformEventUsageMetric
Après la summer : select EndDate,Name,StartDate,Value,Client,EventName,EventType,UsageType FROM
PlatformEventUsageMetric WHERE TimeSegment='Daily'

20. Platform Event tracking ( petits soucis) (3a/3)
Avant la summer : select EndDate,Name,StartDate,Value FROM PlatformEventUsageMetric
Après la summer : select EndDate,Name,StartDate,Value,Client,EventName,EventType,UsageType FROM
PlatformEventUsageMetric WHERE TimeSegment='Daily'
Requêtes executées sur la
meme org mais avec 2 outils
différents.
Delivered : 136
Published : 34

21. Platform Event tracking ( petits soucis) (3b/3)
- Activer l’option demande de passer par un livraison package.xml et rien ne montre dans l’UI que l’option est
active !!!!
- Une fois activée, seules les événements post activation sont affichés en api 58
- Perte de compatibilité des requetes en api 58 :
WHERE TimeSegment='XXXX' obligatoire desormais
- Il faut lire la doc et il faudra surement la relire pour bien comprendre comment tout marche (Depuis quand
on doit lire une doc !!!)
Conclusion :

22. Base Lightning Component Internal DOM Structure Changes
for Future Native Shadow Support
Lightning Base Components

23. Develop Offline-Ready LWCs
Possibilité de développer des composants offline pour Salesforce Mobile, avec un certain nombre de limitations
→ https://developer.salesforce.com/docs/atlas.en-us.244.0.mobile_offline.meta/mobile_offline
Lightning Base Components

24. ● Query any list of records you want,
order them, group them
● no need to write any Apex
● respects user Field Level Security
● use the same shared Lightning Data
Service cache
GraphQL Wire Adapter en Beta

25. ● Create Component Visibility Rules in Experience Builder
○ Équivalent des règles de visibilité d’App Builder pour Experience Builder
Experience Cloud

26. ● Create Custom Property Types and Editors for
Lightning Web Components in LWR Sites
○ Gérer la configuration d’un LWC dans Experience Builder
avec n’importe quel design
○ Section de paramétrage = un LWC spécifique
○ Autrement dit: un LWC utilisé pour paramétrer un autre
LWC dans Experience Builder
○ Existe déjà dans Flow Builder, rien encore dans App
Builder 😢🤞
Experience Cloud

27. Sales

28. Quotes without Opportunities
Close deals faster
Customer Need
Organizations want to fast-track deals by creating quotes without being
required to create an opportunity first, speeding up delivering proposals to
their customers for review.
Solution / How To Configure
Sales users in Sales Cloud can create quotes with or without opportunities.
Sales reps still have the option to associate the quote to a customer account.
A new Account for Quote field saves this association. Admins enable feature
via Org Pref, configure sharing settings.
Use Case
Create Quote with/without Opportunity
Select Quote Account values for Quotes created without opportunity
Ability to change Quote Owner
Impact
Org scalability - no longer create dummy Opportunities for Quotes

29. Customer Need
Sales organizations create multiple opportunities that represent the same
deal in order to represent the deal by product mix, resulting in complex
implementations.
Solution / How To Configure
Enable an Opportunity Product Split for an Opportunity Split type and add
the Splits Component to Opportunity layouts.
Use Case
Sales users can define splits by product line item.
Users can specify team members and their credit for each product in the deal.
Flows and triggers can also be leveraged to create an opportunity product
split.
Impact
Faster time to value
Scalability in Opportunity implementations
Opportunity Product Splits
Team Selling by Product Mix
Sales Cloud Enterprise &
Unlimited Editions

30. Mobile

31. Salesforce mobile app plus
Same App
Require an extra license
Support LWCs for offline usage

32. Sharing & Access

33. User Access Policies [Open Beta]
Apply User Access Automatically or in Mass
Customer Need
Easily grant or revoke user access to permission sets, permission set groups,
permission set licenses, package licences, groups, and queues.
Solution / How To Configure
Enable in user management settings. Once enabled you will be able to
configure up to 20 User Access Policies in an active state or as many as
needed for mass migration.
Use Case
Identify users by attributes on the user record, user entitlements, or set an
active user access policy to apply access when users are created or updated.
Impact
Admin Efficiency
UE & EE
only

34. Account Engagement
Innovations

35. Data Cloud Integration
Easily integrate Account Engagement and Data Cloud
Customer Need
Leverage the power of Data Cloud to create smarter audiences that can be used in
Account Engagement for B2B marketing.
Solution / How To Configure
Connect Account Engagement business units in Data Cloud Setup and create a data
stream. Marketers then create segments in Data Cloud, connect those segments to a
dynamic list in Account Engagement, and use that list in any marketing or automations
in Account Engagement.
Use Case
● Use more 3rd party data from Data Cloud for Account Engagement marketing
(e.g. ERP purchase data to cross-sell)
● Use more Salesforce data for Account Engagement marketing (e.g. use line
item object in a multi-product order for cross-sell)
● Enable better account-based segmentation
● Create a more complete 360 degree view of the customer B2B with marketing
data from Account Engagement in Data Cloud
Impact
Targeted audiences for marketing efforts
Better engagement
All Account Engagement Editions
EE+ Only Salesforce Editions

36. Flow Enhancement

37. Process Builder Is on the Brink of Death!
● Migrate to Flow Tool Supports Scheduled Actions of Process
Builder
● Process Builder Creation Disabled

38. Flow UI Changes

39. Flow User Permission Changes

40. ● Reactive Components in Flow (Beta)
● Http Callout ( POST )
● Flow Data Table Search Bar
● Enhanced Send Email Flow Action

41. The future of reactivity

42. Thank You