Summit-Events-App icon indicating copy to clipboard operation
Summit-Events-App copied to clipboard

[BUG] - Authenticated User unable to create event registration

Open rdblake21 opened this issue 11 months ago • 1 comments

Describe the bug Currently, we're trying to setup the Summit Events through an authenticated experience cloud site. In the case of Higher Ed, someone logs in, sees the event calendar and then when they select an event to register, they have the prefilled information on the registration form. That all works, but when the individual hits "Submit" and gets to the confirmation page, the registration record never appears on the Admin side of Salesforce. When running System Debug, the functionality shows it working like it's supposed to, however, the authenticated individual who submits the form can't create it. The Guest User, this works as expected. This is also with the guest user and the authenticated user all having the same permissions and sharing rules associated to them.

To Reproduce Steps to reproduce the behavior:

  1. Setup an authenticated experience cloud site and associated Summit Events to it.
  2. Provide the authenticated user access to Summit Events functionality, with the same permissions as the Guest User
  3. Select an events and confirm that Summit events is pulling in the authenticated users information, followed by hitting "Submit"
  4. Check inside of Salesforce and see if the Registration has been created.
  5. Open the registration page in an incognito window and register for the event as the guest user.
  6. Check inside of Salesforce and confirm that the guest was able to register.

Expected behavior An authenticated user should be able to have the same experience as the guest user. There is some additional expectation that any matching logic is skipped because we know who the individual is already and the related ContactId is associated to the registration based on the authenticated User.

Org Environment

  • This was tested in Education Cloud with Person Accounts, though matching logic was not enabled.

Additional context The work around is to create the event site NOT on the Experience community, but that then requires authenticated users to re-enter their information.

rdblake21 avatar Mar 05 '25 15:03 rdblake21