EventCloud - Wrap Up
Reading Only

All tests have passed, business signoff has been captured, and the changes have been deployed to production! Time to celebrate!

Throughout this project, you turned user stories into a technical solution. You were trusted to decide between Flow and Apex and evaluate the technical trade-offs along the way. You also got to practice retrieving records, performing cross-object updates, and implementing validations.

Here are a couple of things you can do to expand on the managed package if you like:

Report and Dashboards

Set these up to visualize your data. Report on the average number of sponsors and attendees per event. Figure out how events rank based on Net Revenue. Report on the average number of sessions or revenue per event.

Sharing and Visibility

Create new permission sets based on user personas and limit object access. For example, a user with the "Finance Manager" permission set can only view most sObjects and fields but can edit Event's revenue and expense fields. A user with the "Event Coordinator" permission set can modify garden and plant records.

Enhance the Requirements

Add your own fields and requirements to the app. For example, build automation that creates a Task for session hosts before their session is about to start. Or send out emails whenever speakers are accepted.

I hope you enjoyed working on this project. Please share your thoughts if you have a few minutes. Positive or negative, I'll take them all.

If you feel like you learned a lot from this course, consider pitching in to help cover server costs or to buy me a cup of coffee