Difference between revisions of "Make a Field Conditionally Required"
(→Step 1. Create the script) |
|||
| Line 36: | Line 36: | ||
== See Also == | == See Also == | ||
| − | [[if statements]] | + | [[Example if statements]] |
Revision as of 19:06, 13 January 2008
This article provides instructions for making a field conditionally required. The example that follows makes a field conditionally required when a ticket is being closed. However, the concept of this customization could be expanded to make a field required only if the condition has been fulfilled.
Contents
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;
//Enter your if statement
if(is_null(string1)) {
//Enter your alert message that appears when the if statement is fulfilled
zmsg=format(" string1 is required in order to close this ticket");
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.
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.
