EventCloud - Project Onboarding

Reading Only

Team Onboarding

You're hired as the sole admin/developer for the "San Francisco Events & Parties" corporation. The Director of Technology and Operations has put together a team to build an Event Management application in Salesforce that they're calling "EventCloud".

The product team has put together user stories outlining the requirements that are needed for the app to go live in production. You're asked to use Flows, Triggers, and/or Validation Rules to build the automation needed for the application. It's totally up to you. Use a combination of clicks and code, or go all in on one.

The requirements will be implemented in your connected org, and Camp Apex will act as your QA (Quality Assurance) team. Once you've built out the requirement, click the "Run Tests" button to verify and validate you've met the requirements.

Project Onboarding

EventCloud will help the event coordination and finance teams oversee the planning and accounting of several events. This includes creating events, tracking sponsorship, sessions, and attendance.

Implementation Details

This is the data model that has been built out for you already. You'll be prompted to install the EventCloud managed package in the UI for the first user story. Take some time to understand this model because you'll be writing automation to read from and update these fields.

Some additional information is available in the Object Manager under the Setup Menu.

Some of the QA tests will create records in bulk. In these scenarios, hundreds of records will be created and updated to put the system under the stress of large data volumes. Whether you choose clicks or code, make sure your automation is bulkified.

Self Testing

Use your Trailhead org to your advantage. Launch the "EventCloud" application from the App Launcher to visualize the requirements before building and for creating your own records to test the automation. You can also write your own debug statements or set up your own debug logs to troubleshoot as you go.

Caveats

Fields like Duration, Net Revenue, etc would be good use cases for formula fields. Other fields may have been good use cases for roll-up fields. However, I chose not to implement them in this way, aiming to shift your attention towards triggered automation using Flows and Apex. There may be other implementation details that could be solved in other ways; if you feel strongly about any in particular, let me know. Otherwise, assume the intent of the project is to focus on developer skills, instead of more traditional admin skills.

This is my second attempt at the project format. Love it, hate it or see issues? Let me know, please. Also, if you like the content & found it helpful, please consider pitching in to help cover Camp Apex's server cost.

I hope this project helps you reach your goals. Good luck!