Exactly..
A good visual way for users to be warned, instead of error or warning mechanism would be to identify which fields you want to product, and have a small icon near those fields called 'Data Police' or something like that where the user knows that information in that field may get peer or management reviews. And you would at least get them to enter something that makes half sense in those fields (which is still valuable) rather than no sense at all.. Joe _____ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Rick Cook Sent: Monday, October 07, 2013 1:39 PM To: [email protected] Subject: Re: Trying to validate work log not to allow Blanks ** Kinda what I usually say about these requests, too. You're trying to apply a software solution to a human problem. Have management address the human problem, and you won't need the software to fix it. And to paraphrase Joe, it's an exercise in futility to make something foolproof, because they simply keep making better fools, and the cycle continues ad nauseum. Rick On Mon, Oct 7, 2013 at 10:31 AM, Joe D'Souza <[email protected]> wrote: ** Just my 2 cents.. Requirements like these ultimately converge down to a training issue where you explain to the users how important it is to have good data in that field. You might disallow spaces or multiple spaces or carriage returns - what are you going to do about users that do something like type a random string in that field? By doing the workflow you requested help on where Fred's idea is a great way to implement it, you are stopping the users from doing just 2 out of at least 10 other possible invalid type of entries and it is almost impossible to stop a user from doing any of that. Something as simple as your work log gets a periodic review from management, could probably add a better layer of protection against what goes in that field. Joe _____ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Grooms, Frederick W Sent: Monday, October 07, 2013 1:18 PM To: [email protected] Subject: Re: Trying to validate work log not to allow Blanks Try using 2 ActiveLink/Filters First Set Worklog = LTRIM(RTRIM($Worklog$)) Second Run-If: (NOT ( 'Worklog' LIKE "___%" ) ) OR ( 'Worklog' = $NULL$ ) Error This way if the worklog entry is not at least 4 characters the user will get an error Fred From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of sriram pm Sent: Monday, October 07, 2013 8:25 AM To: [email protected] Subject: Trying to validate work log not to allow Blanks ** Hi List, We are trying to update the work log when the ticket status is In Progress. We are able to achieve this with a Display Only Form but it allows space and enter which it should not. $Worklog$ != $NULL$ AND $Worklog$ != " "AND $Worklog$ != " " Kindly let us know whether there is any work around for this issue. Thank you, Sriram _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "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"
