DTH Development

Is it possible?

Two emails are sent:

- Registrant receives the "thank you email"
- event administrator receives the admin notification email. You can list multiple admin emails for the event (separated by if you need the email sent to more than one admin.

Sorry to dig up an old post but this question has come up again so I thought I would see if there is a way to achieve this. I'll try and explain myself a bit better this time...

When someone registers for an event there are 2 emails that need to go out (both to the registrant) - a thankyou email and a tax invoice. Can't really combine them into 1 email as they are 2 separate things.

At the moment I have it setup so the thankyou email is sent automatically upon registration, and when an admin changes the status of the registration record from Pending to Active the tax invoice email is sent (using the "Status Change Email Notice" field in the component config). This works well but they really want both emails to go automatically.

The only ways I have come up with to achieve this are:
1. Setup a cron job and script to set Pending records to Active every night. It's not hard to update the record in the DB but I don't know how to do it in a way that triggers the email to be sent.
2. Hack the back end code so that it sends 2 emails at once. Not really sure where to start with this.
3. I tried using the "Paid Status Change Email Notice" field in the component config but since all users are paying via credit card im guessing DTRegister is marking the registration record as Paid when it is created?

Any other methods or insights into the above??

anyone?

We have a similar need and I would guess everyone does.

Just to be clear on two concepts I find confusing in the DT Register doc:
To me, a "registrant" is someone who registers himself or a group. It's the person actually carrying out the registration transaction.

A participant is someone who is registered to attend an event. So we end up with the following cases:

• A registrant registers an individual, himself. The registrant is also the participant.
• A registrant registers a group of participants. He may or may NOT be a participant himself.

The use case should be as follow:

When registering an individual, the registrant is also the participant. He should get a single email that happens to contain the invoice.

When registering a group, the registrant may or may not be a participant of the group. Regardless, the registrant but NOT the participants should get the invoice by email, as an invoice typically contains information a company may not want to share with all participants. Participants, on the other hand, should automatically get a confirmation email and the burden should NOT be on the registrant's shoulder to inform all participants they've been registered.

Finally, the function "Email Registrant" may be useful but more important still is a function called "Email participants". Such an email should not only reach the registrants of an event but ALL participants. This would typically be used to notify PARTICIPANTS of a change in the event programming. Again, the burden should NOT be on the registrant's shoulder to forward the email to all participants.

In otherwords

• Rename the "Thanks email" for "Confirmation email"
• The current config setting "Send Confirmation email to ..." is fine and applies to the Confirmation email (no more confusion with Thanks email)
• Add a new email titled "Registration/Invoice email"
• Add a config setting "Send Reg/Invoice email to ..."
• Add a function called "Email participants", for those times when we need to email all participants, including all group members, and not just registrants.

jsneveu's suggestion is fully suppported. It is exactly what we require. We look forward to a response from dthadmin.