You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Kind of. Right now, with Registration Email Restriction set to One registration per event, it does not allow additional registration records for the event, unless a previous registration record is in a Canceled or Started status. Our current business process is to mark individuals who did not attend an event as a No-Show. By not excluding No-Show as an option, students are not able to register for a subsequent event.
Describe the solution you'd like
I would like to recommend that the No-Show and Rescheduled statuses be added to the list to ignore. Better yet, I think it would be a better admin experience to be able to configure those statuses to be excluded, perhaps via a Custom Metadata Type, in the event we have custom Registration Statuses we would like the system to ignore when enforcing the Registration Email Restriction feature.
Describe alternatives you've considered
We can change our business process to update the Reg Status to Canceled after an event, however this does not accurately represent what happened for that record. The only other option is to not enforce Registration Email Restriction, and manually clean up duplicate submissions.
Are you willing and interested in being engaged during the development and testing process?
Yes.
The text was updated successfully, but these errors were encountered:
Have you shared this feature idea request in the Trailblazer Community?
https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX000000nDxI0AU
Is your feature request related to a problem? Please describe.
Kind of. Right now, with Registration Email Restriction set to One registration per event, it does not allow additional registration records for the event, unless a previous registration record is in a Canceled or Started status. Our current business process is to mark individuals who did not attend an event as a No-Show. By not excluding No-Show as an option, students are not able to register for a subsequent event.
Describe the solution you'd like
I would like to recommend that the No-Show and Rescheduled statuses be added to the list to ignore. Better yet, I think it would be a better admin experience to be able to configure those statuses to be excluded, perhaps via a Custom Metadata Type, in the event we have custom Registration Statuses we would like the system to ignore when enforcing the Registration Email Restriction feature.
Describe alternatives you've considered
We can change our business process to update the Reg Status to Canceled after an event, however this does not accurately represent what happened for that record. The only other option is to not enforce Registration Email Restriction, and manually clean up duplicate submissions.
Are you willing and interested in being engaged during the development and testing process?
Yes.
The text was updated successfully, but these errors were encountered: