Difference between revisions of "Make a Field Conditionally Required"
| Line 21: | Line 21: | ||
== Step 3. Publish the Schema changes == | == Step 3. Publish the Schema changes == | ||
| − | |||
r11.x | r11.x | ||
1. Save your Schema changes | 1. Save your Schema changes | ||
Revision as of 02:44, 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
The script is created as a .spl file and placed in the site/mods/majic directory.
string zmsg;
if(assignee.userid != cst.userid) {
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;
}
}
Step 2. Create the trigger
The trigger is responsible for "triggering" the script.
r11.x triggers are created via the Schema Designer utility. Simply add a Site-Defined Trigger to the desired table.
pre-r11.x triggers are made by creating a .mod file and placing it in the site/mods/majic directory.
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))
