Difference between revisions of "Set Defaults on Manual Notify"

From SDU
Jump to: navigation, search
m
m (Step 2. Clear the web cache)
Line 19: Line 19:
 
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.
 
   
 
   
<font color="blue">For r11.x releases </font> publish your changes via the [[Web Screen Painter]]. The process of publishing automatically initiates a [[pdm_webcache]].
+
''For r11.x releases'' publish your changes via the [[Web Screen Painter]]. The process of publishing automatically initiates a [[pdm_webcache]].
  
<font color="blue">For older releases</font> 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]].
+
''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]].
  
  

Revision as of 13:47, 18 July 2008

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

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.


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.



To make corrections or additions to this article, select the edit tab above.
To discuss or ask questions about this article, select the discussion tab above.