Wine and Sunflowers Ltd

AI-Assisted Study Note

This page brings together public scenario links and AI-assisted research notes for study use. Start with the scenario brief, make your own attempt, and open the spoiler section only when you are ready to compare.

Scenario Snapshot

Field	Detail
Start here	Blog post (canonical)
Scenario source	Community scenario (Ladies Be Architects)
Current status	Live (LBA)
First public date	2018-11 (blog post); PDF created 2018-09-13
Primary source	Open primary source
Coverage available	Scenario brief + Discussion or analysis

Why This Scenario Matters

• This entry is included because it appears in the public CTA scenario corpus and has enough public evidence to track for study use.

Only Open If You Have Attempted the Scenario

The section below contains public follow-up links, board-call material, and AI-assisted notes compiled from those public sources.

Open follow-up links, Q&A, and analysis

Follow-Up Links

• Blog post (canonical)
• Solution Design Session page (workshop version)
• CTAGOF list
• Apex Hours list

Board Insights & Common Pitfalls

Generalized Judge Questions

• Margin Enforcement: “The scenario states >20% gross margin must be enforced. How does your solution prevent a sales rep from closing a deal below that threshold? Where does the logic live — validation rule, Flow, or CPQ?”
• ERP Integration Timing: “Invoices go to ERP monthly but new customers must sync in real-time. How do you design two different integration cadences against the same ERP?”
• Discount Approval: “A discount above 10% needs approval. Walk me through the full approval chain, including what happens to the Opportunity while it waits.”
• Regional Data Visibility: “Sales teams should only see their region’s data. How do you implement this — role hierarchy, territory management, or sharing rules? Justify the trade-offs.”
• Facebook Login for Customers: “You chose Social Sign-On for customers. How do you map a Facebook identity back to a Person Account? What happens when a customer has two Facebook accounts?”

Common Mistakes

• Ignoring the Spreadsheet Problem: The current teams run everything on spreadsheets. Proposing standard Salesforce page layouts without addressing bulk-entry productivity will fail the UX test.
• Single Integration Pattern for ERP: Using one integration pattern (e.g., all real-time) when the scenario explicitly requires both real-time (customers) and batch (invoices/credits monthly, products daily).
• Oversimplifying SSO: Treating internal SSO (Active Directory) and external Social Sign-On (Facebook) as the same design problem.
• Missing Complaint Audit Trail: The scenario has a regulatory requirement for complaint audit trails. Field History Tracking alone may not be sufficient — Shield Platform Encryption or Event Monitoring may be needed.

Strong Patterns

• Multi-Cadence Integration: Designing a clear integration map with real-time (CDC or Platform Events for new customers), daily batch (product sync from ERP), and monthly batch (invoice/credit posting to ERP).
• Person Accounts for B2C: Using Person Accounts to model the 100,000+ consumer customers, with Social Sign-On linking to the Experience Cloud portal.
• Territory Management for Regions: Using Enterprise Territory Management to handle the USA, Australia, South Africa, and UK regional data access requirements.

Strategic Insights

• The “December Freeze” Test: The scenario specifies a December release freeze. Judges will test whether your dev lifecycle strategy accounts for this and how hotfixes are handled during the freeze.
• Scale and Simplicity: With 100,000+ customers and multi-currency requirements across 4 countries, success hinges on keeping the org strategy simple (single org) while demonstrating multi-currency and multi-language awareness.

Additional Notes

• Created by Gemma Emmett (née Blezard), Salesforce CTA and co-lead of Ladies Be Architects.
• PDF attribution: “Property of Ladies Be Architects. Developed independently of Salesforce.”
• Alias: Listed as “Wine & SunFlowers” on the CTA Gang of Four list.
• Contact: emily@ladies-be-architects.com (Emily McCowan, LBA lead).