589 enhance appointment limits

[DavidCuentasMar]

Critical Changes

• 2 New fields:
  • Enforce_Registrations_Limit__c (Checkbox, Default Unchecked)
  • Appointment_Registrations_Limit__c (Number, Default 9999)
• Access to new fields has been added to the Summit_Events_Registrant permission set

Changes

• Use of AggregateResult in SummitEventsRegisterAppointmentCtlr
• SummitEventsRegisterAppointmentCtlr class removes appointments before rendering them if:
  • Related Summit_Events_Appointments__c has Enforce_Registrations_Limit__c equals to true
  • AND
  • Related registrations are >= Appointment_Registrations_Limit__c
• New fields added to Summit Events Appointment Default Layout
• SummitEventsRegisterAppointment_TEST edited to consider this new scenario

Issues Closed

• Appointment Limits #589

Note

• This PR looks better than 589 enhance appointment limits #599

[tcdahlberg]

Thanks @DavidCuentasMar. This is looking good. I still need to pull it in and test again.

I was thinking about the initial approach you had when we started. It may be that some SEA users might actually want appointment limits to be counted at the event level. I could think of a few event configurations that might work that way. If I were to guess, though, most will want it from the instance level like we have now. In future release we could maybe offer a choice.

Sorry to copy and paste from another pull request but...We have been slowly working on getting person account matching active in the next release, so I've been a bit slow in pulling in PR code and testing. Sorry about that. We had a good testing day yesterday and are pretty confident things are working for a release. We may just release to get person account out the door so we can move on to more fun things like this.

btw. If you want to be a part of the core group SEA meetings connect with me on trailhead or linked in and let me know.