Ability to assign email templates more specifically to events
Currently templates are limited to functions of event eg 'event has been submitted'- no matter what the event is. So an event that a student needs to sign off will say the same thing that an event an assessor needs to sign off- making it difficult to provide instructions/ clarity within the email template as to what that person is doing and why. It would be useful to be able to specify this eg if X event is being submitted (to student) then use this template, if Y event is being submitted (to assessor) then use this other template.
Comments: 3
Oldest
•
Newest
•
Most likes
•
Fewest likes
-
29 Feb, '24
RafEmail templates linked to Events or Blueprint would be extremely useful. For example, when a student receives a very poor assessment in a WBA, the academic team would like to be alerted to be able to follow up straight away.
-
25 Jul, '24
PaulI agree with this.
This is becoming more of an issue as our cohort grows using just a few templates to cover a wide range of event types I am creating and already have to be very careful with wording to cover a range of recipient types (student, tutor, observer, nhs partner etc)
It would be great if we could build an email template ourselves (by picking fields like we do for reports?), or have a way to put in a request for new email templates through service request. -
29 Jul, '24
PaulWith regards to my previous comment, i would like to have flexibility to customise a template similar to what i have put in below.
Dear %fullname%
%actor_fullname% has submitted their event %event_type% (%event_name%?) and has submitted it to you for review.
You can view the content below, and use this for further conversations and feedback with your student.
Thank You
%organisation%
%previous_section%
(%field_a%)
(%field_b% )
(%field_m%)
(%field_y%)
Using the generic template results in any (ALL) conditional fields being applied to the generated email which can make it a very long and confusing email to the end user. I use the current email for 8 other simpler workflows and am happy with the detail it provides.
I will train the users to ignore the conditional fields but It's all about user experience, and it will not be optimal in this case, with negative feedback as a result. There are many good features about the system, but is let down when these end user issues surface