Download to read offline
Uploaded byDaniel Peter
Rules-based Record Generation with Custom Metadata Types
The document discusses the use of custom metadata types in Salesforce for generating records based on field values in order to manage complex sales bonus structures. It emphasizes an architect mindset that prioritizes future-proofing, maintainability, and performance. The presentation includes concrete examples and highlights principles such as separation of concerns in software design.
More Related Content
Similar to Rules-based Record Generation with Custom Metadata Types
Rules-based Record Generation with Custom Metadata Types
- 1. Rules-based Record Generation withCustom Metadata Types
- 2. Daniel Peter 🌵 SalesforcePractice Lead, Robots & Pencils 🌵 Salesforce MVP 🌵 Bay Area Salesforce Developer Group Leader 🌵 27x Certified 🌵 @danieljpeter
- 4.
- 5.
- 6. Thank You Organizers& Volunteers!
- 7. Hierarchy of takeaways 7 ConcreteExample Concept Architect Mindset
- 8. Concrete Example In Salesforcehow can I build something on opportunities to help me pay bonuses to my Sales Reps? They all get different bonuses for different things, and it’s always changing.
- 9. Concept Using Custom MetadataTypes you can define a rule set to split, clone, transform values on any object to create records in a child object for various use cases.
- 10. Architect Mindset Simple Future Proof Maintainableby the end user Self-Documenting Scalable Performant Secure
- 11. Sales Bonus Rules DanCactusJack 1 year, 1% 10 years, 10% Before 2020: $500 After 2020: $1000 / Large opps
- 12.
- 17.
- 18. Separation of concerns Incomputer science, separation of concerns (SoC) is a design principle for separating a computer program into distinct sections such that each section addresses a separate concern. https://en.wikipedia.org/wiki/Separation_of_concerns
- 19. Salesforce Object (Opportunity) field SalesforcePlatform Workflow Process Builder Apex Formula fields Future feature? Evergreen? CMDT (Sales Bonus Rules) Sales Bonus Service (Apex) Salesforce Object (Sales Bonus)
- 20. Solution Summary 🌵 Generatesrecords based on field values on other objects, and CMDT definitions. 🌵 Data integrity upserting with Unique Key 🌵 Sharing model decoupling 🌵 Self documenting 🌵 Active / start /end date 🌵 Maintainable by configuration 🌵 Has an escape hatch (Apex)
- 21.