It's also possible to make the field required and use modify all or sql and enter N/A for existing requests. For all new requests, create a filter on submit for which N/A is invalid. The user have to enter a value but not N/A. Sometimes it's better to make the field really required, depends on the situation.
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Timothy Powell Sent: Friday, August 18, 2006 9:20 PM To: [email protected] Subject: Re: Mandatory / Required Field If you create a field on your form, and the Entry Mode for that field (as defined on the Database tab of the Field Properties) is set to Required, then any submit or modification of a record where that field value is NULL will result in an error. The record cannot be saved until that required field has a value. To make a field conditionally required, create the same field, but this time set the Entry Mode to Optional. Then you can create workflow (active links or filters) to enforce value based on conditions that you define. For instance, in your example, to make a field value required on a new ticket but not an existing ticket, I'd create a filter that executes on Submit and the Run If statement is: $YourField$ = $NULL$. Then add an If Action that throws an Message (type Error). Your message text might say something like "A value for YourField is required in order to submit a new ticket". Enforce based on C/T/I? Sure...same concept as above, but you modify your Run If statement to look at particular C/T/I (and/or any other field) values present in the ticket. But if there is any chance that you might want the field mandatory based on numerous C/T/Is that you have, I'd do the C/T/I checking via some type of lookup and have the filter examine the result of that lookup in order to determine the enforcement. HTH, Tim Powell -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Vianna Sent: Friday, August 18, 2006 2: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 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
