Ah, now I understand. It would seem reasonable to track the changing of configuration data, though a CR seems a bit burdensome for so small a change. It could be a useful means of encouraging a measured approach to changing something as important as group names, though.
The bigger issue for me is that I wouldn't let anyone who doesn't understand how Remedy uses groups within 50 feet of them, especially if things like Assignment and notifications were based upon that data. That's why Remedy installations have data administrators - to keep many cooks from spoiling the soup. Rick On 7/13/07, Kathy Morris <[EMAIL PROTECTED]> wrote:
** The end users want to rename the group names (disable and create new). The impact on the CI's is one concern. Are most companies submitting a support group name change as an incident. The only CR created was for the new names. These are cosmetic changes not organizational changes. ------------------------------ Get a sneak peak of the all-new AOL.com<http://discover.aol.com/memed/aolcom30tour/?ncid=AOLAOF00020000000982> . __20060125_______________________This posting was submitted with HTML in it___
-- Rick Cook Cook Enterprises 253-278-4112 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
