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"
