One 'problem' with it would be if they at some point in the future decide to install a newer version of ITSM...they would then have custom objects with the same names as 'base' objects....but I don't know enough to know if this is a scenario that needs to be worried about or not.
I have seen many posts from people that essentially say 'I plan on staying in base with my custom stuff, and not deal with all of that other overlay stuff'...and that's cool, but they continue to put themselves in front of the wrecking ball that BMC is trying to help all of us avoid by creating this overlay mechanism. On Fri, Sep 13, 2013 at 12:15 PM, Jason Miller <jason.mil...@gmail.com>wrote: > ** > I agree. I think what is a bit extra confusing in Raj's situation is they > have a mix of Help Desk 5.6 and other custom development. While HD 5.6 is > technically BMC code at this point Raj's company pretty much owns it (maybe > not legally but in practice) and might as well consider it custom. > > So where to draw the line? SHR:People and SHRCFG:OuterJoinPeopleUser as > mentioned are not AR System core forms but are from ITSM/Help Desk. Since > this is an environment you plan on having for a while (if I remember > correctly), if it were me I would convert those to custom. > > The best course might be to do a fresh install of just AR System to get a > current list of out of the box forms and workflow. Any object that exists > in that fresh system I would verify is base in your existing system. If > you customized something in the existing system and it exists in the fresh > system verify it was done using overlays. All objects that do not exist in > the fresh system should be converted to custom. That will get you synced > up with how BMC expects an 8.x system to be layered. > > LJ, anybody else with overlay experience, does this sound about right? > > Jason > > > On Fri, Sep 13, 2013 at 9:38 AM, Brian Pancia <panc...@finityit.com>wrote: > >> ** >> >> Doug put it best a few weeks back. Leave base development mode for BMC >> and everything else in best practice mode. Why the need to jump between >> modes? 9.9 out of 10 times best practice mode will meet all your needs. >> The other .1 is because BMC wants to make changes to their code in base >> mode. There are ways to creatively use the different modes. However, >> there are certain risks. At the end of the day best practice mode and >> overlays are there as a huge benefit, so use that as an advantage. Jumping >> between modes will just lead to a lot of issues. >> >> >> >> Brian >> >> >> >> ------------------------------ >> *From:* Action Request System discussion list(ARSList) < >> arslist@ARSLIST.ORG> on behalf of Raj <ravi6...@gmail.com> >> *Sent:* Thursday, September 12, 2013 5:05 PM >> >> *To:* arslist@ARSLIST.ORG >> *Subject:* Re: Using BPCU while ARS Upgrade? >> >> ** >> Thanks everyone for their responses. >> >> Spent quite some time reading on posts related to Overlays, BPCU, >> Developer Studio 7.6.04, etc...and trying to understand what all it means >> and implies. >> Here's the situation I am in now(lil' confused), need some advise from >> experts in here: >> As mentioned in the original post - *[While running the upgrade >> installer to v7.6.04(from v7.1), we had to delete User and Group >> forms(without this step upg installer was failing) and installer recreated >> them again. During this process we lost customizations to User & Group >> form(s).]* >> -User form - recreated by Installer OOTB - converted to overlay - added >> custom fields...done. >> -Customizations - We had some customizations around user onboarding >> process which uses Outer Join between SHR:People and >> User(SHRCFG:OuterJoinPeopleUser). It appeared to be that this form was part >> of OOTB Remedy in version 5 and in my company, we heavily used this form >> for customizations and created customer user onboarding process. But looks >> like in later versions on Remedy BMC dropped this join form. >> In short, I am on ARS v7.6.04 with User, SHR:People and >> SHRCFG:OuterJoinPeopleUser as Overlays and some workflow which I had to >> modify and re-import/modify as Overlays.(Manually created overlays) >> >> Based on the above info, I have couple of questions: >> 1. Upgrade to ARS v8.1. Is it ok to upgrade to ARS v8.1 with only the >> above listed forms/workflow as Overlays and rest all are still as >> Base(Customization Type - Unmodified). As BMC recommends to convert either >> into Overlays or Custom objects(Ideally). But read some posts where folks >> encountered issues while using BPCU and had to do manual rework later on. >> Basically, would like to avoid these issues and manual work and hence do >> not want to run BPCU/or convert into Overlays or Custom objects. >> Did anyone had the same situation where only few objects you converted to >> Overlays & Custom but most you left to Base(Unmodified) and have gone >> through successful upgrade to ARS v8.1(or 8.0, etc) >> 2. Future Customizations: Now since I have mix of objects some are >> Overlays and most are still Base(Unmodified), how to decide to do custom >> development going forward. So e.g., If customization is needed later on - >> add some workflow to join form SHRCFG:OuterJoinPeopleUser(Overlaid) - it is >> not available in Base Development Mode(BD) so do I just do it in Best >> Practice Customization(BPC) Mode or convert it from Overlay to Base and go >> to BD mode and then do development. So,basically it is kind of challenge to >> juggle between Base Development Mode and Best Practice Customization mode >> to do development for a same feature. >> >> Sorry for the long post, still trying to understand on Overlays... >> >> Please advise. >> Regards, >> Raj >> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> DISCLAIMER: The information contained in this e-mail and its >> attachments contain confidential information belonging to the sender, which >> is legally privileged. The information is intended only for the use of the >> recipient(s) named above. If you are not the intended recipient, you are >> notified that any disclosure, copying, distribution or action in reliance >> upon the contents of the information transmitted is strictly prohibited. If >> you have received this information in error, please delete it immediately. >> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
