Agreed. The concept I keep questioning is which objects actually get changed during an upgrade? The base form, obviously, but is the overlay changed as well? My form overlays appear to retain the version information from their creation - in my case 7.00.00 - but they also appear to have been modified during the upgrade to 7.6.04. When I compare the CTM:People__o overlay created by BPCU on the reference server (where it has not been upgraded to 7.6.04) to the same overlay on the upgraded staging server, they are both still BMCVer=7.00.00, but the one on the upgraded staging server has over a dozen more new fields that were added in 7.6.04 (like Vendor Assignee Groups (60900)), plus my four custom fields. I guess the overlay will always reflect the version number from its original creation, but it is supposed to pick up everything on the upgraded base form while retaining your customizations. In this case, it also dropped at least one field from 7.00.00 - Locale (160) - from both the base form and the overlay, when upgraded to 7.6.04.
I think I got confused about how this was _supposed_ to work since I had 6 new Audit forms created by the 7.6.04 upgrade that were created as version 7.6.04, but overlaid with 7.5.00 overlays (which I have since deleted). That had to be an error. I guess we'll have to see what really happens to overlay/overlaid object pairs when 7.6.04.001 is applied. 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:[email protected]] On Behalf Of Murnane, Phil Sent: Friday, April 22, 2011 9:54 AM To: [email protected] Subject: Re: ARS 7.6.04 Form Overlays - nextId increments Misi: I just checked an export of some custom workflow, and even workflow attached to custom fields on an overlay form+view reference the form name without the "__o". If we think of the features delivered by ARS as a stack, with higher-level features dependent on lower-level features (similar to the OSI model), then I'm guessing that the overlay feature was inserted fairly low in the stack, and features above it are mostly unaware of its existence -- all they see is the same old presentation/surface they would have seen in 7.6.03. This is just a guess on my part, though. FWIW, --Phil -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Misi Mladoniczky Sent: Friday, April 22, 2011 09:26 To: [email protected] Subject: Re: ARS 7.6.04 Form Overlays - nextId increments Hi Phil, Well, you can also add fields that are overlay, and in that case workflow can be attached. This means that a lot can be attached to the overlay schemaId. My guess is that you get a copy of everything as soon as you create an overlay form+view. I have exported an overlay form, and you get two versions of the form. The base, and a complete overlay copy with added fields etc. They have probably put the complete copy of the form+view in the application repository in the database. Everything except the T-, H, and B-tables who are still kept together as one. Best Regards - Misi, RRR AB, http://www.rrr.se Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10): * 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. > I'm guessing you're right, Misi. I tried to query a CTM_People__o view > once, and couldn't. Perhaps the record in the arschema table is primarily > to support deleting an overlay? > > --Phil > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Misi Mladoniczky > Sent: Friday, April 22, 2011 02:17 > To: [email protected] > Subject: Re: ARS 7.6.04 Form Overlays - nextId increments > > Hi, > > These are only guesses, based on your results, but I think that the > important nextId-number would be the base-form-arschema-record (without > the __o). > > Best Regards - Misi, RRR AB, http://www.rrr.se > > Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10): > * 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. > >> Okay, maybe not... >> >> NTE:SYS-Define NT Events is schemaId 606 >> BPCU created NTE:SYS-Define NT Events__o as schemaId 2032 because I >> added >> some notifications and that required additional attributes in the >> Notification Event field. >> >> NTE:SYS-Define NT Events 7.0.03 had 95 records and a nextId of 118 >> NTE:SYS-Define NT Events__o has a nextId of 118 - picked up when it was >> created by BPCU >> >> After the upgrade to 7.6.04... >> NTE:SYS-Define NT Events 7.6.04 has 151 records and a nextId of 3356 >> (Next-ID-Block-Size: 100 during upgrade) >> NTE:SYS-Define NT Events__o remains at a nextId of 118 >> >> ...so they do NOT stay in sync. >> >> 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:[email protected]] On Behalf Of strauss >> Sent: Thursday, April 21, 2011 1:47 PM >> To: [email protected] >> Subject: ARS 7.6.04 Form Overlays - nextId increments >> >> Observations: >> On my upgraded 7.6.04 system, there are now TWO schemas: >> HPD:Help Desk (schemaId 993) >> HPD:Help Desk__o (schemaId 2052) >> >> There are still the usual T, H, and B tables for 993, but NONE defined >> for >> 2052. On first glance, schemaId 2052 appears to exist ONLY as an entry >> in >> the arschema table. Since it does not have a T-table, the actual data >> for >> my custom fields must still be stored in T993, correct? >> >> Both tables have the same nextId - 59161. >> >> Which one do I set to 100000 if I want to create test tickets in the >> overlaid system? Both? Will they increment together? If not, what >> happens if you ever decide to delete your form overlay and go back to >> the >> origin object... will the nextId value be out of sync? Inquiring minds >> want to know... >> >> No I haven't tested yet - I have to get to a point where I can easily >> roll >> the db back after I (potentially) screw it all up. >> >> Christopher Strauss, Ph.D. >> Call Tracking Administration Manager >> University of North Texas Computing & IT Center >> http://itsm.unt.edu/ >> > > ____________________fields etc added ___________________________________________________________ > 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"
