Difference between revisions of "Automatically Set System Generated Activities to Internal"
(→Step 1. Create the script) |
|||
| Line 3: | Line 3: | ||
== Step 1. Create the script == | == Step 1. Create the script == | ||
| − | A script is created as an .spl file and placed in the 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-->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-->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--> | ||
Revision as of 18:07, 13 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_ROOTsite/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).
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]);
}
}
Note: The example script works for Requests, Incidents, and Problems. Change the 'alg' in the first line of the script to 'chgalg' for Change Orders or 'issalg' for Issues.
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 desired table.
Note: This code will work for all ticket types.
For older releases 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'.
Note: This code works for Requests, Incidents, and Problems. Change the 'alg' to 'chgalg' for Change Orders or 'issalg' for Issues.
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.
