discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Carey Matthew Black
Sent: Monday, January 19, 2009 4:42 PM
To: arslist@ARSLIST.ORG
Subject: Re: Selection Field: Value vs. Alias Value?
Alan,
I realize you already found a solution... but I had already started
this... so .. I will
ot;Alias value".
>
> Alan
>
> -Original Message-
> From: Action Request System discussion list(ARSList)
> [mailto:arsl...@arslist.org] On Behalf Of Carey Matthew Black
> Sent: Monday, January 19, 2009 2:57 PM
> To: arslist@ARSLIST.ORG
> Subject: Re: Selectio
...@arslist.org] On Behalf Of Alan Blake
Sent: January 19, 2009 11:26 PM
To: arslist@ARSLIST.ORG
Subject: Re: Selection Field: Value vs. Alias Value?
**
I basically have gone with the approach of using a hidden temp field that
converts the Alias value to the underlying value needed for the URL p
discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Rick Cook
Sent: Monday, January 19, 2009 2:59 PM
To: arslist@ARSLIST.ORG
Subject: Re: Selection Field: Value vs. Alias Value?
Alan,
Workflow converts selection field values to numeric anyway, so it really
doesn't matter what the
s value".
Alan
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Carey Matthew Black
Sent: Monday, January 19, 2009 2:57 PM
To: arslist@ARSLIST.ORG
Subject: Re: Selection Field: Value vs. Alias Value?
Alan,
I think your
Alan,
I think your confusing yourself a bit but maybe not...
Selection fields are just an integer value as far as work flow (Active
Links, Filters, and Escalations) are concerned. However, to the user
the field shows the Alias String (for the integer) when the user looks
at the field and when
Alan,
Workflow converts selection field values to numeric anyway, so it really
doesn't matter what the text values are.
Rick
Sent from my Verizon Wireless BlackBerry
-Original Message-
From: Alan Blake
Date: Mon, 19 Jan 2009 14:34:09
To:
Subject: Selection Field: Val
7 matches
Mail list logo