Yes, it works exactly same way. (I did not have requirement for CTM:People so did not try that).
Also there is knowledge article KA353519 Best Regards, Uday -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of strauss Sent: Wednesday, November 16, 2011 12:41 PM To: arslist@ARSLIST.ORG Subject: Re: Overlay objects named __o : common knowledge? There is a patch to the 7.6.04.01 arserver.exe for at least one bug with auditing for ITSM overlays that we obtained in July by opening an issue with support. There may have been more defects identified since then, but applying this patch allowed the OOTB audit logging on the Incident and related ITSM forms to resume (that had stopped after upgrading to 7.6.04.00) after some "jiggling" of the form: I had to open the following overlaid, audited forms in Base Development Mode, toggle Form Properties - Audit - Audit Only Changed Fields to Yes or No, then back to Default (no saving of form required), and then the overlay began showing the correct Audit Log Form information as well. HPD:Help Desk PBM:Known Error PBM:Problem Investigation PBM:Solution Database TMS:Task After that, editing any existing records in these forms created new Audit Log entries. It took a restart the SQL Server underneath the ARSystem db before auditing was restored to the CTM:People form. Toggling the Form Properties was not enough. Action Request System(R) Server x64 Version 7.6.04 SP1 HotFix 01 201107051610 I don't doubt that there are other hotfixes that came out after this one, and of course now there is SP2. All bets are off on SP2; based upon our problems so far with just the installers, it may re-introduce problems that we got hotfixes for, so I will have to test everything again. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Scott Parrish Sent: Wednesday, November 16, 2011 12:03 AM To: arslist@ARSLIST.ORG Subject: Re: Overlay objects named __o : common knowledge? It's my understanding that this issue is a known defect. Scott -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Uday Joshi Sent: Wednesday, November 16, 2011 12:58 AM To: arslist@ARSLIST.ORG Subject: Re: Overlay objects named __o : common knowledge? Hi, One more challenge I am facing that the auditing is disabled on the overlay form. The "FormAppObj" guide has a section on it but its not elaborate enough. Can anyone share hands on experience on how to enable this for overlaid forms. Best Regards, Uday Joshi -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of strauss Sent: Friday, November 11, 2011 5:06 AM To: arslist@ARSLIST.ORG Subject: Re: Overlay objects named __o : common knowledge? The __o syntax was described in the most detail in the Migrator docs, where it tells you how to compare overlay to overlaid objects and vice versa. Eventually it appeared in the 7.6.04 upgrade docs, which were very short on detail and accuracy initially. The Developer Studio hides it (the fact that there is an __o form once you overlay the original), while it is VERY obvious in Migrator, and has been since day one. You will also see all of the __o forms in the arschema table, where they get their own unique schema ids. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of John Luthgers Sent: Thursday, November 10, 2011 2:11 PM To: arslist@ARSLIST.ORG Subject: Re: Overlay objects named __o : common knowledge? Hello Kaïs, i was digging into this since 7.6.04 has been released to add overlay support to ARInside. But I don't know what your question tend to exactly. While i know that overlay objects have "__o" added to it, i decided to hide this fact in the ARInside workflow documentation completely. I think this is to some point API internal information. And for future ARS versions which might support more than just two worklow layeres we don't know what BMC does with this naming convention. Developers who work with overlays for a while will surely sooner or later know about this object naming. But most customers are still using an odler version. Currently, I wouldn't say its common knowledge. John Am 10.11.2011 12:05, schrieb Support: > ** Hello List, > > As we are pre-alpha testing the new version of ARSmarts, we are > wondering if the fact that overlay objects are called /objectname/__o is > common knowledge, or if none of you was aware of this before reading > this sentence :-) :-) .... > > Pls let us know if you knew by answering to this email to the list, or > directly to supp...@arsmarts.com. > > Thanks in advance. > > Kaïs > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
