Obsolescence - how are others handling?

[kpritchard]

Hi All,

I'm looking for ideas on how to use OOTB functionality to create linkages betweenan Obsolete WTPart and it's direct replacement. Ideally, a chain of supersession (both forwrad and backward) could be generated... perfect world, automatically in the WTPart details UI (or custom tab) or at minimum a report could be generated.

Obsolescence and supersession are not new concepts so I'm thinking there must be a way. Any ideas?

[AL_ANDERSON]

10.2 has Part Supercession links from part master to part master. I would
recommend using that functionality for this type of relationship. We have
customized a kind of part supercession link using a sub type of ECTs with
a custom service to mark part masters as superceeded, and then another
customization to the part icon delegate to display a "displaced" icon for
all versions of a displaced part. We also have a custom report to show
"part displacement history" backwards and forwards. We even have two
"types" of part displacement: one for new manufacturing, and one for
service parts.

However, if part supercession had been available 8 years ago, then we
would have used that.

Al







[solutions] - Obsolescence - how are others handling?

Keir Pritchard

[BobLehman2]

10.x tidbits - Custom Watermarking

I have been doing most of my work in 10.1 lately and have come across some new tidbits that I think are interesting and quick to implement and I would like to share them. My reason for doing this is purely selfish - I am a consultant and I am looking for some project work and this is the best place I know of to let people know that. But I want to provide some value to the list not just troll for work. So here goes.


In previous releases of Windchill you can Watermark or Stamp a document with only one Watermark which is configured through the Visualization Configuration Administration utility located on the Site Utilities tab. In version 10.x there is call back or hook that can be implemented to override the default stamping behavior. This callback allows for the calling of a custom class that can be used to implement what ever Watermarking scheme is required. For example for EPM documents you might want a Watermark that targets a Title block of the drawing or for WTDocuments you might want a cover page. These capabilities can be added via Java and calls to the Adobe Livecycle server using the Adobe DDX language. PTC supplies a simple OOTB example of that adds a coversheet to an existing PDF file when the file is in a RELEASED state. This java code is located in

$WT_HOME/prog_examples/wvs/com/ptc/wvs/LiveCycleDelegate.java

When the code is compliled and deployed, it is activated by changing the wvs.properties to call the handler.

For example:

<property name="edrload.livecycle.delegate" default="com.ptc.wvs.LiveCycleDelegate/getLiveCycleInvocationParams"/>

After restarting Windchill this handler will now be called and a cover page will be added to each RELEASED WTDocument.


This process is documented in detail in the Windchill Visualization Services Guide which is available on the PTC Customer Support site.

The capabilities of the DDX language are documented in the Assembler Service and DDX Reference which is available on the Adobe site.


If you have interest in how this works and have questions, please feel free to respond to the group or to me directly.

-

As I create these tidbits I will post them to the group and keep them archived on my company website.