So weird - so unexpected -- that you really would not keep a map of (old name-> new name) when you go and rename your filters…
(And -- it is not that you would obviously know that you messed stuff up either) -- as the system will keep working -- but - just be creating "wrong data"… Which -- is not necessarily found (even in a big system) until a week later… Hence -- restoring is not an option either… Hence -- the project I had. CONCLUSION: It is a bad design - a dangerous design... -John On Fri, Apr 6, 2012 at 1:04 PM, Joe Martin D'Souza <[email protected]>wrote: > ** > I agree.. I remember discussing this exact same point a few months or > perhaps a year ago. Its weird to make a name of a workflow to be used as > ‘code’ to do a specific task. > > But while it is what it is, it would be nice to have a list of such > ‘special naming conventions’.. > > Joe > > *From:* John Sundberg <[email protected]> > *Sent:* Friday, April 06, 2012 1:52 PM > *Newsgroups:* public.remedy.arsystem.general > *To:* [email protected] > *Subject:* Re: Filter names question - `! > > ** I think the convention should be "REMOVED"… > > Add a flag on Filter -- Run Immediately… > > Approx 10 years ago -- I was brought into a big telco project to "fix it"…. > > After a new developer went through and renamed filters/actlinks to meet a > nicer naming convention… (to work with BMCs new filtering based on COLON) > > Try -- troubleshooting that…. > > Old name: > > mtc_FindIPAddress`! > > New name: > > MTC:IP:Find_Address > > > (in a haystack of 2000 filters -- that all got renamed) > > (OK - I am exaggerating the situation a bit -- but -- either way -- my > opinion it is TOO WEIRD to add something to a name - and now it works > different) > > > -John > > > > On Fri, Apr 6, 2012 at 12:46 PM, Joe Martin D'Souza <[email protected]>wrote: > >> We are allowed that on Friday :-) >> >> This is an interesting thread though.. It would be nice to have a full >> list of all these small conventions that could affect functionality.. >> >> Imagine fat fingering the keyboard (although that’s as likely to happen >> anytime too soon as as having a snow storm in the middle east) and naming a >> piece of workflow with these characters and have functionality affected, >> and not have a clue why.. >> >> Joe >> >> >> -----Original Message----- From: LJ LongWing >> Sent: Friday, April 06, 2012 12:30 PM Newsgroups: >> public.remedy.arsystem.general >> >> To: [email protected] >> Subject: Re: Filter names question - `! >> >> Ah...yes, I'll agree that * in a workflow doesn't indicate anything then >> :)....mis-read the darn post :) >> >> -----Original Message----- >> From: Action Request System discussion list(ARSList) [mailto: >> [email protected]] On Behalf Of Joe Martin D'Souza >> Sent: Friday, April 06, 2012 10:13 AM >> To: [email protected] >> Subject: Re: Filter names question - `! >> >> Dee was asking about the * in the beginning of workflow names.. That in >> front of workflow is more the work of a developer customizing an OTB app.. >> >> While I was aware that the * at the end of field names was just a visual >> thing for bold fields, I wasn't aware it was because of the section 508 >> compliance standards.. That’s a good to know and thanks for that info. >> >> -----Original Message----- From: LJ LongWing >> Sent: Friday, April 06, 2012 12:06 PM Newsgroups: >> public.remedy.arsystem.general >> To: [email protected] >> Subject: Re: Filter names question - `! >> >> The * at the beginning of the field name is a Section 508 compliance >> thing...it designates to visually impaired people that the field is >> required >> >> http://www.uspto.gov/web/**offices/cio/s508/03web.htm<http://www.uspto.gov/web/offices/cio/s508/03web.htm> >> >> search for the word 'asterisk' >> >> -----Original Message----- >> From: Action Request System discussion list(ARSList) >> [mailto:[email protected]] On Behalf Of Dee >> Sent: Friday, April 06, 2012 9:27 AM >> To: [email protected] >> Subject: Re: Filter names question - `! >> >> Thanks Joe, >> >> Like John in this post and Sam in "Suggestions" post last week, are these >> commands/tricks written any where and are there more? >> >> >> Looking at System Forms/Workflow, do these mean anything or just name >> conventions? >> >> 1. (*)At the begin of Name of workflow, ex. (*TS-SI 100 Upper Server) >> 2. (~!) At the end of name of workflow, ex. (AP:Sig-RecentHistoryDate~!) >> 3. (`1)At the end of name of workflow, ex. (XR:GetSchemaWorkflow1`1) >> >> >> >> >> >> -- >> >> ______________________________**______________________________** >> ___________________ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" >> > > > > -- > > *John Sundberg* > Kinetic Data, Inc. > "Your Business. Your Process." > *WWRUG10 Best Customer Service/Support Award* > *WWRUG09 Innovator of the Year Award* > * > * > 651-556-0930 I [email protected] > www.kineticdata.com I community.kineticdata.com > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > -- *John Sundberg* Kinetic Data, Inc. "Your Business. Your Process." *WWRUG10 Best Customer Service/Support Award* *WWRUG09 Innovator of the Year Award* * * 651-556-0930 I [email protected] www.kineticdata.com I community.kineticdata.com _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
