cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance copy/paste function to support change objects

Enhance copy/paste function to support change objects

Copy and Paste action on change object (problem report / change reques / change notice) throws error "Object that is copied can not be pasted in this location" in Windchill PDMLink.

Please enhance the copy and paste function to support change objects.

5 Comments
Newbie

We needed this and ended up adding another customization where a user can copy a change notice from any existing change notices.

Newbie

Hi Yogesh,

have you done the customisation by yourselfs? Or PTC? What would be the price-tag for such a customization?

Cheers, Bertram

Newbie

I added myself. If you are familiar with Java customization with Windchill, it is straight forward. Its not copy-paste as you mentioned, but acceptable by our users. Here is how I did it.

1.  Add new attribute "CopyCNFrom" to Change Notice

2. Add a listener for Change Notice creation which does following

     - reads value for attribute "CopyCNFrom" (which becomes source Change Notice)

     - Copy a few defined attributes from source CN to new Change Notice

     - For each Change Task (source CT) in source CN, it creates new Change Task in new CN and copies all attributes from source CT

We asked users to "Not" submit Change Notice right away. This gives them opportunity to validate/modify new Change Notice/Task.

Newbie

not bad, think I could convince my users to accept something like it. Thanks for sharing your idea!

Peridot

In 10.2 F000 we added Change Notice template capability so you can pre-create a template for a Change Notice including support for types with pre-filled in attributes and a set of pre-defined Change Tasks.  The Change Tasks can also support types, sequences defined, attributes pre-filled in and you can select if Affected Data should be added to them.  If you select to add Affected data you can also use Association constraints then the Affected Data will only go to the appropriate Change Task.  For example if you have a CAD Change Task type with an association constraint to only have EPMDocs on CAD Change Task it will only be seen on that Change Task.