Difference between revisions of "Only Assignee can Close"
(→Step 1. Create the script) |
(→Step 2. Create the trigger) |
||
| Line 15: | Line 15: | ||
<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. | <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-->PRE_VALIDATE zmyscript() 113 FILTER(active == 0);<!--c2--></div><!--ec2--> | <!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->PRE_VALIDATE zmyscript() 113 FILTER(active == 0);<!--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 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 PRE_VALIDATE zmyscript() 113 FILTER(active == 0);<!--c2--></div><!--ec2--> | + | <!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->MODIFY cr PRE_VALIDATE zmyscript() 113 FILTER(active == 0);<br><br>MODIFY chg PRE_VALIDATE zmyscript() 113 FILTER(active == 0);<br><br>MODIFY iss PRE_VALIDATE zmyscript() 113 FILTER(active == 0);<!--c2--></div><!--ec2--> |
| − | + | <br> | |
| − | + | ||
== Step 3. Publish the Schema changes == | == Step 3. Publish the Schema changes == | ||
Revision as of 18:13, 14 January 2008
This article provides instructions for implementing custom functionality that prevents anyone but the Assignee of a ticket from closing it.
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).
string zmsg;
if(assignee.userid != cst.userid) {
//Enter your alert message that appears when the if statement is fulfilled
zmsg=format(" Assignee must be the same as the logged in user in order to close %s", ref_num);
set_error(1);
set_return_data(zmsg);
return;
}
}
Note: The example script works for Requests, Incidents, and Problems. Change the 'cr' in the first line of the script to 'chg' for Change Orders or 'iss' for Issues. Also, for Change Orders, change the 'ref_num' to 'chg_ref_num'.
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.
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'.
MODIFY chg PRE_VALIDATE zmyscript() 113 FILTER(active == 0);
MODIFY iss PRE_VALIDATE zmyscript() 113 FILTER(active == 0);
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.
