Need to understand how to attach a representation of a particular Part/Assembly to the Change notice

[slandge]

I am using Windchill PDMLink Release 12.0 and Datecode with CPS 12.0.2.0

We need to understand how to attach a representation of a particular Part/Assembly to the Change notice
- Representation will have markups and Notes explaining the changes for the part

Here are the errors that I faced
We need to understand how to attach a representation of a particular Part/Assembly to the Change notice in Windchill
- Representation will have markups and Notes explaining the changes for the part

[d_graham]

I recently wrote a utility that can be expanded to do what it sounds like you need automatically.

It will automatically attach various file types (igs, pdf, dwg, dxf, step, whatever) created via publishing to other objects.

This could certainly include Change Objects or any object that can hold content.

And it does it without duplicating the file(s) created during publishing. We are reusing the files created during publishing however the attachments are created with a filename that is different (more appropriate) than the OOTB filenames generated during publishing.

If duplicate attachment filenames exist the existing ones are automatically delete and new ones added.

The attachment also get a Comment stating that they were added automatically and they came from the Representation of object X and were derived from object Y.

Object X and Y could be the same object unless object X is a WTPart.

It works great and is bombproof. 😁

David

[HelesicPetr]

Hi @slandge 

Check if the annotation exists on the object

Add the object to a Change Task

And  right click on the object in the affected table

Edit Annotations

In Associated Annotations wizard use the green +

Select your annotation and click ok 

Result in the Change Task Affected Objects Table 

Hope this can help.

PetrH

[avillanueva]

Side comment: Would love to have the ability to do this for Resulting items to support reviews.  Attaching representations against affected objects supports the model of fully documenting changes to existing, released items. What is lacking is support for active reviews against to be released, revised or new items in resulting items section. It should support both as a way of communicating issues noted during review of those items.