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...)
 
m
 
(16 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
__NOTOC__
 
[[Category:Customizations]]
 
[[Category:Customizations]]
−
This article provides instructions for setting the default value of Priority and Impact to <empty>.
+
{{Global Header}}
 +
{{Global Announcement}}
  
−
== Step 1. Create the trigger ==
+
== Overview ==
−
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.  
+
This article provides instructions for setting the default value of Priority and Impact to &#60;empty&#62;.
  
−
<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.
+
== Procedures ==
−
<!--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-->
+
=== Step 1. Modify Schema ===
−
''Note: This code will work for all ticket types.''
+
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 file|.mod]] anything you like, but it is recommended that it be preceded with a 'z'. Take the code you need from the examples below.
 +
<source lang="text">MODIFY chg impact
 +
{
 +
  ON_NEW DEFAULT null;
 +
};
  
−
<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'.
+
MODIFY chg priority
 +
{
 +
  ON_NEW DEFAULT null;
 +
};
  
−
<!--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-->
+
MODIFY cr impact
−
''Note: This code works for Requests, Incidents, and Problems. Change the 'cr' to 'chg' for Change Orders or 'iss' for Issues.''
+
{
−
<br><br>
+
  ON_NEW DEFAULT null;
 +
};
  
−
== Step 2. Publish the Schema changes ==
+
MODIFY cr priority
−
The methods used to publish schema changes vary based on the Service Desk release.
+
{
 +
  ON_NEW DEFAULT null;
 +
};
  
−
<font color="blue">For r11.x releases</font>, follow these steps:
+
MODIFY iss priority
−
#Save your Schema changes
+
{
−
#Stop the Service Desk service
+
  ON_NEW DEFAULT null;
−
#Run pdm_publish from a command line
+
};</source>
−
#Start the Service Desk service
+
  
−
<font color="blue">For older release</font> recycle the Service Desk service.
+
=== Step 2. Publish the Schema changes ===
−
<br>
+
For ALL releases recycle the Service Desk service.

Latest revision as of 04:06, 27 July 2008

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.

Overview

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

Procedures

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'. Take the code you need from the examples below. <source lang="text">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;

};</source>

Step 2. Publish the Schema changes

For ALL releases recycle the Service Desk service.

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