**
Rick:
As I said, it was a customized Escalation system that was developed before the advent of DSO (it was that old.) The PM customer actually had a Remedy server, but they took it off line after determining that maintaining it cost too much for the value they received from it. All of the escalation workflow was archived and removed. It was then that the additional 16 statuses were determined to be excess and they needed to be removed. Before this, those statuses were very much needed and used. In other words, the original design was good but it needed a serious review and overhaul.
James McKenzie
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG]On Behalf Of Rick Cook
Sent: Thursday, March 16, 2006 10:53 AM
To: arslist@ARSLIST.ORG
Subject: Re: drop down menu
**
I guess I haven't run into the level of screwed-up-ness in applications that you have (16 UNUSED status values? YOWZA, that's bad design!). I'm not saying it's impossible to reorder status, obviously it's not - never has been. I do make it crystal clear to customers that the level of effort in doing so should cause them to look at ALL viable alternatives to that before deciding that's the best course of action. I have only seen one time in 9 years where they decided (and I agreed) that reording or inserting new status values was the best way to accomplish what they needed.
At any rate, starting with v7, making the status field more configurable is a two-edged sword; on one hand, it's easier to manipulate the order of values, on the other hand, it makes it easier to justify doing so.
Rick
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of McKenzie, James J C-E LCMC HQISEC/L3
Sent: Thursday, March 16, 2006 8:53 AM
To: arslist@ARSLIST.ORG
Subject: Re: drop down menu
**
Rick:
What to not reorder the statuses or what? I don't care why they are doing what they are doing. That is 'not my business'. If they want to make New come after Closed, something is wrong, but if the boss wants to add a Pending status between Work in Progress and Resolved and I can do it, I state that this is possible. I've learnt in this long life that the word impossible belongs in the dictionary and that the difficult just takes longer.
As an example of why I'm glad that someone thought up this program: I had to remove 16 unused and not needed statuses. Why they were added was due to a custom escalation system that was devised for a Program Manager Office. The PM decided, after fielding the product, that they did not want their own Remedy server and the Escalation code was removed but not the statuses. Guess who spend about two days removing them?
Also, if you are a programmer, you know that the value of No and False is 0. Yes and True are 1. Had to reorder several fields so that this was the order so that a program developed by an external agent would function properly.
These are just two reasons for the existance of that program.
James McKenzie
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG]On Behalf Of Rick Cook
Sent: Thursday, March 16, 2006 9:45 AM
To: arslist@ARSLIST.ORG
Subject: Re: drop down menu
**
Don't know - I just tell people not to do that, and there's usually a better way of getting what they say they want the re-ordering for.
Rick
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of McKenzie, James J C-E LCMC HQISEC/L3
Sent: Thursday, March 16, 2006 8:39 AM
To: arslist@ARSLIST.ORG
Subject: Re: drop down menu
**
Rick and Fred:
Does the old archgsel program still work with ARS 6.x? If so, I would recommend using this program to re-order your status selections. And this program can be used on any selection field (drop-down or radio button) not just the status field.
James McKenzie
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG]On Behalf Of Rick Cook
Sent: Thursday, March 16, 2006 7:31 AM
To: arslist@ARSLIST.ORG
Subject: Re: drop down menu
**
One of the v7.0 enhancements is that we will be able to give enum fields non-consecutive numbers, so that we can insert values later.
Rick
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Heider, Stephen
Sent: Thursday, March 16, 2006 6:14 AM
To: arslist@ARSLIST.ORG
Subject: Re: drop down menu
**
Shaun,
Something to keep in mind and also check throughout workflow is, some qualifications use < or >. For example, 'Status' > "Fixed", which would include "Closed". If you added another option to the end of the list then 'Status' > "Fixed" would also include "Resolved".
Since in this example, "Resolved" is normally less than "Closed" you may need to update the SQL tables/views directly after inserting "Resolved" before "Closed"... replacing values of 2 (Closed) to 3 (the new value of Closed).
Stephen
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Michiel Beijen
Sent: Thursday, March 16, 2006 3:35 AM
To: arslist@ARSLIST.ORG
Subject: Re: drop down menu
** One other solution is to hide the status field and create a new charachter field (display only) with a menu attached. You can sort the menu on what ever you like.
On display of the request you set the display only field to the value of the status field and on submit and modify you'll populate the status field with the value of the DO field.
This way you can order the field in the way YOU want without affecting the order in the enum field.
You can also use this method to 'hide' existing enum values without affecting the numbering.
Regards,
Michiel
On 3/16/06, Anjali Gosain
wrote:
This ID is generated by Remedy and is based on position of option in the
drop-down list. Since this a system generated value, it cannot be
changed. So adding the option in between will change the ID of 'Closed'
We faced a similar problem once and ended up modifying the workflow.
I would suggest adding the option at the end of the list. If that is not
feasible u might have to modify the workflow.
-------- Original Message --------
From: Shaun Pollock < aakkineni@REDIFFMAIL.COM>
To: arslist@ARSLIST.ORG
Subject: Re:drop down menu
Date: 3/16/2006 12:05 PM
> For Example:
>
> Status is a drop down list field
> having attributes:
>
> Value Alias Value ID
> open open 0
> Fixed Fixed 1
> Closed Closed 2
>
> i need to add Resolved in between the fixed and closed. As the option
> closed has ID 2 after adding this option will move to 3 . this will make
> impact for the excisting data. so i need to add the option Resolved must
> have ID 3 and should not disturb the ID of the option Closed.
>
> Thanks for the suggestions provided for my previous queries..
>
>
> UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org
>
>
DISCLAIMER:
--------------------------------------------------------------------------------------------------------------
This e-mail contains confidential and/or privileged information. If you are not the intended recipient
(or have received this e-mail in error)please notify the sender immediately and destroy this e-mail.
Any unauthorized copying, disclosure, use or distribution of the material in this e-mail is strictly forbidden.
---------------------------------------------------------------------------------------------------------------
UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org
20060125This posting was submitted with HTML in it 20060125This posting was submitted with HTML in it 20060125This posting was submitted with HTML in it
20060125This posting was submitted with HTML in it 20060125This posting was submitted with HTML in it
20060125This posting was submitted with HTML in it 20060125This posting was submitted with HTML in it
20060125This posting was submitted with HTML in it
Previous Topic
Index