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

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)





--
View this message in context:
http://ars-action-request-system.1093659.n2.nabble.com/Filter-names-question
-tp7442935p7443316.html
Sent from the ARS (Action Request System) mailing list archive at
Nabble.com.
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"

Reply via email to