Re: ITSM naming convention sucks
In this situation, I pick the most used part of the trigger. I.e. CC_NIM:Btn_OpenIncidentTask.There is a possibility for some confusion here, so I have occasionally duplicated an AL and changed the trigger qualification to ensure clarity of code. Thanks, Gavin Coleman Senior Analyst/Programmer Computacenter (UK) Ltd Services Solutions Hatfield Avenue Hatfield, Hertfordshire, AL10 9TW, United Kingdom T: +44 (0) 1707 631662 E: gavin.cole...@computacenter.com W: www.computacenter.com -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of ccrashh Sent: 26 March 2009 17:27 To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks Out of curiousity...what do you do if the code triggers on more than one action?: CC_NIM:Btn_OpenIncidentTask-MRC_Somefield-000-OpenHelpDesk Like that? On Mar 24, 5:56 am, Coleman, Gavin gavin.cole...@computacenter.com wrote: In my opinion, ITSP followed some best naming conventions. Well considering that as far as know the naming convention is not explained anywhere in the ITSP or ITSM documentation, I can't see how you can believe that. Remedy allows you up to 80 characters to name workflow items, and it seems that ITSP and ITSM does not use all of these characters. My Active Link workflow has a naming convention as follows 1. Prefix for custom work (CC_) 2. Form abbreviation (NIM:) - New Incident Console 3. Execute on abbreviation (MRC - Menu Row Choice, Btn - Button, WL - Window Loaded). If more than one Execute on is specified, then the abbreviation I use is the most relevant 4. Name of Button, Table, Field etc (E.g. Btn_OpenIncidentTask) 5. Execution Order (-000-) 6. Details of Actions (OpenHelpDesk) Thus, we get CC_NIM:Btn_OpenIncidentTask-000-OpenHelpDesk If an AL or Filter is part of a Guide, then the suffix _GUIDE is applied. If the AL or Filter calls a Guide, then the suffix _CallGuide is applied. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are ** COMPUTACENTER PLC is registered in England and Wales with the registered number 03110569. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (UK) Limited is registered in England and Wales with the registered number 01584718. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (Mid-Market) Limited is registered in England and Wales with the registered number 3434654. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (FMS) Limited is registered in England and Wales with the registered number 3798091. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW The contents of this email are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive mail for the addressee) you may not copy or use it, or disclose it to anyone else. If you receive it in error please notify us immediately and then destroy it. Computacenter information is available from: http://www.computacenter.com ** ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: ITSM naming convention sucks
If an AL or Filter is part of a guide then I make sure that it is suffixed with _GUIDE. No execution order is needed as this is defined in the Guide itself. Thus I have ALs like CC_NIM:ConsoleView-SelectedGroupsIncident_GUIDE CC_NIM:ConsoleView-SelectedGroupsTask_GUIDE Etc. Gavin Coleman Senior Analyst/Programmer Computacenter (UK) Ltd Services Solutions Hatfield Avenue Hatfield, Hertfordshire, AL10 9TW, United Kingdom T: +44 (0) 1707 631662 E: gavin.cole...@computacenter.com W: www.computacenter.com -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of ccrashh Sent: 26 March 2009 17:30 To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks So then you would scamble through looking at each one to see what each Active Link in the guide actually does? How about: HPD-HD-CUS:xxx-1_CheckForExistingCustomer HPD-HD-CUS:xxx-2_SetCustomerInfoFromContactForm etc. Not sure what the other descriptive text could be...but xxx indicates that it triggers in a guide and nowhere else...I find it easier to find code if it is clearly labelled. On Mar 24, 12:46 pm, Joe DeSouza joe_rem...@yahoo.com wrote: Its a good naming convention - I won't go so far as to say its the best. There are a few things in the ITSP naming convention that I personally do not favor. For eg. AL's found in a guide that are used specifically in the guide alone and nowhere else.. Why different kind of names for each? Why do we need to know what each do? As a developer when looking at the list I would rather see them named as a functional name what the guide does. For eg if the Guide sets customer information and there are 5 AL's in that guide ordered 1 to 5 I would name them something like HPD:GuideSetCustomerInfo01 HPD:GuideSetCustomerInfo02 HPD:GuideSetCustomerInfo03 HPD:GuideSetCustomerInfo04 HPD:GuideSetCustomerInfo05 And name the Guide something like HPD:GuideSetCustomerInfo This is just one odd example of how it would make it easier for a developer to trace what someone else has worked on without running workflow logs for everything.. Joe From: Mahesh Chandra mchand...@gmail.com To: arsl...@arslist.org Sent: Monday, March 23, 2009 11:54:31 PM Subject: Re: ITSM naming convention sucks ** As per ITSP naming convention the standard format of an Active Link is: [z][SchemaCode]:[#]-[Field Name/Button/Function]-[Firing Condition][###E]-[Description]-[IndicatorSuffix][Status] Where z (lowercase) The lowercase z in front of the active link name indicates a Global Workflow Filter Schema Code Schema Code (Reference Schema Code in case of Global Active Link) - 3 Uppercase characters (usually the same as the entry-id prefix of the schema) # Grouping Code: 0 = Initialization (Window Open, Query, Set Defaults, Display, Copy to New) 1 = Execution (Submit, Modify) 2 = Post Execution (After Submit, After Modify) 3 = Close (Window Close) 4 - 5 (Unassigned/Reserved) 9 = In session (Button, Return, Menu/Row Choice, Gain Focus, Lose Focus0 z = Guide (Active Links Called by Guides only) ###[E] Execution Order (3 digits). Append E if Else Action exists Description Functional Description of the Workflow performed Indicator Suffix E = Error N = Note W = Warning R = Run Process Q = SQL G = Call Guide J### - Goto execution order PCDE = Push where CDE is the 3 character code Status + = New Workflow, requires testing (once tested the prefix can be removed) @ = Existing Workflow has been temporarily deactivated # = Existing deactivated workflow with the intent of deleting from the system HPD:INC: ContactSearch_120_GPn-G Even though this piece of workflow doesn't exist in ITSP, I think this is the breakout. HPD Module Name INC 3 Character Schema Code stored in SYS:Form List (ITSP) and Schema Names (ITSM 7) ContactSearch Field Name 120 Execution Order Gpn (not sure) G Indicator Suffix for Call Guide In my opinion, ITSP followed some best naming conventions. Thanks Mahesh On Fri, Mar 20, 2009 at 8:15 AM, Matt Worsdell m...@worsy.co.uk wrote: Not BMC's fault, ITSM is based on ITSP which was produced by a VAR (name withheld to protect the guilty). -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of ccrashh Sent: 20 March 2009 12:53 To: arsl...@arslist.org Subject: ITSM naming convention sucks BMC has to be kidding with their ITSM suite's naming convention...for instance: On the HPD:HelpDesk form, the Customer Search button (inexplicably called Contact Search even though it is under the Customer Information section) has several Active Links associated to it (31 or so). If you were to go to the list of active links and sort by name, the first one that appears is: HPD:INC:ContactSearch_120_GPn-G However
Re: ITSM naming convention sucks
Out of curiousity...what do you do if the code triggers on more than one action?: CC_NIM:Btn_OpenIncidentTask-MRC_Somefield-000-OpenHelpDesk Like that? On Mar 24, 5:56 am, Coleman, Gavin gavin.cole...@computacenter.com wrote: In my opinion, ITSP followed some best naming conventions. Well considering that as far as know the naming convention is not explained anywhere in the ITSP or ITSM documentation, I can't see how you can believe that. Remedy allows you up to 80 characters to name workflow items, and it seems that ITSP and ITSM does not use all of these characters. My Active Link workflow has a naming convention as follows 1. Prefix for custom work (CC_) 2. Form abbreviation (NIM:) - New Incident Console 3. Execute on abbreviation (MRC - Menu Row Choice, Btn - Button, WL - Window Loaded). If more than one Execute on is specified, then the abbreviation I use is the most relevant 4. Name of Button, Table, Field etc (E.g. Btn_OpenIncidentTask) 5. Execution Order (-000-) 6. Details of Actions (OpenHelpDesk) Thus, we get CC_NIM:Btn_OpenIncidentTask-000-OpenHelpDesk If an AL or Filter is part of a Guide, then the suffix _GUIDE is applied. If the AL or Filter calls a Guide, then the suffix _CallGuide is applied. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: ITSM naming convention sucks
So then you would scamble through looking at each one to see what each Active Link in the guide actually does? How about: HPD-HD-CUS:xxx-1_CheckForExistingCustomer HPD-HD-CUS:xxx-2_SetCustomerInfoFromContactForm etc. Not sure what the other descriptive text could be...but xxx indicates that it triggers in a guide and nowhere else...I find it easier to find code if it is clearly labelled. On Mar 24, 12:46 pm, Joe DeSouza joe_rem...@yahoo.com wrote: Its a good naming convention - I won't go so far as to say its the best. There are a few things in the ITSP naming convention that I personally do not favor. For eg. AL's found in a guide that are used specifically in the guide alone and nowhere else.. Why different kind of names for each? Why do we need to know what each do? As a developer when looking at the list I would rather see them named as a functional name what the guide does. For eg if the Guide sets customer information and there are 5 AL's in that guide ordered 1 to 5 I would name them something like HPD:GuideSetCustomerInfo01 HPD:GuideSetCustomerInfo02 HPD:GuideSetCustomerInfo03 HPD:GuideSetCustomerInfo04 HPD:GuideSetCustomerInfo05 And name the Guide something like HPD:GuideSetCustomerInfo This is just one odd example of how it would make it easier for a developer to trace what someone else has worked on without running workflow logs for everything.. Joe From: Mahesh Chandra mchand...@gmail.com To: arsl...@arslist.org Sent: Monday, March 23, 2009 11:54:31 PM Subject: Re: ITSM naming convention sucks ** As per ITSP naming convention the standard format of an Active Link is: [z][SchemaCode]:[#]-[Field Name/Button/Function]-[Firing Condition][###E]-[Description]-[IndicatorSuffix][Status] Where z (lowercase) The lowercase z in front of the active link name indicates a Global Workflow Filter Schema Code Schema Code (Reference Schema Code in case of Global Active Link) - 3 Uppercase characters (usually the same as the entry-id prefix of the schema) # Grouping Code: 0 = Initialization (Window Open, Query, Set Defaults, Display, Copy to New) 1 = Execution (Submit, Modify) 2 = Post Execution (After Submit, After Modify) 3 = Close (Window Close) 4 – 5 (Unassigned/Reserved) 9 = In session (Button, Return, Menu/Row Choice, Gain Focus, Lose Focus0 z = Guide (Active Links Called by Guides only) ###[E] Execution Order (3 digits). Append E if Else Action exists Description Functional Description of the Workflow performed Indicator Suffix E = Error N = Note W = Warning R = Run Process Q = SQL G = Call Guide J### - Goto execution order PCDE = Push where CDE is the 3 character code Status + = New Workflow, requires testing (once tested the prefix can be removed) @ = Existing Workflow has been temporarily deactivated # = Existing deactivated workflow with the intent of deleting from the system HPD:INC: ContactSearch_120_GPn-G Even though this piece of workflow doesn’t exist in ITSP, I think this is the breakout. HPD Module Name INC 3 Character Schema Code stored in SYS:Form List (ITSP) and Schema Names (ITSM 7) ContactSearch Field Name 120 Execution Order Gpn (not sure) G Indicator Suffix for Call Guide In my opinion, ITSP followed some best naming conventions. Thanks Mahesh On Fri, Mar 20, 2009 at 8:15 AM, Matt Worsdell m...@worsy.co.uk wrote: Not BMC's fault, ITSM is based on ITSP which was produced by a VAR (name withheld to protect the guilty). -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of ccrashh Sent: 20 March 2009 12:53 To: arsl...@arslist.org Subject: ITSM naming convention sucks BMC has to be kidding with their ITSM suite's naming convention...for instance: On the HPD:HelpDesk form, the Customer Search button (inexplicably called Contact Search even though it is under the Customer Information section) has several Active Links associated to it (31 or so). If you were to go to the list of active links and sort by name, the first one that appears is: HPD:INC:ContactSearch_120_GPn-G However, the first one that triggers is: HPD:INC:ContactSearch_Info_035_GetPersonInfo Which is 19th in the list of 31 Active Links. WTF. Why would anyone do things this way? How can any real Remedy ARS developer work with this crap without wanting to put his/her fist through the monitor? Here's a tip...fix the naming convention! For example: HPD-INC-CUS:SR-b035-GetPersonInfo ... HPD-INC-CUS:SR-b120-GPn-G --- of course, this should be renamed to something more explicit like: HPD-INC-CUS:SR-b120-CallGuide_CF (CF being an acronym for the ContactFound guide...which I would rename to HD-INC-CF:ContactFound) See, now this naming convention makes sense. Broken down it is the HPD module INC form
Re: ITSM naming convention sucks
Use a bit mask representation of the triggers for that part of name. Oh wait, I already have that in decimal form in the database. Is it Friday yet? Axton Grams The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. On Thu, Mar 26, 2009 at 12:26 PM, ccrashh ccra...@gmail.com wrote: Out of curiousity...what do you do if the code triggers on more than one action?: CC_NIM:Btn_OpenIncidentTask-MRC_Somefield-000-OpenHelpDesk Like that? On Mar 24, 5:56 am, Coleman, Gavin gavin.cole...@computacenter.com wrote: In my opinion, ITSP followed some best naming conventions. Well considering that as far as know the naming convention is not explained anywhere in the ITSP or ITSM documentation, I can't see how you can believe that. Remedy allows you up to 80 characters to name workflow items, and it seems that ITSP and ITSM does not use all of these characters. My Active Link workflow has a naming convention as follows 1. Prefix for custom work (CC_) 2. Form abbreviation (NIM:) - New Incident Console 3. Execute on abbreviation (MRC - Menu Row Choice, Btn - Button, WL - Window Loaded). If more than one Execute on is specified, then the abbreviation I use is the most relevant 4. Name of Button, Table, Field etc (E.g. Btn_OpenIncidentTask) 5. Execution Order (-000-) 6. Details of Actions (OpenHelpDesk) Thus, we get CC_NIM:Btn_OpenIncidentTask-000-OpenHelpDesk If an AL or Filter is part of a Guide, then the suffix _GUIDE is applied. If the AL or Filter calls a Guide, then the suffix _CallGuide is applied. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: ITSM naming convention sucks
I made it a habit to find work flow using the database a long time ago. It's fast and it gives accurate information; I can quickly find what I need when I need it. I leave the admin thread free to do what nothing else can do-create/delete/modify work flow, handle cache operations, etc. That nasty bug in the admin tool that made using the detailed work flow listing unusable (unbearably slow) helped me down that path. Axton Grams The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. On Thu, Mar 26, 2009 at 1:30 PM, Axton axton.gr...@gmail.com wrote: Use a bit mask representation of the triggers for that part of name. Oh wait, I already have that in decimal form in the database. Is it Friday yet? Axton Grams The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. On Thu, Mar 26, 2009 at 12:26 PM, ccrashh ccra...@gmail.com wrote: Out of curiousity...what do you do if the code triggers on more than one action?: CC_NIM:Btn_OpenIncidentTask-MRC_Somefield-000-OpenHelpDesk Like that? On Mar 24, 5:56 am, Coleman, Gavin gavin.cole...@computacenter.com wrote: In my opinion, ITSP followed some best naming conventions. Well considering that as far as know the naming convention is not explained anywhere in the ITSP or ITSM documentation, I can't see how you can believe that. Remedy allows you up to 80 characters to name workflow items, and it seems that ITSP and ITSM does not use all of these characters. My Active Link workflow has a naming convention as follows 1. Prefix for custom work (CC_) 2. Form abbreviation (NIM:) - New Incident Console 3. Execute on abbreviation (MRC - Menu Row Choice, Btn - Button, WL - Window Loaded). If more than one Execute on is specified, then the abbreviation I use is the most relevant 4. Name of Button, Table, Field etc (E.g. Btn_OpenIncidentTask) 5. Execution Order (-000-) 6. Details of Actions (OpenHelpDesk) Thus, we get CC_NIM:Btn_OpenIncidentTask-000-OpenHelpDesk If an AL or Filter is part of a Guide, then the suffix _GUIDE is applied. If the AL or Filter calls a Guide, then the suffix _CallGuide is applied. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: ITSM naming convention sucks
In my opinion, ITSP followed some best naming conventions. Well considering that as far as know the naming convention is not explained anywhere in the ITSP or ITSM documentation, I can't see how you can believe that. Remedy allows you up to 80 characters to name workflow items, and it seems that ITSP and ITSM does not use all of these characters. My Active Link workflow has a naming convention as follows 1. Prefix for custom work (CC_) 2. Form abbreviation (NIM:) - New Incident Console 3. Execute on abbreviation (MRC - Menu Row Choice, Btn - Button, WL - Window Loaded). If more than one Execute on is specified, then the abbreviation I use is the most relevant 4. Name of Button, Table, Field etc (E.g. Btn_OpenIncidentTask) 5. Execution Order (-000-) 6. Details of Actions (OpenHelpDesk) Thus, we get CC_NIM:Btn_OpenIncidentTask-000-OpenHelpDesk If an AL or Filter is part of a Guide, then the suffix _GUIDE is applied. If the AL or Filter calls a Guide, then the suffix _CallGuide is applied. I'm sure other people have naming conventions, but if you are providing a product that is to be released to the general public, then surely publishing the naming convention in your documentation is ESSENTIAL. Just my £0.02 worth! Gavin Coleman Senior Analyst/Programmer Computacenter (UK) Ltd Services Solutions Hatfield Avenue Hatfield, Hertfordshire, AL10 9TW, United Kingdom T: +44 (0) 1707 631662 E: gavin.cole...@computacenter.com W: www.computacenter.com ** COMPUTACENTER PLC is registered in England and Wales with the registered number 03110569. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (UK) Limited is registered in England and Wales with the registered number 01584718. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (Mid-Market) Limited is registered in England and Wales with the registered number 3434654. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (FMS) Limited is registered in England and Wales with the registered number 3798091. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW The contents of this email are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive mail for the addressee) you may not copy or use it, or disclose it to anyone else. If you receive it in error please notify us immediately and then destroy it. Computacenter information is available from: http://www.computacenter.com ** ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: ITSM naming convention sucks
My previous posting has all been taken from ITSP Naming Convention Documentation Ver 2.0.40 Dated July 8, 2002. Thanks Mahesh On Tue, Mar 24, 2009 at 4:56 AM, Coleman, Gavin gavin.cole...@computacenter.com wrote: ** “In my opinion, ITSP followed some best naming conventions.” Well considering that as far as know the naming convention is not explained anywhere in the ITSP or ITSM documentation, I can’t see how you can believe that. Remedy allows you up to 80 characters to name workflow items, and it seems that ITSP and ITSM does not use all of these characters. My Active Link workflow has a naming convention as follows 1. Prefix for custom work (CC_) 2. Form abbreviation (NIM:) – *N*ew *I*ncident *C*onsole 3. Execute on abbreviation (MRC – Menu Row Choice, Btn – Button, WL – Window Loaded). If more than one Execute on is specified, then the abbreviation I use is the most relevant 4. Name of Button, Table, Field etc (E.g. Btn_OpenIncidentTask) 5. Execution Order (-000-) 6. Details of Actions (OpenHelpDesk) Thus, we get CC_NIM:Btn_OpenIncidentTask-000-OpenHelpDesk If an AL or Filter is part of a Guide, then the suffix _GUIDE is applied. If the AL or Filter calls a Guide, then the suffix _CallGuide is applied. I’m sure other people have naming conventions, but if you are providing a product that is to be released to the general public, then surely publishing the naming convention in your documentation is ESSENTIAL. Just my £0.02 worth! *Gavin Coleman* *Senior Analyst/Programmer * *Computacenter (UK) Ltd* Services Solutions Hatfield Avenue Hatfield, Hertfordshire, AL10 9TW, United Kingdom T: +44 (0) 1707 631662 E: *gavin.cole...@computacenter.com* W: *www.computacenter.com* ** COMPUTACENTER PLC is registered in England and Wales with the registered number 03110569. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (UK) Limited is registered in England and Wales with the registered number 01584718. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (Mid-Market) Limited is registered in England and Wales with the registered number 3434654. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (FMS) Limited is registered in England and Wales with the registered number 3798091. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW The contents of this email are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive mail for the addressee) you may not copy or use it, or disclose it to anyone else. If you receive it in error please notify us immediately and then destroy it. Computacenter information is available from: http://www.computacenter.com ** __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: ITSM naming convention sucks
Hmmm. No document of that name exists in the current documentation directory for ITSP 4 on BMC support web. I still say that shows a distinct lack of regard for current users of ITSP / ITSM! I think that the naming convention of ITSP stems from ARS version 4 which had a smaller limit on workflow names. The fact that the naming convention in ITSP seems to vary from module to module also doesn't help! Thanks for the update on the naming convention though. Could have done with this about 3 years ago! Gavin Coleman Senior Analyst/Programmer Computacenter (UK) Ltd Services Solutions Hatfield Avenue Hatfield, Hertfordshire, AL10 9TW, United Kingdom T: +44 (0) 1707 631662 E: gavin.cole...@computacenter.com W: www.computacenter.com From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Mahesh Chandra Sent: 24 March 2009 14:23 To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks ** My previous posting has all been taken from ITSP Naming Convention Documentation Ver 2.0.40 Dated July 8, 2002. Thanks Mahesh On Tue, Mar 24, 2009 at 4:56 AM, Coleman, Gavin gavin.cole...@computacenter.commailto:gavin.cole...@computacenter.com wrote: ** In my opinion, ITSP followed some best naming conventions. Well considering that as far as know the naming convention is not explained anywhere in the ITSP or ITSM documentation, I can't see how you can believe that. Remedy allows you up to 80 characters to name workflow items, and it seems that ITSP and ITSM does not use all of these characters. My Active Link workflow has a naming convention as follows 1. Prefix for custom work (CC_) 2. Form abbreviation (NIM:) - New Incident Console 3. Execute on abbreviation (MRC - Menu Row Choice, Btn - Button, WL - Window Loaded). If more than one Execute on is specified, then the abbreviation I use is the most relevant 4. Name of Button, Table, Field etc (E.g. Btn_OpenIncidentTask) 5. Execution Order (-000-) 6. Details of Actions (OpenHelpDesk) Thus, we get CC_NIM:Btn_OpenIncidentTask-000-OpenHelpDesk If an AL or Filter is part of a Guide, then the suffix _GUIDE is applied. If the AL or Filter calls a Guide, then the suffix _CallGuide is applied. I'm sure other people have naming conventions, but if you are providing a product that is to be released to the general public, then surely publishing the naming convention in your documentation is ESSENTIAL. Just my £0.02 worth! Gavin Coleman Senior Analyst/Programmer Computacenter (UK) Ltd Services Solutions Hatfield Avenue Hatfield, Hertfordshire, AL10 9TW, United Kingdom T: +44 (0) 1707 631662 E: gavin.cole...@computacenter.commailto:gavin.cole...@computacenter.com W: www.computacenter.comhttp://www.computacenter.com/ ** COMPUTACENTER PLC is registered in England and Wales with the registered number 03110569. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (UK) Limited is registered in England and Wales with the registered number 01584718. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (Mid-Market) Limited is registered in England and Wales with the registered number 3434654. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (FMS) Limited is registered in England and Wales with the registered number 3798091. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW The contents of this email are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive mail for the addressee) you may not copy or use it, or disclose it to anyone else. If you receive it in error please notify us immediately and then destroy it. Computacenter information is available from: http://www.computacenter.comhttp://www.computacenter.com/ ** __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: ITSM naming convention sucks
Strictly speaking, ITSM is BMC's product, and they are under no obligation to provide us with any of the nitty-gritty details about how their application was written including any naming conventions used internally, etc. The fact that BMC allows you to customize the product doesn't mean they need to support you in that effort or to make it easy for you. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Coleman, Gavin Sent: Tuesday, March 24, 2009 3:56 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks ** In my opinion, ITSP followed some best naming conventions. Well considering that as far as know the naming convention is not explained anywhere in the ITSP or ITSM documentation, I can't see how you can believe that. Remedy allows you up to 80 characters to name workflow items, and it seems that ITSP and ITSM does not use all of these characters. My Active Link workflow has a naming convention as follows 1. Prefix for custom work (CC_) 2. Form abbreviation (NIM:) - New Incident Console 3. Execute on abbreviation (MRC - Menu Row Choice, Btn - Button, WL - Window Loaded). If more than one Execute on is specified, then the abbreviation I use is the most relevant 4. Name of Button, Table, Field etc (E.g. Btn_OpenIncidentTask) 5. Execution Order (-000-) 6. Details of Actions (OpenHelpDesk) Thus, we get CC_NIM:Btn_OpenIncidentTask-000-OpenHelpDesk If an AL or Filter is part of a Guide, then the suffix _GUIDE is applied. If the AL or Filter calls a Guide, then the suffix _CallGuide is applied. I'm sure other people have naming conventions, but if you are providing a product that is to be released to the general public, then surely publishing the naming convention in your documentation is ESSENTIAL. Just my £0.02 worth! Gavin Coleman Senior Analyst/Programmer Computacenter (UK) Ltd Services Solutions Hatfield Avenue Hatfield, Hertfordshire, AL10 9TW, United Kingdom T: +44 (0) 1707 631662 E: gavin.cole...@computacenter.com W: www.computacenter.com ** COMPUTACENTER PLC is registered in England and Wales with the registered number 03110569. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (UK) Limited is registered in England and Wales with the registered number 01584718. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (Mid-Market) Limited is registered in England and Wales with the registered number 3434654. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (FMS) Limited is registered in England and Wales with the registered number 3798091. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW The contents of this email are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive mail for the addressee) you may not copy or use it, or disclose it to anyone else. If you receive it in error please notify us immediately and then destroy it. Computacenter information is available from: http://www.computacenter.com ** __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ 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. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: ITSM naming convention sucks
I think that paying for support says otherwise... except for that easy part. David M Clark Remedy Programmer/Analyst Lyle Taylor tayl...@ldschurch.org 3/24/2009 10:06 AM Strictly speaking, ITSM is BMC's product, and they are under no obligation to provide us with any of the nitty-gritty details about how their application was written including any naming conventions used internally, etc. The fact that BMC allows you to customize the product doesn't mean they need to support you in that effort or to make it easy for you. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Coleman, Gavin Sent: Tuesday, March 24, 2009 3:56 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks ** In my opinion, ITSP followed some best naming conventions. Well considering that as far as know the naming convention is not explained anywhere in the ITSP or ITSM documentation, I can't see how you can believe that. Remedy allows you up to 80 characters to name workflow items, and it seems that ITSP and ITSM does not use all of these characters. My Active Link workflow has a naming convention as follows 1. Prefix for custom work (CC_) 2. Form abbreviation (NIM:) - New Incident Console 3. Execute on abbreviation (MRC - Menu Row Choice, Btn - Button, WL - Window Loaded). If more than one Execute on is specified, then the abbreviation I use is the most relevant 4. Name of Button, Table, Field etc (E.g. Btn_OpenIncidentTask) 5. Execution Order (-000-) 6. Details of Actions (OpenHelpDesk) Thus, we get CC_NIM:Btn_OpenIncidentTask-000-OpenHelpDesk If an AL or Filter is part of a Guide, then the suffix _GUIDE is applied. If the AL or Filter calls a Guide, then the suffix _CallGuide is applied. I'm sure other people have naming conventions, but if you are providing a product that is to be released to the general public, then surely publishing the naming convention in your documentation is ESSENTIAL. Just my £0.02 worth! Gavin Coleman Senior Analyst/Programmer Computacenter (UK) Ltd Services Solutions Hatfield Avenue Hatfield, Hertfordshire, AL10 9TW, United Kingdom T: +44 (0) 1707 631662 E: gavin.cole...@computacenter.com W: www.computacenter.com ** COMPUTACENTER PLC is registered in England and Wales with the registered number 03110569. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (UK) Limited is registered in England and Wales with the registered number 01584718. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (Mid-Market) Limited is registered in England and Wales with the registered number 3434654. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (FMS) Limited is registered in England and Wales with the registered number 3798091. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW The contents of this email are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive mail for the addressee) you may not copy or use it, or disclose it to anyone else. If you receive it in error please notify us immediately and then destroy it. Computacenter information is available from: http://www.computacenter.com ** __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ 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 distri bution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: ITSM naming convention sucks
That is true, but the fact that there is (was) a published document about the naming convention that is no longer published on support web shows a lack of regard for developers. Mahesh is it possible for you to post the naming convention document to the list please? If not, would you be willing to forward it to me off list? Thanks, Gavin Coleman Senior Analyst/Programmer Computacenter (UK) Ltd Services Solutions Hatfield Avenue Hatfield, Hertfordshire, AL10 9TW, United Kingdom T: +44 (0) 1707 631662 E: gavin.cole...@computacenter.com W: www.computacenter.com From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Lyle Taylor Sent: 24 March 2009 15:06 To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks ** Strictly speaking, ITSM is BMC's product, and they are under no obligation to provide us with any of the nitty-gritty details about how their application was written including any naming conventions used internally, etc. The fact that BMC allows you to customize the product doesn't mean they need to support you in that effort or to make it easy for you. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Coleman, Gavin Sent: Tuesday, March 24, 2009 3:56 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks ** In my opinion, ITSP followed some best naming conventions. Well considering that as far as know the naming convention is not explained anywhere in the ITSP or ITSM documentation, I can't see how you can believe that. Remedy allows you up to 80 characters to name workflow items, and it seems that ITSP and ITSM does not use all of these characters. My Active Link workflow has a naming convention as follows 1. Prefix for custom work (CC_) 2. Form abbreviation (NIM:) - New Incident Console 3. Execute on abbreviation (MRC - Menu Row Choice, Btn - Button, WL - Window Loaded). If more than one Execute on is specified, then the abbreviation I use is the most relevant 4. Name of Button, Table, Field etc (E.g. Btn_OpenIncidentTask) 5. Execution Order (-000-) 6. Details of Actions (OpenHelpDesk) Thus, we get CC_NIM:Btn_OpenIncidentTask-000-OpenHelpDesk If an AL or Filter is part of a Guide, then the suffix _GUIDE is applied. If the AL or Filter calls a Guide, then the suffix _CallGuide is applied. I'm sure other people have naming conventions, but if you are providing a product that is to be released to the general public, then surely publishing the naming convention in your documentation is ESSENTIAL. Just my £0.02 worth! Gavin Coleman Senior Analyst/Programmer Computacenter (UK) Ltd Services Solutions Hatfield Avenue Hatfield, Hertfordshire, AL10 9TW, United Kingdom T: +44 (0) 1707 631662 E: gavin.cole...@computacenter.com W: www.computacenter.com ** COMPUTACENTER PLC is registered in England and Wales with the registered number 03110569. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (UK) Limited is registered in England and Wales with the registered number 01584718. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (Mid-Market) Limited is registered in England and Wales with the registered number 3434654. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (FMS) Limited is registered in England and Wales with the registered number 3798091. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW The contents of this email are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive mail for the addressee) you may not copy or use it, or disclose it to anyone else. If you receive it in error please notify us immediately and then destroy it. Computacenter information is available from: http://www.computacenter.com ** __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ 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: RMI Solutions ARSlist: Where the Answers Are html___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: ITSM naming convention sucks
I don't think so. They will support the applications out of the box. They won't support customizations. If you break something with your customizations, they are not obligated to help you figure out how you broke it. They might, but they might not. They are also not necessarily obligated to help you understand their workflow, unless it relates to a documented integration point. Many of the whitepapers they provide are nice, but not strictly necessary. Understand that I would love it if BMC documented their systems better. I just don't think that the statement that it is necessary that they document their naming conventions, or the implied statement that they should document other implementation details, is correct. It would be great if they did, but they are under no obligation to do so. Lyle -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of David.M Clark Sent: Tuesday, March 24, 2009 9:36 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks I think that paying for support says otherwise... except for that easy part. David M Clark Remedy Programmer/Analyst Lyle Taylor tayl...@ldschurch.org 3/24/2009 10:06 AM Strictly speaking, ITSM is BMC's product, and they are under no obligation to provide us with any of the nitty-gritty details about how their application was written including any naming conventions used internally, etc. The fact that BMC allows you to customize the product doesn't mean they need to support you in that effort or to make it easy for you. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Coleman, Gavin Sent: Tuesday, March 24, 2009 3:56 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks ** In my opinion, ITSP followed some best naming conventions. Well considering that as far as know the naming convention is not explained anywhere in the ITSP or ITSM documentation, I can't see how you can believe that. Remedy allows you up to 80 characters to name workflow items, and it seems that ITSP and ITSM does not use all of these characters. My Active Link workflow has a naming convention as follows 1. Prefix for custom work (CC_) 2. Form abbreviation (NIM:) - New Incident Console 3. Execute on abbreviation (MRC - Menu Row Choice, Btn - Button, WL - Window Loaded). If more than one Execute on is specified, then the abbreviation I use is the most relevant 4. Name of Button, Table, Field etc (E.g. Btn_OpenIncidentTask) 5. Execution Order (-000-) 6. Details of Actions (OpenHelpDesk) Thus, we get CC_NIM:Btn_OpenIncidentTask-000-OpenHelpDesk If an AL or Filter is part of a Guide, then the suffix _GUIDE is applied. If the AL or Filter calls a Guide, then the suffix _CallGuide is applied. I'm sure other people have naming conventions, but if you are providing a product that is to be released to the general public, then surely publishing the naming convention in your documentation is ESSENTIAL. Just my £0.02 worth! Gavin Coleman Senior Analyst/Programmer Computacenter (UK) Ltd Services Solutions Hatfield Avenue Hatfield, Hertfordshire, AL10 9TW, United Kingdom T: +44 (0) 1707 631662 E: gavin.cole...@computacenter.com W: www.computacenter.com ** COMPUTACENTER PLC is registered in England and Wales with the registered number 03110569. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (UK) Limited is registered in England and Wales with the registered number 01584718. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (Mid-Market) Limited is registered in England and Wales with the registered number 3434654. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (FMS) Limited is registered in England and Wales with the registered number 3798091. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW The contents of this email are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive mail for the addressee) you may not copy or use it, or disclose it to anyone else. If you receive it in error please notify us immediately and then destroy it. Computacenter information is available from: http://www.computacenter.com ** __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ 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 distri bution is prohibited
Re: ITSM naming convention sucks
If the question presented to them is about workflow... are they not obligated? Yours... theirs... doesn't matter. David M Clark Remedy Programmer/Analyst Lyle Taylor tayl...@ldschurch.org 3/24/2009 10:50 AM I don't think so. They will support the applications out of the box. They won't support customizations. If you break something with your customizations, they are not obligated to help you figure out how you broke it. They might, but they might not. They are also not necessarily obligated to help you understand their workflow, unless it relates to a documented integration point. Many of the whitepapers they provide are nice, but not strictly necessary. Understand that I would love it if BMC documented their systems better. I just don't think that the statement that it is necessary that they document their naming conventions, or the implied statement that they should document other implementation details, is correct. It would be great if they did, but they are under no obligation to do so. Lyle -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of David.M Clark Sent: Tuesday, March 24, 2009 9:36 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks I think that paying for support says otherwise... except for that easy part. David M Clark Remedy Programmer/Analyst Lyle Taylor tayl...@ldschurch.org 3/24/2009 10:06 AM Strictly speaking, ITSM is BMC's product, and they are under no obligation to provide us with any of the nitty-gritty details about how their application was written including any naming conventions used internally, etc. The fact that BMC allows you to customize the product doesn't mean they need to support you in that effort or to make it easy for you. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Coleman, Gavin Sent: Tuesday, March 24, 2009 3:56 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks ** In my opinion, ITSP followed some best naming conventions. Well considering that as far as know the naming convention is not explained anywhere in the ITSP or ITSM documentation, I can't see how you can believe that. Remedy allows you up to 80 characters to name workflow items, and it seems that ITSP and ITSM does not use all of these characters. My Active Link workflow has a naming convention as follows 1. Prefix for custom work (CC_) 2. Form abbreviation (NIM:) - New Incident Console 3. Execute on abbreviation (MRC - Menu Row Choice, Btn - Button, WL - Window Loaded). If more than one Execute on is specified, then the abbreviation I use is the most relevant 4. Name of Button, Table, Field etc (E.g. Btn_OpenIncidentTask) 5. Execution Order (-000-) 6. Details of Actions (OpenHelpDesk) Thus, we get CC_NIM:Btn_OpenIncidentTask-000-OpenHelpDesk If an AL or Filter is part of a Guide, then the suffix _GUIDE is applied. If the AL or Filter calls a Guide, then the suffix _CallGuide is applied. I'm sure other people have naming conventions, but if you are providing a product that is to be released to the general public, then surely publishing the naming convention in your documentation is ESSENTIAL. Just my £0.02 worth! Gavin Coleman Senior Analyst/Programmer Computacenter (UK) Ltd Services Solutions Hatfield Avenue Hatfield, Hertfordshire, AL10 9TW, United Kingdom T: +44 (0) 1707 631662 E: gavin.cole...@computacenter.com W: www.computacenter.com ** COMPUTACENTER PLC is registered in England and Wales with the registered number 03110569. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (UK) Limited is registered in England and Wales with the registered number 01584718. Its registered office i s at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (Mid-Market) Limited is registered in England and Wales with the registered number 3434654. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (FMS) Limited is registered in England and Wales with the registered number 3798091. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW The contents of this email are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive mail for the addressee) you may not copy or use it, or disclose it to anyone else. If you receive it in error please notify us immediately and then destroy it. Computacenter information is available from: http://www.computacenter.com ** __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___
Re: ITSM naming convention sucks
Another reason to write/construct you own solution and follow best practices in naming conventions/documentation/etc. Been doing Remedy for 13+ years, logical naming of objects is important - Custom or OTB. Oh the days of Remedy - Your Business, Your Way! Doug Tanner Gidd how about you, how does ESS standardize naming conventions? -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Lyle Taylor Sent: Tuesday, March 24, 2009 11:50 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks I don't think so. They will support the applications out of the box. They won't support customizations. If you break something with your customizations, they are not obligated to help you figure out how you broke it. They might, but they might not. They are also not necessarily obligated to help you understand their workflow, unless it relates to a documented integration point. Many of the whitepapers they provide are nice, but not strictly necessary. Understand that I would love it if BMC documented their systems better. I just don't think that the statement that it is necessary that they document their naming conventions, or the implied statement that they should document other implementation details, is correct. It would be great if they did, but they are under no obligation to do so. Lyle -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of David.M Clark Sent: Tuesday, March 24, 2009 9:36 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks I think that paying for support says otherwise... except for that easy part. David M Clark Remedy Programmer/Analyst Lyle Taylor tayl...@ldschurch.org 3/24/2009 10:06 AM Strictly speaking, ITSM is BMC's product, and they are under no obligation to provide us with any of the nitty-gritty details about how their application was written including any naming conventions used internally, etc. The fact that BMC allows you to customize the product doesn't mean they need to support you in that effort or to make it easy for you. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Coleman, Gavin Sent: Tuesday, March 24, 2009 3:56 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks ** In my opinion, ITSP followed some best naming conventions. Well considering that as far as know the naming convention is not explained anywhere in the ITSP or ITSM documentation, I can't see how you can believe that. Remedy allows you up to 80 characters to name workflow items, and it seems that ITSP and ITSM does not use all of these characters. My Active Link workflow has a naming convention as follows 1. Prefix for custom work (CC_) 2. Form abbreviation (NIM:) - New Incident Console 3. Execute on abbreviation (MRC - Menu Row Choice, Btn - Button, WL - Window Loaded). If more than one Execute on is specified, then the abbreviation I use is the most relevant 4. Name of Button, Table, Field etc (E.g. Btn_OpenIncidentTask) 5. Execution Order (-000-) 6. Details of Actions (OpenHelpDesk) Thus, we get CC_NIM:Btn_OpenIncidentTask-000-OpenHelpDesk If an AL or Filter is part of a Guide, then the suffix _GUIDE is applied. If the AL or Filter calls a Guide, then the suffix _CallGuide is applied. I'm sure other people have naming conventions, but if you are providing a product that is to be released to the general public, then surely publishing the naming convention in your documentation is ESSENTIAL. Just my £0.02 worth! Gavin Coleman Senior Analyst/Programmer Computacenter (UK) Ltd Services Solutions Hatfield Avenue Hatfield, Hertfordshire, AL10 9TW, United Kingdom T: +44 (0) 1707 631662 E: gavin.cole...@computacenter.com W: www.computacenter.com ** COMPUTACENTER PLC is registered in England and Wales with the registered number 03110569. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (UK) Limited is registered in England and Wales with the registered number 01584718. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (Mid-Market) Limited is registered in England and Wales with the registered number 3434654. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (FMS) Limited is registered in England and Wales with the registered number 3798091. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW The contents of this email are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive mail
Re: ITSM naming convention sucks
Hi, If you want to make changes you have to do you own due dilligence any way - logs, workflow analyzers, etc. The naming convensions has been missleading in the past because of the few exceptions. Technically, every naming convention that is not mine is missing something (just kidding). Regards, Nicky Madjarov phone: 973-202-4278 Find out how to bust your AR System performance @ http://www.SpeedUpARS.com - Original Message - From: Lyle Taylor tayl...@ldschurch.org Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Sent: Tuesday, March 24, 2009 11:50 AM Subject: Re: ITSM naming convention sucks I don't think so. They will support the applications out of the box. They won't support customizations. If you break something with your customizations, they are not obligated to help you figure out how you broke it. They might, but they might not. They are also not necessarily obligated to help you understand their workflow, unless it relates to a documented integration point. Many of the whitepapers they provide are nice, but not strictly necessary. Understand that I would love it if BMC documented their systems better. I just don't think that the statement that it is necessary that they document their naming conventions, or the implied statement that they should document other implementation details, is correct. It would be great if they did, but they are under no obligation to do so. Lyle -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of David.M Clark Sent: Tuesday, March 24, 2009 9:36 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks I think that paying for support says otherwise... except for that easy part. David M Clark Remedy Programmer/Analyst Lyle Taylor tayl...@ldschurch.org 3/24/2009 10:06 AM Strictly speaking, ITSM is BMC's product, and they are under no obligation to provide us with any of the nitty-gritty details about how their application was written including any naming conventions used internally, etc. The fact that BMC allows you to customize the product doesn't mean they need to support you in that effort or to make it easy for you. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Coleman, Gavin Sent: Tuesday, March 24, 2009 3:56 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks ** In my opinion, ITSP followed some best naming conventions. Well considering that as far as know the naming convention is not explained anywhere in the ITSP or ITSM documentation, I can't see how you can believe that. Remedy allows you up to 80 characters to name workflow items, and it seems that ITSP and ITSM does not use all of these characters. My Active Link workflow has a naming convention as follows 1. Prefix for custom work (CC_) 2. Form abbreviation (NIM:) - New Incident Console 3. Execute on abbreviation (MRC - Menu Row Choice, Btn - Button, WL - Window Loaded). If more than one Execute on is specified, then the abbreviation I use is the most relevant 4. Name of Button, Table, Field etc (E.g. Btn_OpenIncidentTask) 5. Execution Order (-000-) 6. Details of Actions (OpenHelpDesk) Thus, we get CC_NIM:Btn_OpenIncidentTask-000-OpenHelpDesk If an AL or Filter is part of a Guide, then the suffix _GUIDE is applied. If the AL or Filter calls a Guide, then the suffix _CallGuide is applied. I'm sure other people have naming conventions, but if you are providing a product that is to be released to the general public, then surely publishing the naming convention in your documentation is ESSENTIAL. Just my £0.02 worth! Gavin Coleman Senior Analyst/Programmer Computacenter (UK) Ltd Services Solutions Hatfield Avenue Hatfield, Hertfordshire, AL10 9TW, United Kingdom T: +44 (0) 1707 631662 E: gavin.cole...@computacenter.com W: www.computacenter.com ** COMPUTACENTER PLC is registered in England and Wales with the registered number 03110569. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (UK) Limited is registered in England and Wales with the registered number 01584718. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (Mid-Market) Limited is registered in England and Wales with the registered number 3434654. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (FMS) Limited is registered in England and Wales with the registered number 3798091. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW The contents of this email are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you
Re: ITSM naming convention sucks
One more comment on this topic: Something BMC should do is put help text on their OOTB application fields. I really don't know why they don't do it. -Guillaume -Original Message- From: Action Request System discussion list(ARSList) on behalf of Tanner, Doug Sent: Tue 03/24/09 11:57 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks Another reason to write/construct you own solution and follow best practices in naming conventions/documentation/etc. Been doing Remedy for 13+ years, logical naming of objects is important - Custom or OTB. Oh the days of Remedy - Your Business, Your Way! Doug Tanner Gidd how about you, how does ESS standardize naming conventions? -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Lyle Taylor Sent: Tuesday, March 24, 2009 11:50 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks I don't think so. They will support the applications out of the box. They won't support customizations. If you break something with your customizations, they are not obligated to help you figure out how you broke it. They might, but they might not. They are also not necessarily obligated to help you understand their workflow, unless it relates to a documented integration point. Many of the whitepapers they provide are nice, but not strictly necessary. Understand that I would love it if BMC documented their systems better. I just don't think that the statement that it is necessary that they document their naming conventions, or the implied statement that they should document other implementation details, is correct. It would be great if they did, but they are under no obligation to do so. Lyle -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of David.M Clark Sent: Tuesday, March 24, 2009 9:36 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks I think that paying for support says otherwise... except for that easy part. David M Clark Remedy Programmer/Analyst Lyle Taylor tayl...@ldschurch.org 3/24/2009 10:06 AM Strictly speaking, ITSM is BMC's product, and they are under no obligation to provide us with any of the nitty-gritty details about how their application was written including any naming conventions used internally, etc. The fact that BMC allows you to customize the product doesn't mean they need to support you in that effort or to make it easy for you. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Coleman, Gavin Sent: Tuesday, March 24, 2009 3:56 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks ** In my opinion, ITSP followed some best naming conventions. Well considering that as far as know the naming convention is not explained anywhere in the ITSP or ITSM documentation, I can't see how you can believe that. Remedy allows you up to 80 characters to name workflow items, and it seems that ITSP and ITSM does not use all of these characters. My Active Link workflow has a naming convention as follows 1. Prefix for custom work (CC_) 2. Form abbreviation (NIM:) - New Incident Console 3. Execute on abbreviation (MRC - Menu Row Choice, Btn - Button, WL - Window Loaded). If more than one Execute on is specified, then the abbreviation I use is the most relevant 4. Name of Button, Table, Field etc (E.g. Btn_OpenIncidentTask) 5. Execution Order (-000-) 6. Details of Actions (OpenHelpDesk) Thus, we get CC_NIM:Btn_OpenIncidentTask-000-OpenHelpDesk If an AL or Filter is part of a Guide, then the suffix _GUIDE is applied. If the AL or Filter calls a Guide, then the suffix _CallGuide is applied. I'm sure other people have naming conventions, but if you are providing a product that is to be released to the general public, then surely publishing the naming convention in your documentation is ESSENTIAL. Just my £0.02 worth! Gavin Coleman Senior Analyst/Programmer Computacenter (UK) Ltd Services Solutions Hatfield Avenue Hatfield, Hertfordshire, AL10 9TW, United Kingdom T: +44 (0) 1707 631662 E: gavin.cole...@computacenter.com W: www.computacenter.com ** COMPUTACENTER PLC is registered in England and Wales with the registered number 03110569. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (UK) Limited is registered in England and Wales with the registered number 01584718. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (Mid-Market) Limited is registered in England and Wales with the registered number 3434654. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (FMS) Limited is registered in England and Wales
Re: ITSM naming convention sucks
Help text ended with ITSM 5. Engineers accidentally removed it from 6. There apparently wasn't time to add it to 7. Rick Sent from my Verizon Wireless BlackBerry -Original Message- From: Guillaume Rheault guilla...@dcshq.com Date: Tue, 24 Mar 2009 09:04:30 To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks One more comment on this topic: Something BMC should do is put help text on their OOTB application fields. I really don't know why they don't do it. -Guillaume -Original Message- From: Action Request System discussion list(ARSList) on behalf of Tanner, Doug Sent: Tue 03/24/09 11:57 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks Another reason to write/construct you own solution and follow best practices in naming conventions/documentation/etc. Been doing Remedy for 13+ years, logical naming of objects is important - Custom or OTB. Oh the days of Remedy - Your Business, Your Way! Doug Tanner Gidd how about you, how does ESS standardize naming conventions? -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Lyle Taylor Sent: Tuesday, March 24, 2009 11:50 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks I don't think so. They will support the applications out of the box. They won't support customizations. If you break something with your customizations, they are not obligated to help you figure out how you broke it. They might, but they might not. They are also not necessarily obligated to help you understand their workflow, unless it relates to a documented integration point. Many of the whitepapers they provide are nice, but not strictly necessary. Understand that I would love it if BMC documented their systems better. I just don't think that the statement that it is necessary that they document their naming conventions, or the implied statement that they should document other implementation details, is correct. It would be great if they did, but they are under no obligation to do so. Lyle -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of David.M Clark Sent: Tuesday, March 24, 2009 9:36 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks I think that paying for support says otherwise... except for that easy part. David M Clark Remedy Programmer/Analyst Lyle Taylor tayl...@ldschurch.org 3/24/2009 10:06 AM Strictly speaking, ITSM is BMC's product, and they are under no obligation to provide us with any of the nitty-gritty details about how their application was written including any naming conventions used internally, etc. The fact that BMC allows you to customize the product doesn't mean they need to support you in that effort or to make it easy for you. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Coleman, Gavin Sent: Tuesday, March 24, 2009 3:56 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks ** In my opinion, ITSP followed some best naming conventions. Well considering that as far as know the naming convention is not explained anywhere in the ITSP or ITSM documentation, I can't see how you can believe that. Remedy allows you up to 80 characters to name workflow items, and it seems that ITSP and ITSM does not use all of these characters. My Active Link workflow has a naming convention as follows 1. Prefix for custom work (CC_) 2. Form abbreviation (NIM:) - New Incident Console 3. Execute on abbreviation (MRC - Menu Row Choice, Btn - Button, WL - Window Loaded). If more than one Execute on is specified, then the abbreviation I use is the most relevant 4. Name of Button, Table, Field etc (E.g. Btn_OpenIncidentTask) 5. Execution Order (-000-) 6. Details of Actions (OpenHelpDesk) Thus, we get CC_NIM:Btn_OpenIncidentTask-000-OpenHelpDesk If an AL or Filter is part of a Guide, then the suffix_GUIDE is applied. If the AL or Filter calls a Guide, then the suffix_CallGuide is applied. I'm sure other people have naming conventions, but if you are providing a product that is to be released to the general public, then surely publishing the naming convention in your documentation is ESSENTIAL. Just my £0.02 worth! Gavin Coleman Senior Analyst/Programmer Computacenter (UK) Ltd Services Solutions Hatfield Avenue Hatfield, Hertfordshire, AL10 9TW, United Kingdom T: +44 (0) 1707 631662 E: gavin.cole...@computacenter.com W: www.computacenter.com ** COMPUTACENTER PLC is registered in England and Wales with the registered number 03110569. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (UK) Limited is registered in England and Wales with the registered number 01584718. Its registered office
Re: ITSM naming convention sucks
Let me give an example of what I'm talking about. Let's say you make some code changes to the CMDB and you find after a bit that reconciliation is not working. You're not sure if it's your changes or an issue with the system. You contact BMC for support, and they ask you to send them logs, etc. At some point you indicate, well, we made some changes, but I'm not sure they would affect this. Eventually, if they can't replicate the issue on their side or see from the logs what's going on, they may ask you to undo your changes and see if the issue still persists. If they suspect the issue is due to your changes, depending on who you're working with and how much they want to help you, they may or may not help you figure out what it was you broke. At that point, they are not obligated to support you from the ITSM application perspective, because OOB the system works - if you broke it, it's now yours to figure out. Now, if you have a specific workflow question, then they may help you, but that's a different issue. Either way, none of that has anything to do with whether or not they are obligated to publish the implementation details and internal standards they use to write their applications. It would be nice if they did, because that makes it easier for us, but that still doesn't mean that it's ESSENTIAL that they do. You could also look at the fact that it may largely be a moving target. Many of the applications are old and evolving, and naming conventions can change over time. As they change, they can't possibly go back and update all the existing workflow that used an old naming convention. The best they can do is use the new convention for new workflow and possibly update existing workflow as they touch it. This means that no matter what naming convention they publish, it can't be considered fully accurate and will just cause people to complain that they're not following their own standards. Looked at that way, I can see why they might not even want to publish it. Now, what would be _nice_ would be if they published a best practices document that _recommends_ one or more possible naming conventions along with other best practices that may make application understanding and maintenance easier. I've heard of something like that existing, but I haven't been able to find it yet... Lyle -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of David.M Clark Sent: Tuesday, March 24, 2009 9:54 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks If the question presented to them is about workflow... are they not obligated? Yours... theirs... doesn't matter. David M Clark Remedy Programmer/Analyst Lyle Taylor tayl...@ldschurch.org 3/24/2009 10:50 AM I don't think so. They will support the applications out of the box. They won't support customizations. If you break something with your customizations, they are not obligated to help you figure out how you broke it. They might, but they might not. They are also not necessarily obligated to help you understand their workflow, unless it relates to a documented integration point. Many of the whitepapers they provide are nice, but not strictly necessary. Understand that I would love it if BMC documented their systems better. I just don't think that the statement that it is necessary that they document their naming conventions, or the implied statement that they should document other implementation details, is correct. It would be great if they did, but they are under no obligation to do so. Lyle -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of David.M Clark Sent: Tuesday, March 24, 2009 9:36 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks I think that paying for support says otherwise... except for that easy part. David M Clark Remedy Programmer/Analyst Lyle Taylor tayl...@ldschurch.org 3/24/2009 10:06 AM Strictly speaking, ITSM is BMC's product, and they are under no obligation to provide us with any of the nitty-gritty details about how their application was written including any naming conventions used internally, etc. The fact that BMC allows you to customize the product doesn't mean they need to support you in that effort or to make it easy for you. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Coleman, Gavin Sent: Tuesday, March 24, 2009 3:56 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks ** In my opinion, ITSP followed some best naming conventions. Well considering that as far as know the naming convention is not explained anywhere in the ITSP or ITSM documentation, I can't see how you can believe that. Remedy allows you up to 80 characters to name workflow items, and it seems that ITSP and ITSM does not use all of these characters. My Active
Re: ITSM naming convention sucks
I completely agree with that comment. :-) From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Guillaume Rheault Sent: Tuesday, March 24, 2009 10:05 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks ** One more comment on this topic: Something BMC should do is put help text on their OOTB application fields. I really don't know why they don't do it. -Guillaume -Original Message- From: Action Request System discussion list(ARSList) on behalf of Tanner, Doug Sent: Tue 03/24/09 11:57 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks Another reason to write/construct you own solution and follow best practices in naming conventions/documentation/etc. Been doing Remedy for 13+ years, logical naming of objects is important - Custom or OTB. Oh the days of Remedy - Your Business, Your Way! Doug Tanner Gidd how about you, how does ESS standardize naming conventions? -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Lyle Taylor Sent: Tuesday, March 24, 2009 11:50 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks I don't think so. They will support the applications out of the box. They won't support customizations. If you break something with your customizations, they are not obligated to help you figure out how you broke it. They might, but they might not. They are also not necessarily obligated to help you understand their workflow, unless it relates to a documented integration point. Many of the whitepapers they provide are nice, but not strictly necessary. Understand that I would love it if BMC documented their systems better. I just don't think that the statement that it is necessary that they document their naming conventions, or the implied statement that they should document other implementation details, is correct. It would be great if they did, but they are under no obligation to do so. Lyle -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of David.M Clark Sent: Tuesday, March 24, 2009 9:36 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks I think that paying for support says otherwise... except for that easy part. David M Clark Remedy Programmer/Analyst Lyle Taylor tayl...@ldschurch.org 3/24/2009 10:06 AM Strictly speaking, ITSM is BMC's product, and they are under no obligation to provide us with any of the nitty-gritty details about how their application was written including any naming conventions used internally, etc. The fact that BMC allows you to customize the product doesn't mean they need to support you in that effort or to make it easy for you. From: Action Request System discussion list(ARSList) __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ 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. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: ITSM naming convention sucks
At first when I read your response Lyle I was taken aback but I definitely now understand your viewpoint. BMC Developers are constantly under the gun to upgrade their applications and with their ITSM application upgrades comes new functionality offered by the new AR System platform and its new features. That can lead to more that any workflow can do as far as actions and execute conditions, etc which could lead to new naming conventions. Going back and rewriting the existing code that is transferred to the new version would be quite an undertaking hence the state of all the ITSM workflow setup with 30 character as the limit even though that limit changed with AR System 7. The bottom line point with this rant is that looking up how things work and/or trying to troubleshoot issues typically ends up requiring developers to look through a mass number of Active Links or Filters listed by forms or by prefixes and trying to make sense of the listings of various workflow. Based on the toolset we have (the Remedy Admin Tool) we try to rely on the naming conventions to allow us to make sense of how things work and/or to quickly research and troubleshoot issues or questions that may arise. Ideally a better view of the workflow in a more recognizable format would provide developers a better way of performing this effort. I think that's really all developers are concerned about. Ive seen tools such as Abydos Analyser and Designer that can help but I have yet to see a tool BMC has provides that makes this effort of seeing the big picture easier. Ive seen some shots of the new Developers Tool offered for ARS 7.5 but not sure if that alleviates the need to look through lists of workflow and with the need to understand and see the big picture based on the naming conventions. Thanks Peter Lammey ESPN IT Client Architecture and Automation 860-766-4761 -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Lyle Taylor Sent: Tuesday, March 24, 2009 12:12 PM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks Let me give an example of what I'm talking about. Let's say you make some code changes to the CMDB and you find after a bit that reconciliation is not working. You're not sure if it's your changes or an issue with the system. You contact BMC for support, and they ask you to send them logs, etc. At some point you indicate, well, we made some changes, but I'm not sure they would affect this. Eventually, if they can't replicate the issue on their side or see from the logs what's going on, they may ask you to undo your changes and see if the issue still persists. If they suspect the issue is due to your changes, depending on who you're working with and how much they want to help you, they may or may not help you figure out what it was you broke. At that point, they are not obligated to support you from the ITSM application perspective, because OOB the system works - if you broke it, it's now yours to figure out. Now, if you have a specific workflow question, then they may help you, but that's a different issue. Either way, none of that has anything to do with whether or not they are obligated to publish the implementation details and internal standards they use to write their applications. It would be nice if they did, because that makes it easier for us, but that still doesn't mean that it's ESSENTIAL that they do. You could also look at the fact that it may largely be a moving target. Many of the applications are old and evolving, and naming conventions can change over time. As they change, they can't possibly go back and update all the existing workflow that used an old naming convention. The best they can do is use the new convention for new workflow and possibly update existing workflow as they touch it. This means that no matter what naming convention they publish, it can't be considered fully accurate and will just cause people to complain that they're not following their own standards. Looked at that way, I can see why they might not even want to publish it. Now, what would be _nice_ would be if they published a best practices document that _recommends_ one or more possible naming conventions along with other best practices that may make application understanding and maintenance easier. I've heard of something like that existing, but I haven't been able to find it yet... Lyle -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of David.M Clark Sent: Tuesday, March 24, 2009 9:54 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks If the question presented to them is about workflow... are they not obligated? Yours... theirs... doesn't matter. David M Clark Remedy Programmer/Analyst Lyle Taylor tayl...@ldschurch.org 3/24/2009 10:50 AM I don't think so. They will support
Re: ITSM naming convention sucks
It still could have been done writting a SQL update to all objects to mark them as 6 or 7 after development of that product if they wanted to.. Joe From: Rick Cook remedyr...@gmail.com To: arslist@ARSLIST.ORG Sent: Tuesday, March 24, 2009 12:08:22 PM Subject: Re: ITSM naming convention sucks **Help text ended with ITSM 5. Engineers accidentally removed it from 6. There apparently wasn't time to add it to 7. Rick Sent from my Verizon Wireless BlackBerry From: Guillaume Rheault Date: Tue, 24 Mar 2009 09:04:30 -0700 To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks One more comment on this topic: Something BMC should do is put help text on their OOTB application fields. I really don't know why they don't do it. -Guillaume -Original Message- From: Action Request System discussion list(ARSList) on behalf of Tanner, Doug Sent: Tue 03/24/09 11:57 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks Another reason to write/construct you own solution and follow best practices in naming conventions/documentation/etc. Been doing Remedy for 13+ years, logical naming of objects is important - Custom or OTB. Oh the days of Remedy - Your Business, Your Way! Doug Tanner Gidd how about you, how does ESS standardize naming conventions? -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Lyle Taylor Sent: Tuesday, March 24, 2009 11:50 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks I don't think so. They will support the applications out of the box. They won't support customizations. If you break something with your customizations, they are not obligated to help you figure out how you broke it. They might, but they might not. They are also not necessarily obligated to help you understand their workflow, unless it relates to a documented integration point. Many of the whitepapers they provide are nice, but not strictly necessary. Understand that I would love it if BMC documented their systems better. I just don't think that the statement that it is necessary that they document their naming conventions, or the implied statement that they should document other implementation details, is correct. It would be great if they did, but they are under no obligation to do so. Lyle -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of David.M Clark Sent: Tuesday, March 24, 2009 9:36 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks I think that paying for support says otherwise... except for that easy part. David M Clark Remedy Programmer/Analyst Lyle Taylor tayl...@ldschurch.org 3/24/2009 10:06 AM Strictly speaking, ITSM is BMC's product, and they are under no obligation to provide us with any of the nitty-gritty details about how their application was written including any naming conventions used internally, etc. The fact that BMC allows you to customize the product doesn't mean they need to support you in that effort or to make it easy for you. From: Action Request System discussion list(ARSList) ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: ITSM naming convention sucks
Its a good naming convention - I won't go so far as to say its the best. There are a few things in the ITSP naming convention that I personally do not favor. For eg. AL's found in a guide that are used specifically in the guide alone and nowhere else.. Why different kind of names for each? Why do we need to know what each do? As a developer when looking at the list I would rather see them named as a functional name what the guide does. For eg if the Guide sets customer information and there are 5 AL's in that guide ordered 1 to 5 I would name them something like HPD:GuideSetCustomerInfo01 HPD:GuideSetCustomerInfo02 HPD:GuideSetCustomerInfo03 HPD:GuideSetCustomerInfo04 HPD:GuideSetCustomerInfo05 And name the Guide something like HPD:GuideSetCustomerInfo This is just one odd example of how it would make it easier for a developer to trace what someone else has worked on without running workflow logs for everything.. Joe From: Mahesh Chandra mchand...@gmail.com To: arslist@ARSLIST.ORG Sent: Monday, March 23, 2009 11:54:31 PM Subject: Re: ITSM naming convention sucks ** As per ITSP naming convention the standard format of an Active Link is: [z][SchemaCode]:[#]-[Field Name/Button/Function]-[Firing Condition][###E]-[Description]-[IndicatorSuffix][Status] Where z (lowercase) The lowercase z in front of the active link name indicates a Global Workflow Filter Schema Code Schema Code (Reference Schema Code in case of Global Active Link) - 3 Uppercase characters (usually the same as the entry-id prefix of the schema) # Grouping Code: 0 = Initialization (Window Open, Query, Set Defaults, Display, Copy to New) 1 = Execution (Submit, Modify) 2 = Post Execution (After Submit, After Modify) 3 = Close (Window Close) 4 – 5 (Unassigned/Reserved) 9 = In session (Button, Return, Menu/Row Choice, Gain Focus, Lose Focus0 z = Guide (Active Links Called by Guides only) ###[E] Execution Order (3 digits). Append E if Else Action exists Description Functional Description of the Workflow performed Indicator Suffix E = Error N = Note W = Warning R = Run Process Q = SQL G = Call Guide J### - Goto execution order PCDE = Push where CDE is the 3 character code Status + = New Workflow, requires testing (once tested the prefix can be removed) @ = Existing Workflow has been temporarily deactivated # = Existing deactivated workflow with the intent of deleting from the system HPD:INC: ContactSearch_120_GPn-G Even though this piece of workflow doesn’t exist in ITSP, I think this is the breakout. HPD Module Name INC 3 Character Schema Code stored in SYS:Form List (ITSP) and Schema Names (ITSM 7) ContactSearch Field Name 120 Execution Order Gpn (not sure) G Indicator Suffix for Call Guide In my opinion, ITSP followed some best naming conventions. Thanks Mahesh On Fri, Mar 20, 2009 at 8:15 AM, Matt Worsdell m...@worsy.co.uk wrote: Not BMC's fault, ITSM is based on ITSP which was produced by a VAR (name withheld to protect the guilty). -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of ccrashh Sent: 20 March 2009 12:53 To: arslist@ARSLIST.ORG Subject: ITSM naming convention sucks BMC has to be kidding with their ITSM suite's naming convention...for instance: On the HPD:HelpDesk form, the Customer Search button (inexplicably called Contact Search even though it is under the Customer Information section) has several Active Links associated to it (31 or so). If you were to go to the list of active links and sort by name, the first one that appears is: HPD:INC:ContactSearch_120_GPn-G However, the first one that triggers is: HPD:INC:ContactSearch_Info_035_GetPersonInfo Which is 19th in the list of 31 Active Links. WTF. Why would anyone do things this way? How can any real Remedy ARS developer work with this crap without wanting to put his/her fist through the monitor? Here's a tip...fix the naming convention! For example: HPD-INC-CUS:SR-b035-GetPersonInfo ... HPD-INC-CUS:SR-b120-GPn-G --- of course, this should be renamed to something more explicit like: HPD-INC-CUS:SR-b120-CallGuide_CF (CF being an acronym for the ContactFound guide...which I would rename to HD-INC-CF:ContactFound) See, now this naming convention makes sense. Broken down it is the HPD module INC form (though, I would change this to HD probably to match the form's actual acronym) CUS (for Customer - so we know this has something to do with the Customer information on the form) SR - for Search (so if this were the Create button, I would use CR, and MD for Modify) b - for button (other abbreviations would be s = submit, m=modify, mc = menu choice, etc.) 035 or 120 - execution order GetPersonInfo - or other - description of the functionality (can be followed by things like -E for Error, or -G for a Goto, etc.) So, if I were
Re: ITSM naming convention sucks
Yes, I completely understand your point and can relate with that. I've also spent countless hours trying to reverse engineer BMC's code via filter and active link logs, etc., and felt like tearing my hair out more than once... Lyle -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Lammey, Peter A. Sent: Tuesday, March 24, 2009 10:27 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks At first when I read your response Lyle I was taken aback but I definitely now understand your viewpoint. BMC Developers are constantly under the gun to upgrade their applications and with their ITSM application upgrades comes new functionality offered by the new AR System platform and its new features. That can lead to more that any workflow can do as far as actions and execute conditions, etc which could lead to new naming conventions. Going back and rewriting the existing code that is transferred to the new version would be quite an undertaking hence the state of all the ITSM workflow setup with 30 character as the limit even though that limit changed with AR System 7. The bottom line point with this rant is that looking up how things work and/or trying to troubleshoot issues typically ends up requiring developers to look through a mass number of Active Links or Filters listed by forms or by prefixes and trying to make sense of the listings of various workflow. Based on the toolset we have (the Remedy Admin Tool) we try to rely on the naming conventions to allow us to make sense of how things work and/or to quickly research and troubleshoot issues or questions that may arise. Ideally a better view of the workflow in a more recognizable format would provide developers a better way of performing this effort. I think that's really all developers are concerned about. Ive seen tools such as Abydos Analyser and Designer that can help but I have yet to see a tool BMC has provides that makes this effort of seeing the big picture easier. Ive seen some shots of the new Developers Tool offered for ARS 7.5 but not sure if that alleviates the need to look through lists of workflow and with the need to understand and see the big picture based on the naming conventions. Thanks Peter Lammey ESPN IT Client Architecture and Automation 860-766-4761 -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Lyle Taylor Sent: Tuesday, March 24, 2009 12:12 PM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks Let me give an example of what I'm talking about. Let's say you make some code changes to the CMDB and you find after a bit that reconciliation is not working. You're not sure if it's your changes or an issue with the system. You contact BMC for support, and they ask you to send them logs, etc. At some point you indicate, well, we made some changes, but I'm not sure they would affect this. Eventually, if they can't replicate the issue on their side or see from the logs what's going on, they may ask you to undo your changes and see if the issue still persists. If they suspect the issue is due to your changes, depending on who you're working with and how much they want to help you, they may or may not help you figure out what it was you broke. At that point, they are not obligated to support you from the ITSM application perspective, because OOB the system works - if you broke it, it's now yours to figure out. Now, if you have a specific workflow question, then they may help you, but that's a different issue. Either way, none of that has anything to do with whether or not they are obligated to publish the implementation details and internal standards they use to write their applications. It would be nice if they did, because that makes it easier for us, but that still doesn't mean that it's ESSENTIAL that they do. You could also look at the fact that it may largely be a moving target. Many of the applications are old and evolving, and naming conventions can change over time. As they change, they can't possibly go back and update all the existing workflow that used an old naming convention. The best they can do is use the new convention for new workflow and possibly update existing workflow as they touch it. This means that no matter what naming convention they publish, it can't be considered fully accurate and will just cause people to complain that they're not following their own standards. Looked at that way, I can see why they might not even want to publish it. Now, what would be _nice_ would be if they published a best practices document that _recommends_ one or more possible naming conventions along with other best practices that may make application understanding and maintenance easier. I've heard of something like that existing, but I haven't been able to find it yet... Lyle
Re: ITSM naming convention sucks
It's this kind of thinking that will get us less and less from BMC as time goes on. Date: Tue, 24 Mar 2009 09:06:21 -0600 From: tayl...@ldschurch.org Subject: Re: ITSM naming convention sucks To: arslist@ARSLIST.ORG ** Strictly speaking, ITSM is BMC’s product, and they are under no obligation to provide us with any of the nitty-gritty details about how their application was written including any naming conventions used internally, etc. The fact that BMC allows you to customize the product doesn’t mean they need to support you in that effort or to make it easy for you. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Coleman, Gavin Sent: Tuesday, March 24, 2009 3:56 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks ** “In my opinion, ITSP followed some best naming conventions.” Well considering that as far as know the naming convention is not explained anywhere in the ITSP or ITSM documentation, I can’t see how you can believe that. Remedy allows you up to 80 characters to name workflow items, and it seems that ITSP and ITSM does not use all of these characters. My Active Link workflow has a naming convention as follows Prefix for custom work (CC_) Form abbreviation (NIM:) – New Incident Console Execute on abbreviation (MRC – Menu Row Choice, Btn – Button, WL – Window Loaded). If more than one Execute on is specified, then the abbreviation I use is the most relevant Name of Button, Table, Field etc (E.g. Btn_OpenIncidentTask) Execution Order (-000-) Details of Actions (OpenHelpDesk) Thus, we get CC_NIM:Btn_OpenIncidentTask-000-OpenHelpDesk If an AL or Filter is part of a Guide, then the suffix _GUIDE is applied. If the AL or Filter calls a Guide, then the suffix _CallGuide is applied. I’m sure other people have naming conventions, but if you are providing a product that is to be released to the general public, then surely publishing the naming convention in your documentation is ESSENTIAL. Just my £0.02 worth! Gavin Coleman Senior Analyst/Programmer Computacenter (UK) Ltd Services Solutions Hatfield Avenue Hatfield, Hertfordshire, AL10 9TW, United Kingdom T: +44 (0) 1707 631662 E: gavin.cole...@computacenter.com W: www.computacenter.com ** COMPUTACENTER PLC is registered in England and Wales with the registered number 03110569. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (UK) Limited is registered in England and Wales with the registered number 01584718. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (Mid-Market) Limited is registered in England and Wales with the registered number 3434654. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (FMS) Limited is registered in England and Wales with the registered number 3798091. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW The contents of this email are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive mail for the addressee) you may not copy or use it, or disclose it to anyone else. If you receive it in error please notify us immediately and then destroy it. Computacenter information is available from: http://www.computacenter.com ** __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ 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: RMI Solutions ARSlist: Where the Answers Are html___ _ Windows Live™ SkyDrive: Get 25 GB of free online storage. http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_skydrive_032009 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: ITSM naming convention sucks
Hi Doug In my opinion there are problems with trying to do too much with naming conventions for workflow. One of the principal problems is in applying enhancements to an existing application - if you add actions to an active link, do you change the name? If so, your delta definitions file needs to contain a disabled version of the object being replaced, and the new object with the new name too. I try to avoid this unless the active link actions are radically altered so that the existing name would be misleading. What do you do when an active link has 25 actions?? I see no point in trying to include firing conditions in the object name (window open, menu choice etc.) as these can be seen in the object list in the admin tool. In ESS active links tend to be named with abbreviations for APP:FORM/SHR-btnTextDescriptionnn where nn is a sequence number for related workflow if appropriate. They might also contain a suffix Nm/Dlg to indicate if that workflow is designed to run specifically for normal windows, or modal dialog windows. For filters, the only difference is to include the filter execution order like APP:FORM/SHR-620TextDescriptionnn where 620 is the execution order. This lists most filters in the order they will fire. In other words, we try to keep the naming convention as simple as possible while still giving useful information, but retaining existing object names where possible to make applying enhancements easier. As far as support is concerned, you break it and we'll help you fix it. Period. We normally set up copies of client's servers including any customizations so that we can easily troubleshoot issues with them. And support costs you no more for 2000 users than it does for 20 users - fixed price. David Sanders Remedy Solution Architect Enterprise Service Suite @ Work == tel +44 1494 468980 mobile +44 7710 377761 email david.sand...@westoverconsulting.co.uk web http://www.westoverconsulting.co.uk -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Tanner, Doug Sent: Tuesday, March 24, 2009 3:58 PM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks Another reason to write/construct you own solution and follow best practices in naming conventions/documentation/etc. Been doing Remedy for 13+ years, logical naming of objects is important - Custom or OTB. Oh the days of Remedy - Your Business, Your Way! Doug Tanner Gidd how about you, how does ESS standardize naming conventions? -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Lyle Taylor Sent: Tuesday, March 24, 2009 11:50 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks I don't think so. They will support the applications out of the box. They won't support customizations. If you break something with your customizations, they are not obligated to help you figure out how you broke it. They might, but they might not. They are also not necessarily obligated to help you understand their workflow, unless it relates to a documented integration point. Many of the whitepapers they provide are nice, but not strictly necessary. Understand that I would love it if BMC documented their systems better. I just don't think that the statement that it is necessary that they document their naming conventions, or the implied statement that they should document other implementation details, is correct. It would be great if they did, but they are under no obligation to do so. Lyle -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of David.M Clark Sent: Tuesday, March 24, 2009 9:36 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks I think that paying for support says otherwise... except for that easy part. David M Clark Remedy Programmer/Analyst Lyle Taylor tayl...@ldschurch.org 3/24/2009 10:06 AM Strictly speaking, ITSM is BMC's product, and they are under no obligation to provide us with any of the nitty-gritty details about how their application was written including any naming conventions used internally, etc. The fact that BMC allows you to customize the product doesn't mean they need to support you in that effort or to make it easy for you. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Coleman, Gavin Sent: Tuesday, March 24, 2009 3:56 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks ** In my opinion, ITSP followed some best naming conventions. Well considering that as far as know the naming convention is not explained anywhere in the ITSP or ITSM documentation, I can't see how you can believe that. Remedy allows you up to 80 characters to name workflow items, and it seems that ITSP and ITSM does not use all of these characters. My Active Link workflow has a naming
Re: ITSM naming convention sucks
I'm not trying to say that BMC shouldn't publish more documentation and/or improve what they already have, or that we shouldn't ask for more. I just don't agree with the final statement (or perhaps the tone of it) in Gavin's e-mail below. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of John Doe Sent: Tuesday, March 24, 2009 11:24 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks ** It's this kind of thinking that will get us less and less from BMC as time goes on. Date: Tue, 24 Mar 2009 09:06:21 -0600 From: tayl...@ldschurch.org Subject: Re: ITSM naming convention sucks To: arslist@ARSLIST.ORG ** Strictly speaking, ITSM is BMC's product, and they are under no obligation to provide us with any of the nitty-gritty details about how their application was written including any naming conventions used internally, etc. The fact that BMC allows you to customize the product doesn't mean they need to support you in that effort or to make it easy for you. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Coleman, Gavin Sent: Tuesday, March 24, 2009 3:56 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks ** In my opinion, ITSP followed some best naming conventions. Well considering that as far as know the naming convention is not explained anywhere in the ITSP or ITSM documentation, I can't see how you can believe that. Remedy allows you up to 80 characters to name workflow items, and it seems that ITSP and ITSM does not use all of these characters. My Active Link workflow has a naming convention as follows 1. Prefix for custom work (CC_) 2. Form abbreviation (NIM:) - New Incident Console 3. Execute on abbreviation (MRC - Menu Row Choice, Btn - Button, WL - Window Loaded). If more than one Execute on is specified, then the abbreviation I use is the most relevant 4. Name of Button, Table, Field etc (E.g. Btn_OpenIncidentTask) 5. Execution Order (-000-) 6. Details of Actions (OpenHelpDesk) Thus, we get CC_NIM:Btn_OpenIncidentTask-000-OpenHelpDesk If an AL or Filter is part of a Guide, then the suffix _GUIDE is applied. If the AL or Filter calls a Guide, then the suffix _CallGuide is applied. I'm sure other people have naming conventions, but if you are providing a product that is to be released to the general public, then surely publishing the naming convention in your documentation is ESSENTIAL. Just my £0.02 worth! Gavin Coleman Senior Analyst/Programmer Computacenter (UK) Ltd Services Solutions Hatfield Avenue Hatfield, Hertfordshire, AL10 9TW, United Kingdom T: +44 (0) 1707 631662 E: gavin.cole...@computacenter.com W: www.computacenter.com ** COMPUTACENTER PLC is registered in England and Wales with the registered number 03110569. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (UK) Limited is registered in England and Wales with the registered number 01584718. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (Mid-Market) Limited is registered in England and Wales with the registered number 3434654. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW COMPUTACENTER (FMS) Limited is registered in England and Wales with the registered number 3798091. Its registered office is at Hatfield Business Park, Hatfield Avenue, Hatfield, Hertfordshire AL10 9TW The contents of this email are intended for the named addressee only. It contains information which may be confidential and which may also be privileged. Unless you are the named addressee (or authorised to receive mail for the addressee) you may not copy or use it, or disclose it to anyone else. If you receive it in error please notify us immediately and then destroy it. Computacenter information is available from: http://www.computacenter.com ** __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ 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: RMI Solutions ARSlist: Where the Answers Are html___ Windows Live(tm) SkyDrive: Get 25 GB of free online storage. Check it out.http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_skydrive_032009 __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___
Re: ITSM naming convention sucks
Hi David, I agree with your approach. It is definitely a pain in the neck to have to rename workflow, makes migrations much more difficult. The more intelligence you put in the naming convention, the more likely object names will have to be updated. With the details view in the admin tool and DeveloperStudio, and the new enhancements done to DeveloperStudio like the summary description of the active link and filter actions, you don't have to put all that intelligence in the name. -Guillaume -Original Message- From: Action Request System discussion list(ARSList) on behalf of David Sanders Sent: Tue 03/24/09 1:39 PM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks Hi Doug In my opinion there are problems with trying to do too much with naming conventions for workflow. One of the principal problems is in applying enhancements to an existing application - if you add actions to an active link, do you change the name? If so, your delta definitions file needs to contain a disabled version of the object being replaced, and the new object with the new name too. I try to avoid this unless the active link actions are radically altered so that the existing name would be misleading. What do you do when an active link has 25 actions?? I see no point in trying to include firing conditions in the object name (window open, menu choice etc.) as these can be seen in the object list in the admin tool. In ESS active links tend to be named with abbreviations for APP:FORM/SHR-btnTextDescriptionnn where nn is a sequence number for related workflow if appropriate. They might also contain a suffix Nm/Dlg to indicate if that workflow is designed to run specifically for normal windows, or modal dialog windows. For filters, the only difference is to include the filter execution order like APP:FORM/SHR-620TextDescriptionnn where 620 is the execution order. This lists most filters in the order they will fire. In other words, we try to keep the naming convention as simple as possible while still giving useful information, but retaining existing object names where possible to make applying enhancements easier. As far as support is concerned, you break it and we'll help you fix it. Period. We normally set up copies of client's servers including any customizations so that we can easily troubleshoot issues with them. And support costs you no more for 2000 users than it does for 20 users - fixed price. David Sanders Remedy Solution Architect Enterprise Service Suite @ Work == tel +44 1494 468980 mobile +44 7710 377761 email david.sand...@westoverconsulting.co.uk web http://www.westoverconsulting.co.uk -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Tanner, Doug Sent: Tuesday, March 24, 2009 3:58 PM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks Another reason to write/construct you own solution and follow best practices in naming conventions/documentation/etc. Been doing Remedy for 13+ years, logical naming of objects is important - Custom or OTB. Oh the days of Remedy - Your Business, Your Way! Doug Tanner Gidd how about you, how does ESS standardize naming conventions? -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Lyle Taylor Sent: Tuesday, March 24, 2009 11:50 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks I don't think so. They will support the applications out of the box. They won't support customizations. If you break something with your customizations, they are not obligated to help you figure out how you broke it. They might, but they might not. They are also not necessarily obligated to help you understand their workflow, unless it relates to a documented integration point. Many of the whitepapers they provide are nice, but not strictly necessary. Understand that I would love it if BMC documented their systems better. I just don't think that the statement that it is necessary that they document their naming conventions, or the implied statement that they should document other implementation details, is correct. It would be great if they did, but they are under no obligation to do so. Lyle -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of David.M Clark Sent: Tuesday, March 24, 2009 9:36 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks I think that paying for support says otherwise... except for that easy part. David M Clark Remedy Programmer/Analyst Lyle Taylor tayl...@ldschurch.org 3/24/2009 10:06 AM Strictly speaking, ITSM is BMC's product, and they are under no obligation to provide us with any of the nitty-gritty details about how their application was written including any naming conventions used internally, etc. The fact that BMC allows you
Re: ITSM naming convention sucks
Thats exactly why I prefer functional names over names that describe what exactly the AL does unless that AL is specifically doing that without being a part of a bigger function. By functional names I mean if there is a set of AL's or Filters that run either as a guide or otherwise, that perform a specific function such as SetCustomerInfo or RetreiveUserData or whatever with a postfix of 01, 02, 03 to signify the number of AL's within that.. I have had time when I had to insert AL's or Filters in patches of the apps I build which I do by putting additional postfixes.. such as 01a, 01b. At some places I did have the luxury of renaming the AL or Filter to make way for new AL's or Filters. The biggest advantage of doing this is easily finding the piece of code you are after if you are trouble shooting a particular function that may be causing a problem.. Joe From: David Sanders david.sand...@westoverconsulting.co.uk To: arslist@ARSLIST.ORG Sent: Tuesday, March 24, 2009 1:39:12 PM Subject: Re: ITSM naming convention sucks Hi Doug In my opinion there are problems with trying to do too much with naming conventions for workflow. One of the principal problems is in applying enhancements to an existing application - if you add actions to an active link, do you change the name? If so, your delta definitions file needs to contain a disabled version of the object being replaced, and the new object with the new name too. I try to avoid this unless the active link actions are radically altered so that the existing name would be misleading. What do you do when an active link has 25 actions?? I see no point in trying to include firing conditions in the object name (window open, menu choice etc.) as these can be seen in the object list in the admin tool. In ESS active links tend to be named with abbreviations for APP:FORM/SHR-btnTextDescriptionnn where nn is a sequence number for related workflow if appropriate. They might also contain a suffix Nm/Dlg to indicate if that workflow is designed to run specifically for normal windows, or modal dialog windows. For filters, the only difference is to include the filter execution order like APP:FORM/SHR-620TextDescriptionnn where 620 is the execution order. This lists most filters in the order they will fire. In other words, we try to keep the naming convention as simple as possible while still giving useful information, but retaining existing object names where possible to make applying enhancements easier. As far as support is concerned, you break it and we'll help you fix it. Period. We normally set up copies of client's servers including any customizations so that we can easily troubleshoot issues with them. And support costs you no more for 2000 users than it does for 20 users - fixed price. David Sanders Remedy Solution Architect Enterprise Service Suite @ Work == tel +44 1494 468980 mobile +44 7710 377761 email david.sand...@westoverconsulting.co.uk web http://www.westoverconsulting.co.uk -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Tanner, Doug Sent: Tuesday, March 24, 2009 3:58 PM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks Another reason to write/construct you own solution and follow best practices in naming conventions/documentation/etc. Been doing Remedy for 13+ years, logical naming of objects is important - Custom or OTB. Oh the days of Remedy - Your Business, Your Way! Doug Tanner Gidd how about you, how does ESS standardize naming conventions? -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Lyle Taylor Sent: Tuesday, March 24, 2009 11:50 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks I don't think so. They will support the applications out of the box. They won't support customizations. If you break something with your customizations, they are not obligated to help you figure out how you broke it. They might, but they might not. They are also not necessarily obligated to help you understand their workflow, unless it relates to a documented integration point. Many of the whitepapers they provide are nice, but not strictly necessary. Understand that I would love it if BMC documented their systems better. I just don't think that the statement that it is necessary that they document their naming conventions, or the implied statement that they should document other implementation details, is correct. It would be great if they did, but they are under no obligation to do so. Lyle -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of David.M Clark Sent: Tuesday, March 24, 2009 9:36 AM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks I think that paying
Re: ITSM naming convention sucks
Oh, hark to yea gohd olde dayse when thee naming convention alloweyd 30 characters, and yea needn't use all off them. Wouldst we ever haff thot subject-verb disagreement could arise in an 80-character naming convention, much less heated disagreement? Jennifer Meyer From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Joe DeSouza Sent: Tuesday, March 24, 2009 2:25 PM To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks Thats exactly why I prefer functional names over names that describe what exactly the AL does unless that AL is specifically doing that without being a part of a bigger function. By functional names I mean if there is a set of AL's or Filters that run either as a guide or otherwise, that perform a specific function such as SetCustomerInfo or RetreiveUserData or whatever with a postfix of 01, 02, 03 to signify the number of AL's within that.. I have had time when I had to insert AL's or Filters in patches of the apps I build which I do by putting additional postfixes.. such as 01a, 01b. At some places I did have the luxury of renaming the AL or Filter to make way for new AL's or Filters. The biggest advantage of doing this is easily finding the piece of code you are after if you are trouble shooting a particular function that may be causing a problem.. Joe From: David Sanders david.sand...@westoverconsulting.co.uk To: arslist@ARSLIST.ORG Sent: Tuesday, March 24, 2009 1:39:12 PM Subject: Re: ITSM naming convention sucks Hi Doug In my opinion there are problems with trying to do too much with naming conventions for workflow. One of the principal problems is in applying enhancements to an existing application - if you add actions to an active link, do you change the name? If so, your delta definitions file needs to contain a disabled version of the object being replaced, and the new object with the new name too. I try to avoid this unless the active link actions are radically altered so that the existing name would be misleading. What do you do when an active link has 25 actions?? I see no point in trying to include firing conditions in the object name (window open, menu choice etc.) as these can be seen in the object list in the admin tool. In ESS active links tend to be named with abbreviations for APP:FORM/SHR-btnTextDescriptionnn where nn is a sequence number for related workflow if appropriate. They might also contain a suffix Nm/Dlg to indicate if that workflow is designed to run specifically for normal windows, or modal dialog windows. For filters, the only difference is to include the filter execution order like APP:FORM/SHR-620TextDescriptionnn where 620 is the execution order. This lists most filters in the order they will fire. In other words, we try to keep the naming convention as simple as possible while still giving useful information, but retaining existing object names where possible to make applying enhancements easier. As far as support is concerned, you break it and we'll help you fix it. Period. We normally set up copies of client's servers including any customizations so that we can easily troubleshoot issues with them. And support costs you no more for 2000 users than it does for 20 users - fixed price. David Sanders Remedy Solution Architect Enterprise Service Suite @ Work == tel +44 1494 468980 mobile +44 7710 377761 email david.sand...@westoverconsulting.co.ukmailto:david.sand...@westoverconsulting.co.uk web http://www.westoverconsulting.co.uk -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG] On Behalf Of Tanner, Doug Sent: Tuesday, March 24, 2009 3:58 PM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks Another reason to write/construct you own solution and follow best practices in naming conventions/documentation/etc. Been doing Remedy for 13+ years, logical naming of objects is important - Custom or OTB. Oh the days of Remedy - Your Business, Your Way! Doug Tanner Gidd how about you, how does ESS standardize naming conventions? -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG] On Behalf Of Lyle Taylor Sent: Tuesday, March 24, 2009 11:50 AM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks I don't think so. They will support the applications out of the box. They won't support customizations. If you break something with your customizations, they are not obligated to help you figure out how you broke it. They might, but they might not. They are also not necessarily obligated to help you understand their workflow, unless it relates to a documented integration point. Many of the whitepapers
Re: ITSM naming convention sucks
As per ITSP naming convention the standard format of an Active Link is: *[z][SchemaCode]:[#]-[Field Name/Button/Function]-[Firing Condition][###E]-[Description]-[IndicatorSuffix][Status]* Where z (lowercase) The lowercase z in front of the active link name indicates a Global Workflow Filter Schema Code Schema Code (Reference Schema Code in case of Global Active Link) - 3 Uppercase characters (usually the same as the entry-id prefix of the schema) # Grouping Code: 0 = Initialization (Window Open, Query, Set Defaults, Display, Copy to New) 1 = Execution (Submit, Modify) 2 = Post Execution (After Submit, After Modify) 3 = Close (Window Close) 4 – 5 (Unassigned/Reserved) 9 = In session (Button, Return, Menu/Row Choice, Gain Focus, Lose Focus0 z = Guide (Active Links Called by Guides only) ###[E] Execution Order (3 digits). Append E if Else Action exists Description Functional Description of the Workflow performed Indicator Suffix E = Error N = Note W = Warning R = Run Process Q = SQL G = Call Guide J### - Goto execution order PCDE = Push where CDE is the 3 character code Status + = New Workflow, requires testing (once tested the prefix can be removed) @ = Existing Workflow has been temporarily deactivated # = Existing deactivated workflow with the intent of deleting from the system HPD:INC: ContactSearch_120_GPn-G Even though this piece of workflow doesn’t exist in ITSP, I think this is the breakout. HPD Module Name INC 3 Character Schema Code stored in SYS:Form List (ITSP) and Schema Names (ITSM 7) ContactSearch Field Name 120 Execution Order Gpn (not sure) G Indicator Suffix for Call Guide In my opinion, ITSP followed some best naming conventions. Thanks Mahesh On Fri, Mar 20, 2009 at 8:15 AM, Matt Worsdell m...@worsy.co.uk wrote: Not BMC's fault, ITSM is based on ITSP which was produced by a VAR (name withheld to protect the guilty). -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of ccrashh Sent: 20 March 2009 12:53 To: arslist@ARSLIST.ORG Subject: ITSM naming convention sucks BMC has to be kidding with their ITSM suite's naming convention...for instance: On the HPD:HelpDesk form, the Customer Search button (inexplicably called Contact Search even though it is under the Customer Information section) has several Active Links associated to it (31 or so). If you were to go to the list of active links and sort by name, the first one that appears is: HPD:INC:ContactSearch_120_GPn-G However, the first one that triggers is: HPD:INC:ContactSearch_Info_035_GetPersonInfo Which is 19th in the list of 31 Active Links. WTF. Why would anyone do things this way? How can any real Remedy ARS developer work with this crap without wanting to put his/her fist through the monitor? Here's a tip...fix the naming convention! For example: HPD-INC-CUS:SR-b035-GetPersonInfo ... HPD-INC-CUS:SR-b120-GPn-G --- of course, this should be renamed to something more explicit like: HPD-INC-CUS:SR-b120-CallGuide_CF (CF being an acronym for the ContactFound guide...which I would rename to HD-INC-CF:ContactFound) See, now this naming convention makes sense. Broken down it is the HPD module INC form (though, I would change this to HD probably to match the form's actual acronym) CUS (for Customer - so we know this has something to do with the Customer information on the form) SR - for Search (so if this were the Create button, I would use CR, and MD for Modify) b - for button (other abbreviations would be s = submit, m=modify, mc = menu choice, etc.) 035 or 120 - execution order GetPersonInfo - or other - description of the functionality (can be followed by things like -E for Error, or -G for a Goto, etc.) So, if I were to modify all the ALs accordingly, sorting by name gives us the Active Links in order of their functionality and execution order within that functionality. What BMC has provided is total crap...'natch. And my contract may require me to work on this...double sigh. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: ITSM naming convention sucks
Not BMC's fault, ITSM is based on ITSP which was produced by a VAR (name withheld to protect the guilty). -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of ccrashh Sent: 20 March 2009 12:53 To: arslist@ARSLIST.ORG Subject: ITSM naming convention sucks BMC has to be kidding with their ITSM suite's naming convention...for instance: On the HPD:HelpDesk form, the Customer Search button (inexplicably called Contact Search even though it is under the Customer Information section) has several Active Links associated to it (31 or so). If you were to go to the list of active links and sort by name, the first one that appears is: HPD:INC:ContactSearch_120_GPn-G However, the first one that triggers is: HPD:INC:ContactSearch_Info_035_GetPersonInfo Which is 19th in the list of 31 Active Links. WTF. Why would anyone do things this way? How can any real Remedy ARS developer work with this crap without wanting to put his/her fist through the monitor? Here's a tip...fix the naming convention! For example: HPD-INC-CUS:SR-b035-GetPersonInfo ... HPD-INC-CUS:SR-b120-GPn-G --- of course, this should be renamed to something more explicit like: HPD-INC-CUS:SR-b120-CallGuide_CF (CF being an acronym for the ContactFound guide...which I would rename to HD-INC-CF:ContactFound) See, now this naming convention makes sense. Broken down it is the HPD module INC form (though, I would change this to HD probably to match the form's actual acronym) CUS (for Customer - so we know this has something to do with the Customer information on the form) SR - for Search (so if this were the Create button, I would use CR, and MD for Modify) b - for button (other abbreviations would be s = submit, m=modify, mc = menu choice, etc.) 035 or 120 - execution order GetPersonInfo - or other - description of the functionality (can be followed by things like -E for Error, or -G for a Goto, etc.) So, if I were to modify all the ALs accordingly, sorting by name gives us the Active Links in order of their functionality and execution order within that functionality. What BMC has provided is total crap...'natch. And my contract may require me to work on this...double sigh. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: ITSM naming convention sucks
Ah...that might explain some of the different naming conventions I have seen across modules. Man, this is going to be a pain... ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: ITSM naming convention sucks
It does show the effects of distributed development, but once you figure it out, it really is a much better architecture (or design) than previous versions. --Original Message-- From: ccrashh Sender: Action Request System discussion list(ARSList) To: arslist@ARSLIST.ORG ReplyTo: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks Sent: Mar 20, 2009 7:01 AM Ah...that might explain some of the different naming conventions I have seen across modules. Man, this is going to be a pain... ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are Sent from my Verizon Wireless BlackBerry ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: ITSM naming convention sucks
Matt, Yes. However, when do you think the new owner needs to take full ownership of the current state? BMC decided to take two products and merge them. Then _they_ (not the previous author) released it to customers. IMO: When you sell it, you are responsible for it no matter the original source. It is the vendors responsibility to make it as good (or bad) as they choose. Now with that said... ccrashh, I feel your pain. Yes there are pros and cons to any naming convention. However I have not yet seen one that has zero cons. So no matter what is selected, well, someone will be unhappy. Any and all naming conventions suck. Well unless you happen to be part of the comity that compromises until you all grudgingly agree to a list that no one really wants, but everyone stopped complaining about. Those people likely think that the final result is the Lesser of all evils. (Or they are forced to conclude that they wasted their time producing something that is not worth using.) To be totally clear, my above opinion does not excuse the vendor for any of the following: * releasing a product that is inconsistent with itself * a product that appears to be very dependent on String sorting to understand the relationships between its component parts * a product design that some think borders on developer hostile (But you can buy this or that add on tool to help with this or that.) My opinion is just to point out that age old sayings still apply: You can not keep all of the people happy all of the time. You break it. You bought it. The customer is always right. It is a tough job to try to deal with all three of those ideals at the same time. And I think, in general, customers are becoming more demanding too. However, if we are looking to make suggestions for improvements.. ( I have no idea if any of these already exist in v7.5. Maybe they do. I can only hope. ) ( While they do not apply only to ITSM, I think all of the following would help sales/use of ITSM.) The vendor could provide better ways to navigate from ARS object to object for developers. Things like: Field Properties dialog, with a named menu... How about a button to open the menu object? Related workflow tab: How about a table field with columns that I can sort on. Things like separate fields for all of the following come to mind: Execution order Execute on button Execute on field Execution on Submit, modify, etc Number of If actions list of types of If actions Number of Else actions list of types of Else actions A way to add any object from any object list into a New or existing Packing List. ( I think 7.5 has something like this... but maybe not everywhere.) Basically tools that help the developer to develop based on what is obviously already in the system. And there are a whole set of features/functions that I would love to see added too. :) -- Carey Matthew Black BMC Remedy AR System Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap Pick two. On Fri, Mar 20, 2009 at 9:15 AM, Matt Worsdell m...@worsy.co.uk wrote: Not BMC's fault, ITSM is based on ITSP which was produced by a VAR (name withheld to protect the guilty). -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of ccrashh Sent: 20 March 2009 12:53 To: arslist@ARSLIST.ORG Subject: ITSM naming convention sucks BMC has to be kidding with their ITSM suite's naming convention...for instance: On the HPD:HelpDesk form, the Customer Search button (inexplicably called Contact Search even though it is under the Customer Information section) has several Active Links associated to it (31 or so). If you were to go to the list of active links and sort by name, the first one that appears is: HPD:INC:ContactSearch_120_GPn-G However, the first one that triggers is: HPD:INC:ContactSearch_Info_035_GetPersonInfo Which is 19th in the list of 31 Active Links. WTF. Why would anyone do things this way? How can any real Remedy ARS developer work with this crap without wanting to put his/her fist through the monitor? Here's a tip...fix the naming convention! For example: snip What BMC has provided is total crap...'natch. And my contract may require me to work on this...double sigh. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: ITSM naming convention sucks
Agreed. My personal bug bear is the fact Form Alias settings for some joins reflect other form names. Try opening some of the SIT:Site Alias stuff :( -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Carey Matthew Black Sent: 20 March 2009 14:26 To: arslist@ARSLIST.ORG Subject: Re: ITSM naming convention sucks Matt, Yes. However, when do you think the new owner needs to take full ownership of the current state? BMC decided to take two products and merge them. Then _they_ (not the previous author) released it to customers. IMO: When you sell it, you are responsible for it no matter the original source. It is the vendors responsibility to make it as good (or bad) as they choose. Now with that said... ccrashh, I feel your pain. Yes there are pros and cons to any naming convention. However I have not yet seen one that has zero cons. So no matter what is selected, well, someone will be unhappy. Any and all naming conventions suck. Well unless you happen to be part of the comity that compromises until you all grudgingly agree to a list that no one really wants, but everyone stopped complaining about. Those people likely think that the final result is the Lesser of all evils. (Or they are forced to conclude that they wasted their time producing something that is not worth using.) To be totally clear, my above opinion does not excuse the vendor for any of the following: * releasing a product that is inconsistent with itself * a product that appears to be very dependent on String sorting to understand the relationships between its component parts * a product design that some think borders on developer hostile (But you can buy this or that add on tool to help with this or that.) My opinion is just to point out that age old sayings still apply: You can not keep all of the people happy all of the time. You break it. You bought it. The customer is always right. It is a tough job to try to deal with all three of those ideals at the same time. And I think, in general, customers are becoming more demanding too. However, if we are looking to make suggestions for improvements.. ( I have no idea if any of these already exist in v7.5. Maybe they do. I can only hope. ) ( While they do not apply only to ITSM, I think all of the following would help sales/use of ITSM.) The vendor could provide better ways to navigate from ARS object to object for developers. Things like: Field Properties dialog, with a named menu... How about a button to open the menu object? Related workflow tab: How about a table field with columns that I can sort on. Things like separate fields for all of the following come to mind: Execution order Execute on button Execute on field Execution on Submit, modify, etc Number of If actions list of types of If actions Number of Else actions list of types of Else actions A way to add any object from any object list into a New or existing Packing List. ( I think 7.5 has something like this... but maybe not everywhere.) Basically tools that help the developer to develop based on what is obviously already in the system. And there are a whole set of features/functions that I would love to see added too. :) -- Carey Matthew Black BMC Remedy AR System Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap Pick two. On Fri, Mar 20, 2009 at 9:15 AM, Matt Worsdell m...@worsy.co.uk wrote: Not BMC's fault, ITSM is based on ITSP which was produced by a VAR (name withheld to protect the guilty). -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of ccrashh Sent: 20 March 2009 12:53 To: arslist@ARSLIST.ORG Subject: ITSM naming convention sucks BMC has to be kidding with their ITSM suite's naming convention...for instance: On the HPD:HelpDesk form, the Customer Search button (inexplicably called Contact Search even though it is under the Customer Information section) has several Active Links associated to it (31 or so). If you were to go to the list of active links and sort by name, the first one that appears is: HPD:INC:ContactSearch_120_GPn-G However, the first one that triggers is: HPD:INC:ContactSearch_Info_035_GetPersonInfo Which is 19th in the list of 31 Active Links. WTF. Why would anyone do things this way? How can any real Remedy ARS developer work with this crap without wanting to put his/her fist through the monitor? Here's a tip...fix the naming convention! For example: snip What BMC has provided is total crap...'natch. And my contract may require me to work on this...double sigh. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor
