The document discusses the development of org-dependent packages in Salesforce, highlighting the distinctions between first and second generation source of truth. It introduces concepts like 'happy soup,' which refers to the challenges of merging complex components within an org, and presents a sample scenario involving the organization of a bookstore system. Key takeaways include the importance of effective version control and the need for careful management of packages during the development and deployment process.

1. Org Dependent Packages
Packages for the masses
Keir Bowden
https://trailblazer.me/id/bob-buzzard
@bob_buzzard

2. Overview
Sample Scenario
Demo
Developing packages
Takeaways
More information
Agenda

3. Salesforce Org Metadata
All objects, automation, code
Hard to untangle
aka Big Ball of Mud
Happy Soup
It Works!
"These systems show unmistakable signs of unregulated
growth, and repeated, expedient repair."
Brian Foote and Joseph Yoder, Big Ball of Mud.

4. First Generation
Source of truth = Org
All development in Packaging Org
Package uploaded from Org
Teamwork difficult
Second Generation
Source of truth = Version Control
All development in scratch orgs
Package uploaded from local filesystem
SFDX teamwork
More Details - sforce.co/2NgzEfw
Second Generation, Unlocked, Org-Dependent

5. First Generation - Unmanaged
Fire and forget
Cannot upgrade
Change code locally
Second Generation - Unlocked
Can upgrade
Change code locally
Move components in and out of package
Second Generation, Unlocked, Org-Dependent

6. Unlocked/Unmanaged (and managed)
Logically complete
All dependencies satisfied on package upload
Can install into any org
Org-Dependent
Logically incomplete
Dependencies satisfied on package install
Only install into orgs containing dependencies
Generally Available Spring 21!
Second Generation, Unlocked, Org-Dependent
Build on top of happy soup

7. Standalone Packages
Org
"Happy Soup"
Non-dependent
Package
Package installs with/without Happy Soup
Happy Soup refers to Package
Package is independent of orgs
May be installed in many orgs

8. Org-Dependent Packages
Org
"Happy Soup"
Package Refers to Happy Soup
Happy Soup refers to package
Package only installs with Happy Soup
Will fail if dependencies not met
Non-dependent
Package

9. Package "reaches in" -
Nest Lightning Web Components
Access Apex classes
Add to existing sObjects
Dependency is one way
Org cannot access package if not installed
Org-dependent

10. Bookstore System
All stores -
Books
Authors
Publishers
Some stores -
Readings
Sample Scenario

11. Sample Scenario - Lightning App Builder Page
Search Criteria
Matching Books Matching Readings
LMS
Book Search Page

12. Sample Scenario - Objects
Reading
Book
Author

13. Sample Scenario - Apex
Setup Sample Data Setup Sample Data

14. Demo

15. Setup
Push Happy Soup Reset Source Tracking Push Package Code Develop Package Code
Create Scratch Org
Happy Soup
(Push Once, Do Not Change)
Package Code
Happy Soup
Version Control
Package
Version Control
Changes here End up here!
or Create Sandbox
Scratch Org

16. Development
Create Package
Test Package
Version
Develop Package
Create Package
Version
Install Package
Version in Sandbox
Tests
Pass ?
Promote Package
Version
Install in
Production
No
Yes

17. Learn the Salesforce CLI
Allow extra time
Develop -> Create Package -> Test -> Debug cycle
Develop package and happy soup separately
Resist changing installed package
Monitor your package source
Use .forceignore!
Takeaways

18. Developer Guide sforce.co/3qxr5vm
Sample Org Repo bobbuzz.me.uk/LC2021MAIN
Sample Package Repo bobbuzz.me.uk/LC2021PKG
Unlocked Packages Trailhead Module sforce.co/3rTUuR2
More Information

19. Thank You
Keir Bowden
https://trailblazer.me/id/bob-buzzard
@bob_buzzard

20. Questions?
Keir Bowden
https://trailblazer.me/id/bob-buzzard
@bob_buzzard