We are exploring the use of object subtypes in our PDMLink implementation and have a couple of questions for everyone that would care to answer and see other people's responses as well:
* Are you creating object subtypes, such as WTPart subtypes, EPMDoc subtypes and so forth? * If not, why are you not using the subtype functionality? (can be as simple as "I didn't know we can") * If yes, what object types are you creating subtypes for (WTParts, EPMDocs, etc.)? * If yes, what reasons have you decided to leverage the subtyping functionality? (i.e.: attribute control, workflow control, etc.) This is pretty much the heart of the question. * If yes, what drawbacks and/or pitfalls exist when using subtypes? (i.e.: cannot switch an object from subtype to subtype, cannot delete subtype if used, etc.) * This is an extension of the third sub-question above: What are the uses for subtyping that you may be aware of? * What are the various uses for attributes on WTParts that people are currently leveraging? (i.e.: workflow routing, searching and finding data based on those attributes, smart numbering, etc.) * What drawbacks have you experienced with using attributes on WTParts? (i.e.: cannot delete them from the attribute manager once used, etc.)
Please feel free to answer any or all of the above questions that you may have some input on.
I will catalog all answers, summarize, add info from my research, and post by EOB this Friday (of course, this depends on whether or not I get any responses.)
Much thanks in advance.
Principal Engineer Alcon, Inc. Ph: 949.753.6762
This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.