You're reading from Mastering Salesforce Experience Cloud Strategies for creating powerful customer interactions

Product type Paperback

Published in Oct 2024

Publisher Packt

ISBN-13 9781835466346

Length 328 pages

Edition 1st Edition

Tools

Salesforce

Concepts

Business Management

Table of Contents (22) Chapters

Preface

1. Part 1:Curating a Digital Experience Strategy FREE CHAPTER

2. Chapter 1: Defining Your Digital Experience Strategy

3. Chapter 2: Translating Your Audience and Interactions into Meaningful Technology Features

4. Chapter 3: Technology Component Identification – Which Parts of Experience Cloud Do I Need?

5. Part 2: Infrastructure Setup to Support and Customize Design Strategy

6. Chapter 4: Curating Data Models

7. Chapter 5: Understanding Experience Cloud Templates

8. Chapter 6: When to Use Aura Components, Lightning Web Components, and Lightning Runtime Components

9. Part 3: Human-Centric Development

10. Chapter 7: Leveraging Screen Flows versus Apex

11. Chapter 8: Understanding Inputs – Emails, Chats, and Text Messages

12. Chapter 9: Marketing Automation Setup

13. Chapter 10: Leveraging Case Management and Knowledge Bases

14. Part 4: Site Launch

15. Chapter 11: Security – Authentication, Data Sharing, and Encryption

16. Chapter 12: Monitoring Your Site – Salesforce Native Reporting

17. Chapter 13: Site Launch, Maintenance, and Moderation

18. Part 5: Certifications

19. Chapter 14: Best Practices and Certification Test Preparation

20. Index

Why subscribe?

21. Other Books You May Enjoy

Curating an enterprise architecture map

We might have satisfied Kinley in production, but we’re not done appeasing our other internal stakeholders just yet. Dalbert in marketing needs our Experience Cloud data to plug into his marketing technology (MarTech) stack, and Maggie in finance needs data from franchisee sales and end-consumer purchases to connect to our Enterprise Resource Planning (ERP) finance system. We also can’t forget Anna in quality, who needs the user experience to cleanly connect behind the scenes to internal IT systems such as single sign-on (SSO), our data lake, or any other middleware.

Let’s tackle the potential tech stacks around each of our stakeholders as we begin to design our enterprise architecture map. Every organization is different, and this Architecture Map is intended as an example to inspire you; it is not intended to be seen as gospel or as the sole way to do it.