Delightful Events (DE)

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	Discovery index
Scenario source	Community scenario (Flow Republic)
Current status	Live (FR)
First public date	N/A
Primary source	Open primary source
Coverage available	Scenario brief + Solution

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

• Discovery index
• Analysis reference

Board Insights & Common Pitfalls

Generalized Judge Questions

• Spreadsheet Replacement: “How does your solution specifically replace the ‘highly automated spreadsheet’ while ensuring the event organizers don’t lose the speed of bulk entry?”
• RSVP LDV: “With 37.5M RSVPs per year, your table will exceed 100M records in 3 years. How will this impact performance, and what is your specific archiving strategy?”
• Bid Visibility Silos: “How do you ensure that partners can collaborate on a bid with colleagues while remaining strictly blocked from seeing competing suppliers’ bids?”
• Markup Visibility: “The customer must see the price including the markup, while staff sees the base cost. How do you implement this securely using field-level security or separate objects?”
• Event Capacity Logic: “Walk me through the technical flow for the system to ‘suggest up to 10 potential suppliers’ for an event. Is this an LWC filter or an Einstein recommendation?”

Common Mistakes

• Failing the “Spreadsheet” Test: Trying to rebuild a 100-item automated spreadsheet using standard Salesforce Page Layouts, which fails the productivity requirement.
• Missing Junction Objects: Failing to account for the many-to-many relationship between 5,000 suppliers and 1,000 services (Supplier-Service object).
• Vague RFP Security: Allowing partners to see other partners’ bids or client-sensitive information due to an over-simplified sharing model.
• Underestimating RSVP Volume: Storing millions of historical RSVPs in standard objects without suggesting Big Objects or an external data lake for reporting.

Strong Patterns

• LWC Grid for Productivity: Using a custom LWC with a grid-like interface to mimic spreadsheet efficiency for bulk event service entry.
• CPQ for Complex Markup: Leveraging Salesforce CPQ to handle the complex tiered markup and variable service charge requirements natively.
• MuleSoft RSVP Ingest: Using MuleSoft to aggregate and buffer the 2,500 RSVPs per event hitting Salesforce from the CountMeIn (.NET) system.

Strategic Insights

• UX-First Board: In Delightful Events, judges care deeply about the User Experience (UX). You must prove the new system is as fast as the “beloved” spreadsheet it replaces.
• Collaborative Bidding: Success hinges on a robust Partner Portal strategy using Account Relationship Data Sharing or Apex Sharing to allow partner-to-partner collaboration within a bid.

Additional Notes

• Global event management scenario focusing on complex RFP/Bid processes, global logistics, and high-volume guest RSVPs.