Difference between revisions of "Set Defaults on Manual Notify"
m |
(→Step 1. Edit the nf.htmpl form) |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | __NOTOC__ | ||
| + | [[Category:Customizations]] | ||
| + | {{Global Header}} | ||
| + | {{Global Announcement}} | ||
| + | |||
| + | == Overview == | ||
This article provides instructions on how to automatically set the recipients of a [[Manual Notification]] to Affected End User and Group and then have the ability to remove them. | This article provides instructions on how to automatically set the recipients of a [[Manual Notification]] to Affected End User and Group and then have the ability to remove them. | ||
| − | == Step 1. Edit the nf.htmpl form == | + | == Procedures == |
| + | === Step 1. Edit the nf.htmpl form === | ||
In the head of nf.htmpl, look for the following code: | In the head of nf.htmpl, look for the following code: | ||
<source lang="javascript"> function initNames() { | <source lang="javascript"> function initNames() { | ||
| Line 15: | Line 22: | ||
For r11.x releases it is recommended that you edit your pages via the [[Web Screen Painter]]. For older releases you must edit the files directly. | For r11.x releases it is recommended that you edit your pages via the [[Web Screen Painter]]. For older releases you must edit the files directly. | ||
| + | For r12.6 release, functionality is found in the Notifications. Add a Requestor and/or Affected End User to Administrator Tab>>Notifications>>Activity Notifications>>Manual Notify>>Object Contact Recipients tab. Adding the Requestor and/or Affected End User objects to this tab will then set those objects as the default Available Recipients on the Manual Notify form. | ||
| − | == Step 2. Clear the web cache == | + | === Step 2. Clear the web cache === |
The final step is to clear Service Desk's cache. The methods vary depending on release. | The final step is to clear Service Desk's cache. The methods vary depending on release. | ||
| − | + | ''For r11.x releases'' publish your changes via the [[Web Screen Painter]]. The process of publishing automatically initiates a [[pdm_webcache]]. | |
| − | + | ''For older releases'' execute [[pdm_webcache]] from a command prompt on the [[Primary Server]]. There is no need to run this command on the [[Secondary Server|Secondary Servers]]. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Latest revision as of 15:36, 17 September 2012
To discuss or ask questions about this article, select the discussion tab above.
Overview
This article provides instructions on how to automatically set the recipients of a Manual Notification to Affected End User and Group and then have the ability to remove them.
Procedures
Step 1. Edit the nf.htmpl form
In the head of nf.htmpl, look for the following code: <source lang="javascript"> function initNames() { <PDM_IF $dob.notify_list.length == 0> // Cope with Netscape's lack of resizing: document.main_form.notify_list.options.length = 0; </PDM_IF></source>and place this code directly below it: <source lang="javascript">if (document.main_form.in_names.value == ){ document.main_form.in_names.value = '$args.customer.combo_name::$args.group.last_name'; document.main_form.in_ids.value = '$args.customer.id $args.group.id'; }</source>
For r11.x releases it is recommended that you edit your pages via the Web Screen Painter. For older releases you must edit the files directly.
For r12.6 release, functionality is found in the Notifications. Add a Requestor and/or Affected End User to Administrator Tab>>Notifications>>Activity Notifications>>Manual Notify>>Object Contact Recipients tab. Adding the Requestor and/or Affected End User objects to this tab will then set those objects as the default Available Recipients on the Manual Notify form.
Step 2. Clear the web cache
The final step is to clear Service Desk's cache. The methods vary depending on release.
For r11.x releases publish your changes via the Web Screen Painter. The process of publishing automatically initiates a pdm_webcache.
For older releases execute pdm_webcache from a command prompt on the Primary Server. There is no need to run this command on the Secondary Servers.
