OK, I see what you're saying, but couldn't that also be done without the 
selection field?  It seems you could easily map status reasons to multiple 
status values effectively achieving the same end, even if each status reason 
has a unique ID of some kind.  For example, you could give the status reason 
"Foobar" a unique ID of 1000 and simply map Foobar to multiple status values in 
a configuration form.  Your workflow then fires based on the unique ID rather 
than a selection field value.  You lose the ability to fire on "Return" for the 
selection field, but that seems like it would probably be easy to work around.

Lyle

From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Kelly Gatewood
Sent: Wednesday, July 08, 2009 11:50 AM
To: arslist@ARSLIST.ORG
Subject: Re: Selection Menu Question

**
Lyle,

The benefit that I personally see in the way that BMC implemented this is that 
the selection field contains all of the status reason values for all status 
selections.  In turn this would allow for status reasons to be shared across 
status values and also allow the programmer to fire workflow dependant upon the 
selection fields values.

For example:

Status Reason: Enhancement

Workflow could fire upon the selection of the this status reason regardless as 
to the actual status of the Incident.

Thanks

Kelly Gatewood
Senior Solutions Architect
IT Prophets
Cell 615-830-5078
www.itprophets.com<http://www.itprophets.com>
From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Lyle Taylor
Sent: Wednesday, July 08, 2009 11:47 AM
To: arslist@ARSLIST.ORG
Subject: Re: Selection Menu Question

**
You bring up something that I've been wondering about.  What's the point in 
having the hidden selection field for Status Reason?  What purpose does it 
serve that couldn't be met by simply storing the status reason, or using a 
character field to store it's Request ID, GUID, selection value, or whatever 
other unique key you want to use?  That way, it would be completely 
configurable and would not require both configuration and customization to add 
or remove status reasons.

Thanks,
Lyle

From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Kelly Gatewood
Sent: Wednesday, July 08, 2009 10:13 AM
To: arslist@ARSLIST.ORG
Subject: Re: Selection Menu Question

**
John,

A good example of this is how BMC handle the Status Reason field in ITSM 7.x.

They have the standard selection field (but it is hidden) and then have a 
character field with a menu (which has the values that you filter).

What happens, is when you choose the menu value, workflow then sets the 
appropriate value of the selection field.

Thanks

Kelly Gatewood
Senior Solutions Architect
IT Prophets
Cell 615-830-5078
www.itprophets.com<http://www.itprophets.com>
From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of John Kelley
Sent: Wednesday, July 08, 2009 10:58 AM
To: arslist@ARSLIST.ORG
Subject: Re: Selection Menu Question

**
Thats Exactly what I was looking for.  Thankyou Kelly

Now my only other issue, the original APPStatus field on the Helpdesk form is a 
selection field instead of a character field.   Is there any way to convert the 
selection field to a character field so I can map out a menu to it?

JK

_Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_


NOTICE: This email message is for the sole use of the intended recipient(s) and 
may contain confidential and privileged information. Any unauthorized review, 
use, disclosure or distribution is prohibited. If you are not the intended 
recipient, please contact the sender by reply email and destroy all copies of 
the original message.
_Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_
_Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"

Reply via email to