What is the Event Registration Submission (ERS) object and why is it important?
- Never lose registration data or payments
- Provide a better experience for your attendees
- Easily troubleshoot issues
- Click on the App Launcher icon.
- Type in and select the Events (Admin) app.
- Click on the Event Registration Submissions tab.
Here is where you'll find all the registration records from every event. You probably aren't seeing any at this moment, but register for one of the sample events and then come back.
Here is an example of an Event Registration Submission record:
All of the attendee data is saved here. Their name, email, the ticket they selected, etc..
Why is this object important? It's important because if an event registration submission fails for whatever reason, you want to know why and fix it so the attendee gets a confirmation email.
Here is an example of a failed Event Registration Submission record:
To prevent issues with Event Registration Submission processing during times of high concurrent registrations, automatically scheduled ERS batch processing via the Events (Admin) page will occur.
A protected custom setting with a default value at "Off" was added and can only be changed from the Events (Admin) page. The public custom setting has been deprecated.
- Identify and fix the issue defined in the
- Check the
- Click Save.
This will reprocess the Event Registration Submission record and create the Attendee record.
Want to be notified when an Event Registration Submission record fails? You have come to the right place.
By default, we have enabled this workflow to send the user who authorized events an email when an ERS fails.
If you want to change who receives the notification:
- Navigate to Setup.
- In the Quick Find, search for and select "Workflow Rules."
- Select the Blackthorn | Events ERS Failed workflow.
- Click on the Email Alert.
- Click the Edit button.
- Update the recipients or enter an additional email.
When an attendee checks out for an event, many records are created and updated automatically. The below flow gives you insight on our execution order so you know when to interact with the Attendee object for your custom processes and flows.
An Attendee record is created.
- The Attendee record relates to the Contact, Lead, or Person Account and the Event.
- Registration Status is set to Registered.
Answers to custom questions are processed through the Form Submission object and related to the Attendee.
Sales document (Invoice) & line items are created.
- The contact/lead/person account, status, subject line, and additional fields are set on the Sales Document.
The card information is sent immediately to the Payment Gateway. A token is received (PCI compliant).
The completed transaction and payment method are saved in Salesforce. Initially, they are orphan records because the Event Registration Submission hasn't processed to connect the payment with the registration invoice.
Once the ERS is processed, the Transaction is updated with the related Invoice.
Draft: This is used when the attendee has not completed the checkout.
To Process: This is used when the checkout is completed and the record is submitted for processing.
Failed: This is used when there is issues submitting the ERS record.
Completed: This is used when the ERS record is processed successfully.
Updated 3 months ago