Documenting the underlying DB is a great idea! Joe, you rock! Jason
On Tue, Oct 11, 2011 at 1:11 PM, Joe Martin D'Souza <[email protected]>wrote: > That documentation is a work in progress, but we decided to publish it so > it becomes an available resource for those who want to access it while its > being documented.. > > To answer Christine's email, it’s a single repository for all AR System > based applications such as Incident, Problem, Asset and Change which include > the CMDB component. > > Maybe I'll add a section about the underlying DB in that documentation.. > > Joe > > -----Original Message----- From: Misi Mladoniczky > Sent: Tuesday, October 11, 2011 2:02 PM Newsgroups: > public.remedy.arsystem.general > To: [email protected] > Subject: Re: Remedy DB / customization - Basic question > > > Hi, > > And here is a document at BMCDN: > https://communities.bmc.com/**communities/docs/DOC-17063<https://communities.bmc.com/communities/docs/DOC-17063> > > Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011) > > Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11): > * RRR|License - Not enough Remedy licenses? Save money by optimizing. > * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. > Find these products, and many free tools and utilities, at http://rrr.se. > > >> Trying to understand how Remedy works from a customization perspective.. >> >> We have Incident, Asset, Change and Release Management currently running >> in >> our environment, 7.5 >> >> Is there a DB for each module or does Remedy contain 1 DB that all >> modules >> map to? >> When we customize (add a field to a form), how difficult is that? >> Can a new field be mapped to an unpopulated field in the DB? >> What are the best practices for customizing? (right now, looking to >> customize Incident) >> >> Any guidance would be greatly appreciated! >> >> thanks >> c >> **************************************************************** >> ********** >> This e-mail and any files transmitted with it may contain >> confidential information and is intended solely for use by >> the individual to whom it is addressed. If you received >> this e-mail in error, please notify the sender, do not >> disclose its contents to others and delete it from your >> system. >> >> **************************************************************** >> ********** >> >> ______________________________**______________________________** >> ___________________ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" >> >> > ______________________________**______________________________** > ___________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > ______________________________**______________________________** > ___________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
