Recently I cleaned up and refined all our OIRs, eliminating redundancy and documenting thoroughly. Had to accomodate a few special cases. We use both autonumber and manual numbering - for auto, we use a lot of prefixes and suffixes.
For OIR's and Numbering, I looked thru all the PTC on-line help in Windchill, and then all the PDF's, and then all the case solutions and other knowledge base articles about how to disable / enable autonumbering - and found no less than 37 places where it's specified how to do this - each with slight variations a little different intention. I tried most of them - some work, some don't. A lot have typos. None really take into account the fact that you may override Org vs. Site; Library vs. Org, etc. Sitting down to read all the PTC info about OIR's and numbering in one shot results in a lot of scrambled brain cells - but the summary can fit on 1/2 page.
We tried various major approaches to OIRs and discussed many times:
- Make changes at Site
- Leave Site alone and for any overrides, create at Org
- Include all elements at Org (e.g. Number, Folder)
- Include only the elements that are overridden <<< this is the major way we have these now
- Use Product/Library OIR's only for special cases
- Given Org-level for most of PDM, create in each Project also to carefully control Project behavior (include in Project templates)
/////
By the way, I recently updated our query builder report on OIR's - allows one to gather all OIR code in one place - either for all types or an entered type / type root. Helps us quite a bit. It's especially helpful if you have OIR's for a type that selectively override - e.g. for WTPart, one at Site, one at Org for the root type, one at Org for a subtype, one in a special Library for the root type, etc. QML for this attached - hopefully will be helpful.
