Sometimes we get students that drop by for ad-hoc appointments. That is, they get to have a meeting with an advisor without a pre-booked appointment, perhaps due to some urgent and/or sensitive circumstance (so no pre-defined Walk-in availability). Our advisors would still like to record these appointments after meeting the students. There is nothing preventing them from setting up appintments in the past, which is good, but what we do not want is the confirmation e-mail that is automatically sent to the student.
Any tips on where to look for a solution to this issue?
It is undesirable for Student Success Hub to send an appointment confirmation email to a student for an appointment that an advisor creates after the meeting has already taken place (i.e. past appointment entered retroactively).
I've found a workaround for this scenario - however, it does require assistance from the sysadmin.
Before the advisor creates a past appointment, they should contact the sysadmin and ask to be temporarily added to the 'usernames to exclude' list for this trigger handler: sfal.AttendeeCreationEmail_TDTM.
While the advisor is on that exclusion list, appointments they create will not trigger the appointment confirmation email. After the advisor has finished creating the appointment, the sysadmin can remove their username from the trigger handler to resume normal operations.