In this topic Hide
This page is used to create a new eForm email template. These are templates that are sent to support eForm processing via activities in the workflow.
Important! Steps 2 and 3 below for setting the correct domain and group for the email template are crucial.
Field information provided in this help page may also provide guidance when editing an existing template.
This page is only used for eForm emails. For managing email templates for core records and Significant Events, see: Email Templates - RME
Menu path: RME > System > eForm Email Templates (Search) > eForm Email Templates
1. From the RME menu, select System > eForm Email Templates (formerly 'Manage E-Mail Templates').
2. In the Domain dropdown, select the domain for the email template.
3. In the Template Group dropdown, select the type of email template, which indicates where and how the email template can be used. Use the Template Groups table below as a guide.
4. In the toolbar at the top, click the New button. A new page displays with fields to enter the template details based on the selected domain and template group, with further sections for email content.
5. Enter the template details, using the table below as a guide.
Field Label (in layout order) |
Description |
Template Group |
Read only Group selected for the email template (in step 3 above) |
Is Current |
Default: Yes Indicates whether the email template is active • Yes = active and available for selection in workflows • No = inactive; the email template will remain visible in workflows in which it has been included but it will not be available for new workflows |
Send as individual email? |
Default: No Indicates if you want to send group emails based on the defined recipient details (No), or send separate emails to each recipient, for example, to add the individual recipient's first and last name from an RME core record in the email content (Yes) • When
set to Yes, the Recipient Preferred Full Name
item displays in the list of core field values you can add to
the email template subject or body. • When
the Recipient Preferred Full
Name core field value is included in the email content
for individual recipients defined with the Sending
Option of TO (not
BCC or CC),
their Preferred Full Name
from a core record will be added in the resulting email • In
the sent email, each recipient will only see their name (or email
address if the type is Manual).
If, for example, there are five members in the group, five separate
emails are generated, each one personally addressed to one recipient.
Example: "Dear [First name] [Last name]". This means
that recipients will not see who else received the same email. |
Name * |
Mandatory Descriptive name for the template |
Description * |
Mandatory Description for this template to explain its purpose and when it is used |
From * |
Mandatory Email address from which the email will be sent, seen by all recipients |
Failure Notification Email |
Email address to use for notifications when emails are not sent successfully |
Even if this field is not marked as mandatory (red asterisk *), it is required for the email to be sent.
6. To define who the email is sent to, click the Add Recipient button. If you change your mind at any time, click the Cancel button to close the Recipient Add control.
7. In the Sending Option dropdown, select the sending option from the following:
Sending Option |
Description |
BCC |
As a hidden reference Each BCC recipient is hidden from other recipients |
CC |
As a reference All recipients will be visible in the sending details, including any CC |
TO |
Directly to recipients All recipients will be visible in the sending details If Send as individual email? is Yes, individual emails are sent to each identified recipient so only their name and/or email address will be visible.
|
8. In the Recipient Type dropdown, choose how you want to define recipient/s, either Manual, Participant or Personnel, as explained in the table below. Each option will dynamically display different fields.
Recipient Type |
Description |
Manual |
This recipient type allows you to directly enter a specific email address. This may be useful when the recipient is a person who performs the same role and has involvement with all eForms at the particular workflow stage, for example, a particular ethics officer might be cc’d on all email notifications so you could select that specific person as a recipient. 1. In the Recipient Type dropdown, select Manual. 2. In the Recipient: Enter Email Address field that displays, enter the full email address 3. Click the Confirm button at the top of the Add Recipient section. 4. The email address is added to the recipient grid. To remove a recipient from the grid, click the
Delete icon |
Participant (default) |
This recipient type allows you to select recipients from the list of participant roles configured for the selected domain. As these participants are either groups or roles rather than specific people, the email will be sent to those people in the groups or with the role/s you choose who are linked to the eForm at the time the email is being sent. For example, the email may be sent to the Chief and Partner Investigators, or the Primary Investigator or Primary Contact. 1. In the Recipient Type dropdown, select Participant if not already selected. 2. In the Recipient: Select Participant Groups section, expand the tree hierarchies and select one or more checkboxes for the relevant recipient groups under RME Groups and/or Virtual Groups. You can select recipients from lists of committees, panels, RME roles, personnel positions, supervisors, or custom review groups. For more about participant groups, see: . 3. Click the Confirm button at the top of the Add Recipient section. 4. Selected recipients are added to the recipient grid. To remove a recipient from the grid, click the
Delete icon |
Personnel |
This recipient type allows you to select recipients from the list of personnel in the system. You can only select one recipient at a time. This is useful when you know exactly who the recipients will be but are not sure of the email addresses. 1. In the Recipient Type dropdown, select Personnel. A new dropdown displays. 2. In the Recipient - Lookup Personnel lookup field, find a specific person and select them so they appear in this field. 3. Click the Confirm button at the top of the Add Recipient section. 4. The person is added to the recipient grid. 5. To select another recipient, go to step 1 and repeat these steps. To remove a recipient from the grid, click the
Delete icon |
9. When all recipients are added, click the Confirm button to save the details.
If using the HDRCM Workflow – Notify Nominees group for the template, the For Nominee section displays.
In the Notify On dropdown, select when you want an email sent, from these options:
• New – Sends an email via the workflow activity if there is new information in the Nominations eForm
• Update
– Sends an email via the workflow activity if information in the Nominations
eForm has changed
Options display so you can define the change/s to information that will
trigger the email, from Examination Type,
Is Current, Is
Primary and Position.
• New
+ Update – Sends an email via the workflow activity if there is
new information and/or if information has changed in the Nominations eForm
Options display so you can define the change/s to information that will
trigger the email, from Examination Type,
Is Current, Is
Primary and Position.
Ethics meeting templates only
Workflows can be configured to send an email when an eForm application is assigned to a meeting, when an eForm is unassigned, or reassigned to a different meeting. Use one of these sliders if the template will be used to notify recipients about the relevant eForm application assignment:
• Is For Assign
• Is For Unassign
• Is For Reassign
You can only set each of
these for one current template in the list.
10. For templates in the following domain and template group combinations, the Include as Attachments section displays. It includes documents attached to the eForm application in the email:
• Domain: Ethics; Template Group: Meeting
• Domain: All; Template Group: Workflow - General
• Domain: All; Template Group: Workflow - Assessment Review
• Domain: HDRCM; Template Group: Workflow - Notify Nominees
These sliders allow you to control what is attached to the email:
Attachment Option |
Description |
Application PDF |
To include a PDF of the related eForm application with the email, slide it to Yes.
|
Documents |
Enabled if the Application PDF field above is marked as Yes Indicates whether to include all documents attached to the eForm application
For more information about documents, see: RME core - Document upload and management. |
Include Restricted |
Enabled if the Documents field above is marked as Yes Indicates whether to include any restricted documents attached to the eForm application |
This field is mandatory *.
11. In the Subject field, provide a title for the email (mandatory). You can enter your own text and you can also embed core field values from RME. The subject line can be a mix of both.
Core field values
Field values that you can add to the email subject line or body for the domain are listed at the right of the Subject and Body sections. All can be added to the subject line except Application URL as this is a link.
Options include all RME fields in the core records used, linked investigator details, Reviewer Group member lists and the name of the eForm template used to create the eForm. Embedded fields are provided for some fields in the actual eForm, such as Application ID and Title, as well as primary and non-primary personnel linked to the form, and reviewers assigned to the form.
To add a core field value, select to highlight it and click the Add to Subject button. The code to embed the core field value is added to the subject field where you see {@=xxx@}. The actual details will be inserted when the email is sent. See the example below.
For HDRCM, an additional field displays above the core field list: Template Category. Use this to display fields in the selection list for a specific HDRCM eForm template category, as shown in the eForm email template walkthrough below.
This field is mandatory *.
12. In the Body section, enter the content for the email (mandatory). As for Subject above, you can select a core field value to imbed at points in your text. Put the cursor where you want the core value to display and select a core value in the list. Click the Add to Body button. See the eForm email template walkthrough below.
Example
a) In this example body text, each reviewer's name will be inserted at the start, the name of the eForm template used will be added in the next line, and the eForm application details will be inserted in the last paragraph.
Dear {@=Reviewer First Name@},
An application for {@=TEMPLNAME@} has been submitted to the subcommittee for interim approval.
Please log onto ResearchMaster and indicate your approval. The application details are: ID: {@=ECODE@} Researcher: {@=Primary Investigator First Name@} {@=Primary Investigator Surname@} Title: {@=TITLE@}"
b) To add a dynamic link (URL) in the email that will open the eForm application related to the notification, select and insert the Application URL field value. The link text is "Application".
13. Format the email body by using the text editing toolbar. For details, see: Text editing toolbar
14. When you have finished defining the email template, click the Save button in the toolbar.
Result: The template is created with an active status (Is Current = Yes) by default. Where an embedded core field is used in the template, the actual data value of the field for each specific eForm will be inserted at the time the email is prepared for sending.
Click to show or hide: eForm email template walkthrough
Template groups indicate where and how the email template can be used. The table below lists the available template groups alphabetically:
Group |
Domains |
Description |
Email Application |
Contracts Ethics HDR Progress Review HDRCM Research Outputs Research Project Requests
|
Templates that become available when you include the Email Application activity in your workflow in the Workflow Designer The Email Application activity can be used to email a copy of the eForm to defined recipients at any stage in the workflow.
|
Meeting |
Ethics |
Templates used to notify participants about scheduled meetings and assignment of applications to these meetings Separate templates can be created for notification emails when: · An eForm has been assigned to a meeting · An eForm has been unassigned from a meeting · A form has been unassigned from one meeting and assigned to another Meeting group templates are available when configuring the email notifications for the above actions in RME: System > Email Template and selecting Template Group > Meetings for the appropriate domain. |
Reminder Notification |
HDRCM HDR PR |
Templates used for sending reminders of particular pending activities to relevant parties The email template is selected when the reminder notifications need to be sent out. |
Update Overall Due Date Notification |
HDR PR |
Templates used for notifying relevant parties when the overall due date for an eForm record is updated You can set up the notification email template for updating the overall due date in the RMENET system configuration screen of the domain. |
Workflow – Assessment Review |
Contracts Ethics HDR Progress Review HDRCM Research Outputs Research Project Requests |
Templates used solely for the Assessment Review state in a workflow to: · Assign reviewers to an eForm · Un-assign reviewers from a form |
Workflow - Notify Nominees |
HDRCM |
Templates used in the Send Email workflow activity related to an eForm based on the Nominations eForm template category, to send emails to notify new nominees (supervisors, examiners or progress panel members), or notify nominees when their details have changed, as configured in the For Nominees section in the template |
Workflow – General |
Contracts Ethics HDR Progress Review HDRCM Research Outputs Research Project Requests |
Templates used in the Send E-mail workflow activity to automatically create a dynamic email and send it to the defined recipient/s during the workflow process of the eForm The Send E-mail activity may be included in multiple events that occur within the workflow. For example, when an ethics application eForm is approved, there may be workflow activities that: a) Update the status of the form to Approved, and b) Notify the chief investigator and research office via email that the form has been approved. |
Workflow – Update Due Date Notification |
HDRCM HDR PR
|
Templates used for notifying relevant parties when the due date for a workflow state is updated You can associate an email template in this group with a workflow state due date in the Workflow Designer when you setup the Misc properties: Due Date and Update Due Date Email Template. |
"Participant Groups" are used in the system to define users involved in a workflow process. Each of the Participant Groups in a workflow performs different functions in different workflow states. These functions are normally domain-specific and defined by the eForm template.
Participant Groups are further categorised into two different groups: a) RME Groups and ) Virtual Groups.
RME Groups consists of Committees, Panels and roles which are set up and managed in RME and available for selection in RME Designer > Domain Configuration section.
Members of RME Groups remain static and do not change with context as their members are not directly related to any particular eForms or applicants. For example, an ethics committee is set up for ethics-related applications rather than any single eForm application.
In comparison to RME Groups, Virtual Groups are dynamic. Their members change with the context of the data since they are directly linked to an instance of data. For example, members of the Chief Investigators group will change from one eForm to another.
The Virtual Groups available in each domain are slightly different, as outlined in the table below.
Virtual Group |
Domains |
Description |
|
Creator |
Contracts Ethics Research Outputs Research Project Requests (RPR) |
Person who created the eForm from an eForm template The creator is always given the Edit permission automatically when the eForm is in its very first state of a workflow, regardless of the actual state permission configuration. This permission is removed when the eForm moves out from the very first state. |
|
Creator |
HDR PR HDRCM |
Person who created the eForm from an eForm template Similar to other domains above, the creator is always given the Edit permission when the eForm is in its very first state of a workflow, regardless of the actual state permission configuration. This permission is removed when the eForm moves out from the very first state. In HDR domains, there is an additional option. RME administrators and supervisors can create eForms on behalf of students. The Creator virtual group may be configured to allow RME administrators and supervisors to perform actions on these eForms in other states the workflow. |
|
Custom Review Groups |
All |
Groups of reviewers who are to be part of the workflow process but not known at the time the workflow is configured Custom Review Groups give you the ability to add or remove reviewers to the workflow process on the fly when the actual eForm is processed. With the proper security permissions, you can add individuals, all committee/panel members or just a subset of committee/panel members to a Custom Review Group for each eForm. Members of Each Custom Review Group can either have an Executive role or a Member role. People with an Executive role can usually perform administrative tasks while people with a member role can just compete normal reviews. |
|
Examiner |
HDRCM - eForm template category: Examiner Outcome/Examination and Submission |
Person identified as an examiner for a student’s enrolment, linked to an individual Examiner Outcome eForm When a new Examiner Outcome eForm is created from the parent eForm, each identified examiner is automatically linked to this Virtual Group so they can assess the student’s examination/submission. |
|
Examiners |
HDRCM |
People identified as examiners of a student enrolment, linked to a core record, and flagged as an examiner in the Personnel record |
|
Sub-group: Examiner Positions |
Positions are an important factor in controlling eForm access and permissions for workflow activities. This is a list of positions that can be assigned to each examiner in RME core. |
||
Sub-group: Primary Examiner |
There can be only one primary examiner linked to a single eForm record. A primary examiner can also hold an examiner position. When this happens, the security permission assigned to primary will take precedence. |
||
Panel members |
HDR PR |
People identified as progress panel members of student Progress panels manage the progress review of students. |
|
Personnel Positions |
All |
Used to show the relationship of a person to the core record, for example, the investigator position in ethics eForm applications. Positions are set up in RME > Setup > Categories. Different domains use different position categories. |
|
Student |
HDR PR HDRCM |
Postgraduate student whose progress review is being created (automatically allocated) |
|
Supervisors |
Ethics Research Project Requests (RPR) |
People identified as a supervisor of a researcher, linked to a core record |
|
Supervisors |
HDR PR HDRCM |
People identified as a supervisor of a student, linked to a core record |
|
Sub-group: Primary Supervisor |
There can be only 1 primary supervisor linked to a single eForm record. A primary supervisor can also hold a supervisor position. When this happens, the security permission assigned to primary supervisor will take precedence. |
||
Sub-group: Supervisor positions |
Positions are an important factor in controlling eForm access and permissions for workflow activities. This is a list of positions that can be assigned to each supervisor in RME core. |
For full details, refer to the RME Workflow Designer User Guide > Identify participants, and Participant Groups.
Product Key: Modules - Core
Page ID: ADM020M.htm