as a matter a fact when we DSO all incidents, Changes and Assets.. How is this gunna work.
That will bring my numbers up a little.. Is there a special Procedure for these ? Considering this is for an Important BMC client... On Tue, Nov 8, 2011 at 2:57 PM, patrick zandi <remedy...@gmail.com> wrote: > Dave: > Question: is there a way to add DSO fields into a form without overlays? > IF not then why were are not these fields added by BMC and made the core > before I have to do an overlay? > DSO is bmc's product, so I think this might just have been an overlook in > the release of the product? > What about AIE? is AIE in the same boat? > What about IBRSD? is this in the same boat? just asking.. > > I could use a little clarification.. > > > On Tue, Nov 8, 2011 at 2:41 PM, patrick zandi <remedy...@gmail.com> wrote: > >> Well if you do DSO you have to change the form to get the DSO fields into >> the FORM... >> So I do not know where you go with that... >> >> >> >> On Tue, Nov 8, 2011 at 2:29 PM, Easter, David <david_eas...@bmc.com>wrote: >> >>> ** >>> >>> Primary reason is that you shouldn’t be modifying quite a few forms… >>> Best practice recommendation is:**** >>> >>> ** ** >>> >>> **1. **Utilize the OOTB products as delivered as much as >>> possible. **** >>> >>> **2. **If a change in functionality is needed, *add* to the >>> application – not modify. Create new fields and workflow rather than >>> modifying existing objects.**** >>> >>> **3. **If and only if you cannot achieve desired capabilities by >>> extending the application, then utilize overlays to modify the provided BMC >>> object.**** >>> >>> ** ** >>> >>> In addition, were overlays provided OOTB, then you’d have hundreds (if >>> not thousands) of overlays that are exactly the same as the base objects. >>> Since the goal is to have overlays only for those objects that are modified >>> (in fact, best practice is to delete any overlays that are not needed), the >>> value of overlays would be diminished. Overlays should be there only for >>> objects that are modified so that they are kept to a minimum and quickly >>> identifiable. **** >>> >>> ** ** >>> >>> -David J. Easter**** >>> >>> Manager of Product Management, Remedy Platform**** >>> >>> BMC Software, Inc.**** >>> >>> **** >>> >>> 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.**** >>> >>> ** ** >>> >>> *From:* Action Request System discussion list(ARSList) [mailto: >>> arslist@ARSLIST.ORG] *On Behalf Of *patrick zandi >>> *Sent:* Tuesday, November 08, 2011 11:18 AM >>> >>> *To:* arslist@ARSLIST.ORG >>> *Subject:* Re: 7.6.04 - dev studio (read only) cannot add fields**** >>> >>> ** ** >>> >>> ** **** >>> >>> Dumb Question: so If you always have to do this:: Why didn't bmc in its >>> wisdom create all forms with overlays automatically, since that is all you >>> can change.. I am modifying quiet a few forms and my thinking cap is >>> thinking 8-)**** >>> >>> >>> >>> >>> -- >>> Patrick Zandi >>> >>> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ **** >>> >>> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ >>> >> >> >> >> -- >> Patrick Zandi >> > > > > -- > Patrick Zandi > -- Patrick Zandi _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
