Re: Incident Module - Reported Source
Marcelo, I always dread these types of requests. I don't think any workflow is dependent on reported source field but as a general practice I try to avoid modifying ITSM objects as much as I can. I handle it by creating a dummy field and hiding the original. Ben Cantatore Remedy Manager (914) 457-6209 Emerging Health IT 3 Odell Plaza Yonkers, New York 10701 marc...@cpchem.com 06/09/10 12:20 PM I have been asked to modify and remove some of the selection attributes for the field Reported Source in Incident Management (ITSM 7.0.03). I would like to know if there is any adverse effect in removing selection values. For example: Delete option Fax. Rename option Systems Management to System Generated. Etc. Also, going forward, what is the best way to find out if changing a OOB field or field value will affect other OOB functionality (i.e. notifications, approvals, SLAs, etc)? Thanks, Marcelo ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are
Re: Incident Module - Reported Source
Our rule is that if the menu is sequential, we won't modify it, but if the numbering is custom we will add odd valued entries (so they won't be affected by upgrades). We have modified that particular menu without issue. You can use a tool like Abydos to track what workflow uses a particular field. Anne Ramey *** E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties only by an authorized State Official. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Benedetto Cantatore Sent: Thursday, June 10, 2010 9:33 AM To: arslist@ARSLIST.ORG Subject: Re: Incident Module - Reported Source ** Marcelo, I always dread these types of requests. I don't think any workflow is dependent on reported source field but as a general practice I try to avoid modifying ITSM objects as much as I can. I handle it by creating a dummy field and hiding the original. Ben Cantatore Remedy Manager (914) 457-6209 Emerging Health IT 3 Odell Plaza Yonkers, New York 10701 marc...@cpchem.com 06/09/10 12:20 PM I have been asked to modify and remove some of the selection attributes for the field Reported Source in Incident Management (ITSM 7.0.03). I would like to know if there is any adverse effect in removing selection values. For example: Delete option Fax. Rename option Systems Management to System Generated. Etc. Also, going forward, what is the best way to find out if changing a OOB field or field value will affect other OOB functionality (i.e. notifications, approvals, SLAs, etc)? Thanks, Marcelo ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.orghttp://www.arslist.org attend wwrug10 www.wwrug.comhttp://www.wwrug.com ARSlist: Where the Answers Are _attend WWRUG10 www.wwrug.com ARSlist: Where the Answers Are_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are
Re: Incident Module - Reported Source
I just did this. Start by querying the database for that field id to get an idea of what other forms carry the same field (for example, the HPD:Incident_InterfaceCreate) and may pass (or receive it) from the HPD:Help Desk form. You'll want to make the same changes to all the forms that have a dependency. In my case I was only modifying an existing value so I left alone anything that was not customer facing. Fortunately this is a custom selection field so you can remove/replace/insert values without adversely affecting existing data. -- Chris Danaceau AttivaSoft Solutions Architect From: Action Request System discussion list(ARSList) on behalf of Martinez, Marcelo A Sent: Wed 6/9/2010 12:20 PM To: arslist@ARSLIST.ORG Subject: Incident Module - Reported Source I have been asked to modify and remove some of the selection attributes for the field Reported Source in Incident Management (ITSM 7.0.03). I would like to know if there is any adverse effect in removing selection values. For example: Delete option Fax. Rename option Systems Management to System Generated. Etc. Also, going forward, what is the best way to find out if changing a OOB field or field value will affect other OOB functionality (i.e. notifications, approvals, SLAs, etc)? Thanks, Marcelo ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are
Re: Incident Module - Reported Source
Thank you everyone for your comments. Much appreciated! Marcelo -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Chris Danaceau Sent: Thursday, June 10, 2010 8:46 AM To: arslist@ARSLIST.ORG Subject: Re: Incident Module - Reported Source I just did this. Start by querying the database for that field id to get an idea of what other forms carry the same field (for example, the HPD:Incident_InterfaceCreate) and may pass (or receive it) from the HPD:Help Desk form. You'll want to make the same changes to all the forms that have a dependency. In my case I was only modifying an existing value so I left alone anything that was not customer facing. Fortunately this is a custom selection field so you can remove/replace/insert values without adversely affecting existing data. -- Chris Danaceau AttivaSoft Solutions Architect From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Ramey, Anne Sent: Thursday, June 10, 2010 8:41 AM To: arslist@ARSLIST.ORG Subject: Re: Incident Module - Reported Source ** Our rule is that if the menu is sequential, we won't modify it, but if the numbering is custom we will add odd valued entries (so they won't be affected by upgrades). We have modified that particular menu without issue. You can use a tool like Abydos to track what workflow uses a particular field. Anne Ramey *** E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties only by an authorized State Official. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Benedetto Cantatore Sent: Thursday, June 10, 2010 9:33 AM To: arslist@ARSLIST.ORG Subject: Re: Incident Module - Reported Source ** Marcelo, I always dread these types of requests. I don't think any workflow is dependent on reported source field but as a general practice I try to avoid modifying ITSM objects as much as I can. I handle it by creating a dummy field and hiding the original. Ben Cantatore Remedy Manager (914) 457-6209 Emerging Health IT 3 Odell Plaza Yonkers, New York 10701 marc...@cpchem.com 06/09/10 12:20 PM I have been asked to modify and remove some of the selection attributes for the field Reported Source in Incident Management (ITSM 7.0.03). I would like to know if there is any adverse effect in removing selection values. For example: Delete option Fax. Rename option Systems Management to System Generated. Etc. Also, going forward, what is the best way to find out if changing a OOB field or field value will affect other OOB functionality (i.e. notifications, approvals, SLAs, etc)? Thanks, Marcelo ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.orghttp://www.arslist.org attend wwrug10 www.wwrug.comhttp://www.wwrug.com ARSlist: Where the Answers Are _attend WWRUG10 www.wwrug.com ARSlist: Where the Answers Are_ _attend WWRUG10 www.wwrug.com ARSlist: Where the Answers Are_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are
