Difference between revisions of "Priority and Impact Default to Empty"

From SDU
Jump to: navigation, search
(New page: Category:Customizations This article provides instructions for setting the default value of Priority and Impact to <empty>. == Step 1. Create the trigger == This step is to create the...)
 
(→‎Step 1. Create the trigger)
Line 2: Line 2:
 
This article provides instructions for setting the default value of Priority and Impact to <empty>.
 
This article provides instructions for setting the default value of Priority and Impact to <empty>.
  
−
== Step 1. Create the trigger ==
+
== Step 1. Modify SChema ==
−
This step is to create the trigger that will initiate the script. The methods used to implement the trigger vary based on the Service Desk release.  
+
<font color="blue">For ALL releases</font> make your schema change by creating a .mod file and placing it in the [[NX_ROOT]]/site/mods/majic directory. Name the .mod anything you like, but it is recommended that it be preceded with a 'z'.
 +
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->&#91;code&#93;MODIFY chg impact<br>{<br> &nbsp; &nbsp;ON_NEW DEFAULT null;<br>};<br>MODIFY chg priority<br>{<br> &nbsp; &nbsp;ON_NEW DEFAULT null;<br>};<br><br>MODIFY cr impact<br>{<br> &nbsp; &nbsp;ON_NEW DEFAULT null;<br>};<br><br>MODIFY cr priority<br>{<br> &nbsp; &nbsp;ON_NEW DEFAULT null;<br>};<br><br>MODIFY iss priority<br>{<br> &nbsp; &nbsp;ON_NEW DEFAULT null;<br>};<!--c2--></div><!--ec2-->
  
−
<font color="blue">For r11.x releases</font> triggers are created via the Schema Designer utility. Simply add the following code as a Site-Defined Trigger to the desired table.
 
−
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->POST_CI val_fieldupdate_site&#40;persistent_id, audit_userid, CHANGED_ONLY, customfield1, customfield2, customfield3&#41; 57 FILTER&#40;EVENT&#40;"UPDATE"&#41;&#41;;<!--c2--></div><!--ec2-->
 
−
''Note: This code will work for all ticket types.''
 
−
 
−
<font color="blue">For older releases</font> triggers are made by creating a .mod file and placing it in the [[NX_ROOT]]/site/mods/majic directory. Name the .mod anything you like, but it is recommended that it be preceded with a 'z'.
 
−
 
−
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->MODIFY cr POST_CI val_fieldupdate_site&#40;persistent_id, audit_userid, CHANGED_ONLY, customfield1, customfield2, customfield3&#41; 57 FILTER&#40;EVENT&#40;"UPDATE"&#41;&#41;;<!--c2--></div><!--ec2-->
 
 
''Note: This code works for Requests, Incidents, and Problems. Change the 'cr' to 'chg' for Change Orders or 'iss' for Issues.''  
 
''Note: This code works for Requests, Incidents, and Problems. Change the 'cr' to 'chg' for Change Orders or 'iss' for Issues.''  
 
<br><br>
 
<br><br>

Revision as of 20:28, 13 January 2008

This article provides instructions for setting the default value of Priority and Impact to <empty>.

Step 1. Modify SChema

For ALL releases make your schema change by creating a .mod file and placing it in the NX_ROOT/site/mods/majic directory. Name the .mod anything you like, but it is recommended that it be preceded with a 'z'.

CODE
[code]MODIFY chg impact
{
   ON_NEW DEFAULT null;
};
MODIFY chg priority
{
   ON_NEW DEFAULT null;
};

MODIFY cr impact
{
   ON_NEW DEFAULT null;
};

MODIFY cr priority
{
   ON_NEW DEFAULT null;
};

MODIFY iss priority
{
   ON_NEW DEFAULT null;
};

Note: This code works for Requests, Incidents, and Problems. Change the 'cr' to 'chg' for Change Orders or 'iss' for Issues.

Step 2. Publish the Schema changes

The methods used to publish schema changes vary based on the Service Desk release.

For r11.x releases, follow these steps:

  1. Save your Schema changes
  2. Stop the Service Desk service
  3. Run pdm_publish from a command line
  4. Start the Service Desk service

For older release recycle the Service Desk service.

Retrieved from "http://greggsmith.net/wiki/index.php?title=Priority_and_Impact_Default_to_Empty&oldid=242"