Difference between revisions of "Automatically Set System Generated Activities to Internal"
(→Step 2. Create the trigger) |
|||
| Line 1: | Line 1: | ||
[[Category:Customizations]] | [[Category:Customizations]] | ||
| − | This article provides instructions for having system generated Activities set to ''Internal'' so it cannot be viewed by users of the Employee or Customer Interfaces. | + | This article provides instructions for having system generated [[Activities]] set to ''Internal'' so it cannot be viewed by users of the Employee or Customer Interfaces. |
== Step 1. Create the script == | == Step 1. Create the script == | ||
| − | A script is created as an .spl file and placed in the [[NX_ROOT]]/site/mods/majic directory. When the Service Desk service starts, the contents of the majic directory are processed and cached. You can use any naming scheme you like for your .spl file, but it is recommended that the file be preceded with a 'z' for easy identification as a custom file (eg zMyCompany.spl, zcr_scripts.spl, zMyScripts.spl). | + | A script is created as an [[.spl file]] and placed in the [[NX_ROOT]]/site/mods/majic directory. When the Service Desk service starts, the contents of the majic directory are processed and cached. You can use any naming scheme you like for your [[.spl file]], but it is recommended that the file be preceded with a 'z' for easy identification as a custom file (eg zMyCompany.spl, zcr_scripts.spl, zMyScripts.spl). |
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->// Use 'alg' for Requests, Incidents & Problems, 'chgalg' for Changes, and 'issalg' for Issues<br>alg::zmyscript(...) {<br>send_wait(0, this, "call_attr", "internal", "set_val", "1", "SURE_SET");<br>if (msg_error()) {<br>logf(ERROR, "error updating alg internal with 1: '%s'", msg[0]);<br>}<br>}<!--c2--></div><!--ec2--> | <!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->// Use 'alg' for Requests, Incidents & Problems, 'chgalg' for Changes, and 'issalg' for Issues<br>alg::zmyscript(...) {<br>send_wait(0, this, "call_attr", "internal", "set_val", "1", "SURE_SET");<br>if (msg_error()) {<br>logf(ERROR, "error updating alg internal with 1: '%s'", msg[0]);<br>}<br>}<!--c2--></div><!--ec2--> | ||
| Line 14: | Line 14: | ||
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->POST_VALIDATE zmyscript() 111 FILTER(type{->'EVT'});<!--c2--></div><!--ec2--> | <!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->POST_VALIDATE zmyscript() 111 FILTER(type{->'EVT'});<!--c2--></div><!--ec2--> | ||
| − | <font color="blue">For older releases</font> triggers are made by creating a .mod file and placing it in the site/mods/majic directory. Name the .mod anything you like, but it is recommended that it be preceded with a 'z'. | + | <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 file|.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 alg POST_VALIDATE zmyscript() 111 FILTER(type{->'EVT'});<br><br>MODIFY chgalg POST_VALIDATE zmyscript() 111 FILTER(type{->'EVT'});<br><br>MODIFY issalg POST_VALIDATE zmyscript() 111 FILTER(type{->'EVT'});<!--c2--></div><!--ec2--> | <!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->MODIFY alg POST_VALIDATE zmyscript() 111 FILTER(type{->'EVT'});<br><br>MODIFY chgalg POST_VALIDATE zmyscript() 111 FILTER(type{->'EVT'});<br><br>MODIFY issalg POST_VALIDATE zmyscript() 111 FILTER(type{->'EVT'});<!--c2--></div><!--ec2--> | ||
| Line 25: | Line 25: | ||
#Save your Schema changes | #Save your Schema changes | ||
#Stop the Service Desk service | #Stop the Service Desk service | ||
| − | #Run pdm_publish from a command line | + | #Run [[pdm_publish]] from a command line |
#Start the Service Desk service | #Start the Service Desk service | ||
<font color="blue">For older release</font> recycle the Service Desk service. | <font color="blue">For older release</font> recycle the Service Desk service. | ||
<br> | <br> | ||
Revision as of 03:44, 17 January 2008
This article provides instructions for having system generated Activities set to Internal so it cannot be viewed by users of the Employee or Customer Interfaces.
Step 1. Create the script
A script is created as an .spl file and placed in the NX_ROOT/site/mods/majic directory. When the Service Desk service starts, the contents of the majic directory are processed and cached. You can use any naming scheme you like for your .spl file, but it is recommended that the file be preceded with a 'z' for easy identification as a custom file (eg zMyCompany.spl, zcr_scripts.spl, zMyScripts.spl).
alg::zmyscript(...) {
send_wait(0, this, "call_attr", "internal", "set_val", "1", "SURE_SET");
if (msg_error()) {
logf(ERROR, "error updating alg internal with 1: '%s'", msg[0]);
}
}
Step 2. Create the trigger
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.
For r11.x releases triggers are created via the Schema Designer utility. Simply add the following code as a Site-Defined Trigger to the alg (Request Activity Log), chgalg (Change Order Activity Log), or issalg (Issue Activity Log) tables.
For older releases 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 chgalg POST_VALIDATE zmyscript() 111 FILTER(type{->'EVT'});
MODIFY issalg POST_VALIDATE zmyscript() 111 FILTER(type{->'EVT'});
Step 3. 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:
- Save your Schema changes
- Stop the Service Desk service
- Run pdm_publish from a command line
- Start the Service Desk service
For older release recycle the Service Desk service.
