Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Salesforce Anti-Patterns

You're reading from   Salesforce Anti-Patterns Create powerful Salesforce architectures by learning from common mistakes made on the platform

Arrow left icon
Product type Paperback
Published in Nov 2022
Publisher Packt
ISBN-13 9781803241937
Length 206 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Lars Malmqvist Lars Malmqvist
Author Profile Icon Lars Malmqvist
Lars Malmqvist
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Part 1: Technical Anti-Patterns
2. Chapter 1: Why You Need to Understand Salesforce Anti-Patterns FREE CHAPTER 3. Chapter 2: How Not to Mess Up Your System Architecture 4. Chapter 3: How Not to Get Confused about Security 5. Chapter 4: What Not to Do about Data 6. Part 2: Solution Anti-Patterns
7. Chapter 5: Unpicking Solution Architecture Troubles 8. Chapter 6: Keeping Integration Straight 9. Part 3: Process and Communication Anti-Patterns
10. Chapter 7: Keeping the Development Life Cycle from Going off Track 11. Chapter 8: Communication without Mistranslation 12. Chapter 9: Conclusion 13. Index 14. Other Books You May Enjoy

Conventions used

There are a number of text conventions used throughout this book.

Any command-line input or output is written as follows:

@isTest
class dummyTest{
  static testMethod void notRealTest(){
	//assume A is a class with two methods
	A aInstance = new A();
     aInstance.methodA();
 	aInstance.methodB();
	//nothing is done to test anything
  }
}

Bold: Indicates a new term, an important word, or words that you see onscreen. For instance, words in menus or dialog boxes appear in bold. Here is an example: “When building custom solutions on Salesforce, you will generally be using Apex, an object-oriented language closely related to Java. That means you should be following good object-oriented analysis and design (OOAD) practices if you are proposing to build anything non-trivial on the platform.”

Tips or important notes

Appear like this.

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime