HR Case Email Templates showing if different Application

Rob Sestito · ‎07-02-2018

HR Email Templates

Hello SN Comm,

I have been going through email notifications and their templates as I am in the middle of an upgrade/migration from non-scoped to scoped applications. When looking at email notification 'HR Case Opened' it is using the email template, 'sn_hr_core_case.ess.general'. When I open that email template record, it shows the following message:

Can anyone tell me if this is normal or not? I am confused as to why an email template for an HR Case - would show its record as being under the SP application. If anyone is able to answer, that would be great!

Thanks,

-Rob

hollysnyder · ‎07-02-2018

Hi Rob!

You'll notice that there are two similar baseline email templates: sn_hr_core_case.hr.general and sn_hr_core_case.ess.general

The sn_hr_core_case.ess.general email template is in the Service Portal application, because this is the template you would want to use on emails that direct the user to the Service Portal. In the email template, the mail script get_hr_uri is used which generates the URL for the case view on the portal. In the specific example you use, the HR Case Opened email would go to the user who opened the case or the user the case is opened for. They would typically access cases via Service Portal.

The sn_hr_core_case.hr.general email template is in the Core application, because this is the template you would want to use on emails that direct the user to the native UI case view. HR Case Worknoted would be an example of an email notification using this email template. That email would go to the case assigned_to who would access the case via the native UI.

Hope this helps! 🙂

View solution in original post

Robert Duca · ‎04-28-2020

Looks like advanced ref qualifier on the dictionary prevents you from changing this easily..

javascript:'collection=NULL^ORcollection=global^ORcollection=' + current.collection

I had to remove it, update my notification and then add it back.... kinda klunky... was there a better way to do this??