You can use action Submit (= Create) and have a filter checking if the field is null or not, this filter will not trigger when editing already created requests (modify). You can also add a filter which don't accept the field to be set to null if set before. Based on CTI? Filters can perform anything .. I guess You want to make the field required if another field is XXX or check values is another form based upon field in your mainfom, ordinary filter actions, no problems. /L ars
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Vianna Sent: Friday, August 18, 2006 8:33 PM To: [email protected] Subject: Mandatory / Required Field Hello I have been asked to add a new mandatory field to our ticket form. Unfortunately I have done very little development in the past (my primary role is administration). I'm wondering what ramifications adding this field might have? For example, I would like it to be mandatory for any new tickets, but if somebody opens an existing (older) ticket, would they be forced to fill in something to that field as well? I don't want that to happen. Also, is there a way to make a field mandatory based on CTI? Any help that somebody can offer me would be great. I'm relatively new to this user group as well, so if I should be providing more info, please let me know. (We're running 5.01.02 patch level 1346 if that helps?) Thank you!! Vianna _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
