Difference between revisions of "Make a Field Conditionally Required"
(→Step 1. Create the script) |
(→Step 2. Create the trigger) |
||
| Line 16: | Line 16: | ||
<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--> | ||
| + | This code will work for all ticket types. | ||
<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'. | ||
Revision as of 03:35, 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 the Assignee is the only only able to close a ticket. Other examples are displayed at the bottom of this article.
Contents
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;
//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. For Change Orders, change the 'cr' in the first line of the script to 'chg'. For Issues change the 'cr' to 'iss'.
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.
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'.
Step 3. Publish the Schema changes
r11.x 1. Save your Schema changes 2. Stop the Service Desk service 3. Run pdm_publish from a command line 4. Start the Service Desk service
pre-r11.x Recycle the Service Desk service
Note: This logic can be used to greatly expand system functionality by ensuring that data gets collected when any number of conditions exist.
Tips
String statements together using && Example (is_null(anyfield1) && is_null(anyfield2))
For not null add an ! Example (!is_null(anyfield))
