Tom, The enforcement of required is working correctly... You just need to understand what is happening on Modify.
The way a Modify works from our UI is that we send only CHANGED fields. That means you are not modifying the date field in question so there is no checking whether there is a value or not. So, there is no enforcement. If you tried to blank the field on an existing record, you would find that the system would complain about a missing required field. If you want to force the entry of a missing date on an existing entry, you need to put something to force that. I would suggest you do that on the client or you will have problems with automated processes that may be updating the record suddenly getting errors and I don't think you want that. What you would do is for this field that you have newly made required, is put an active ink that fires on Modify (so it runs only on the modify operation as Create is covered already) with a run if of 'field' = $NULL$ and an Action of Error and a message that tells the user that they must fill in a date. NOW, the user that is trying to modify will be forced to enter a date for the date field if it is empty or they will not be able to modify. Any record with the field filled in will not trigger this workflow. So, this is how you would do what you are asking. Note however that this is a bit harsh. That means that ANY USER coming along who wants to modify anything about one of these records without a date MUST supply a date before they will be allowed to save anything to the record. Doug -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Tom Siegel Sent: Friday, May 06, 2016 1:51 PM To: [email protected] Subject: Re: Making field required after the fact I think I have part of it figured out. It appears that if you change an existing field from optional to required the functionality is as follows 1) The required field will be enforced on create and an error message will display 2) If you open an exisiting incident with the newly required field blank but change another field and submit (modify). The system will not enforce the field requirement 3) If you open an existing incident, populate the required field, submit(Modify), clear the required field, submit(Modify). The required field will be enforced on submit and an error message will display I will try this again with my active link, If I can't get this functionality I will use the active link to make the field label bold, and use a filter to enforce the field being populated (required) on create and modify Thanks, Tom _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
