"that it doesn't indicate a change in value, only indicates that it's changing to something "
And that is where I have a problem... It mostly indicates something is changing, but not always. It could have a value when nothing has changed. So there's no point in using it. It adds complication without adding value. Thad Esser Remedy Developer "Argue for your limitations, and sure enough, they're yours."-- Richard Bach "LJ Longwing" <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" <[email protected]> 02/21/2008 01:30 PM Please respond to [email protected] To [email protected] cc Subject Re: Interview questions The problem is that some people wouldn't have the proper matching 'DB. statement after it...which makes this statement work well....but if you remove that last statement you then have the situation where TR = "Completed", but it was already completed...and you didn't want to do that....that's the major gripe I have seen about TR...that it doesn't indicate a change in value, only indicates that it's changing to something -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Pargeter, Christie Sent: Thursday, February 21, 2008 2:24 PM To: [email protected] Subject: Re: Interview questions Here is a piece of workflow that I have in my system today that uses TR and it should. ( 'RecordUploadStatus' = "Uploaded") AND ( 'Emp_EntryID' != $NULL$ ) AND ( 'ClassNameID' != $NULL$ ) AND ( 'TR.lesson_status' = "Completed" ) AND ( 'DB.lesson_status' != "Completed" ) -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of arslist Sent: Thursday, February 21, 2008 1:01 PM To: [email protected] Subject: Re: Interview questions I think questions about: 1) Field Ids 2) Workflow naming 3) How do you document what you have done (and this is a biggy, the WHY stuff was done is usually left out) The responses to those 3 open ended questions tell you alot. I had one senior person tell me recently that he didn't think there was any reason to choose your own field ids for a custom module (on a system with the ITSM6 suite). Didn't get a chance to show him how much workflow I had been able to borrow from ITSM6 for the custom module by using the same field ids for the standard fields and then just copying the workflow with new naming (so changes for the ITSM module, or BMC patches would not affect the workflow that I borrowed). ... Daniel -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Tim Widowfield Sent: February 21, 2008 3:48 PM To: [email protected] Subject: Re: Interview questions Well, I can only speak for myself, but I normally use the TR. prefix, just so you can look at the qualification at a glance and understand what it means. It reminds me of C and Java programmers who omit braces when they aren't necessary. Sure, it's legal, but is it more readable? Too often we forget that code may be written once, but read hundreds of times (e.g., by beleaguered maintenance programmers at 3:00 AM). I'd much rather argue over whether you should ever let the admin tool pick your field IDs and whether workflow names should be meaningful rather than over syntactic sugar. --Tim ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" ***IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature.*** _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
