I'm not sure for ITSP 4 as I'm using ITSM 7, but BMC support told us
they don't want it done that way, they want everything done manually by
creating a new group and leaving the old one out there for historical
data.  As a result, I've been working on a SQL script to modify them on
the back end instead so I can keep the exact same groups.  Whenever I'm
done with that SQL script, whether it becomes a stored procedure or
what, I plan to post it to the list.

Shawn Pierson

        -----Original Message-----
        From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Koyb P. Liabt
        Sent: Thursday, July 12, 2007 2:33 PM
        To: [email protected]
        Subject: Renaming Groups and Workflow


        **
        AR 7
        ITSP 4.0, CMDB 1.0

        If a group name is changed - what workflow needs to be modified
to ensure that the historical data is transferred to the new group name?
        We have CMDB 1.0 also.  Where would I check to see if the CIs
are associated to the group?

        I am synchronizing the following to the new support group name:
        - previous incident tickets (HPD)
        - previous change tickets (CHG)
        - previous task tickets
        - previous approvals
        - any forms that hold assignment info
        - any form that I can find the previous support group name
information

        Isn't there a way to automatically update support group name
changes so that this propagates to the appropriate forms?

        Although the documentation reads that the support group name can
not be modified in ITSP 4.0 - a person not really familiar with the
application informed me that ITSP 4.0
        does not allow support group name changes.

        I will also check CI associations.

        Any ideas?  Is there a faster, better way to do this simple name
change.

________________________________

        AOL now offers free email to everyone. Find out more about
what's free from AOL at AOL.com
<http://www.aol.com?ncid=AOLAOF00020000000437> .

        __20060125_______________________This posting was submitted with
HTML in it___


Private and confidential as detailed <a
href="http://www.sug.com/disclaimers/default.htm#Mail";>here</a>.  If you cannot 
access hyperlink, please e-mail sender.

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to