An Introduction to Ruby on Rails-Action Mailer

The program I wrote for my company can now generate, store, associate and differentiate between leads in the dataset. And now, when someone RSVP’s to a hiring event, they receive a ticket. This ticket contains the event name, the date, the location, the attendee’s name, a confirmation number and most importantly a QR code that contains that attendee’s specific one time password secret key. Once scanned, the specific RSVP instance associated with that otp_secret_key destroys it’s child ticket instance, ensuring someone cannot check in with the same QR code twice.

Note: I will cover QR code generation, encoding and decoding in future blog posts.

Now that I have the tickets being generated with the appropriate data, how can I ensure that the attendee gets their ticket? They will need this ticket in order to be checked in on the day of the event. I was originally generating the tickets in the front end. As soon as they submit their RSVP form, if all the data is valid, their ticket is rendered as a modal, containing all of the pertinent information, including the QR code. While this would work and the QR code would scan and check in the attendee, this means the person would have had to take a screenshot or their ticket modal for later use. This didn’t seem very user friendly. I thought about what I usually experienced whenever I buy tickets…