Difference between revisions of "Only Assignee can Close"
(→Step 1. Create the script) |
(→Step 1. Create the script) |
||
| Line 8: | Line 8: | ||
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->cr::zmyscript(...) {<br>string zmsg; <br>if(assignee.userid != cst.userid) {<br>//Enter your alert message that appears when the if statement is fulfilled<br>zmsg=format(" Assignee must be the same as the logged in user in order to close %s", ref_num); <br>set_error(1); <br>set_return_data(zmsg); <br>return; <br>} <br>}<!--c2--></div><!--ec2--> | <!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->cr::zmyscript(...) {<br>string zmsg; <br>if(assignee.userid != cst.userid) {<br>//Enter your alert message that appears when the if statement is fulfilled<br>zmsg=format(" Assignee must be the same as the logged in user in order to close %s", ref_num); <br>set_error(1); <br>set_return_data(zmsg); <br>return; <br>} <br>}<!--c2--></div><!--ec2--> | ||
| − | ''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.'' | + | ''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'." |
<br><br> | <br><br> | ||
Revision as of 04:05, 13 January 2008
This article provides instructions for making a field conditionally required.
In the steps that follow, the example code is used to ensure that only the ticket's Assignee has permissions to close the ticket.
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).
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.
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 'cr' to 'chg' for Change Orders or 'iss' 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.
