Ability to link a document to a wtpart which is in the released state.

[bverbunt]

Ability to link a document to a wtpart which is in the released state.

Currently it's only possible to link a document to a wtpart when the user has the rights to check out the wtpart (modify right). Usually for a wtpart which has a "released"  the user has no right to modify the wtpart. This means that it's not possible to connect a document to a wtpart without revising the wtpart in order to bring it back to the "in work" state. A possible work around is to give users modify right in the "released" state. However this also means that the users is able to edit the wtparts meta data and to connect other wtparts to the wtparts, which is very dangerous when you send wtparts to ERP on release.

It would be very helpful if there was a separate user right for linking instead of the single edit right.

[BjoernRueegg]

Thanks for the Idea!

I belief a new relationship would be necessary to realize this feature. It would be nice to have both. e.g. a calculation mus be linked with the describe relationship, but e.g. a measurement report which is done after production should also be possible to connect to a released part.

The problem is also the parent child check (business rules). This documents shouldn't be tested on their lifecycle state.

[GregoryPERASSO]

Hello

may be you can do that with "configurable links" in 10   (and 9.1)

Your can easily create new types of links (master links, reference link, describe link) with Type Manager and a little configuration in xml files

And define rules for type of objects to links together (for example WTPart and WTDoc subtype "measurement")

and define cardinality. for example the WTDoc as parent owner of the link. so it will be the doc that should be checked out, and not the released WTpart

regards

Gregory

[ChrisPLM]

Hi

I understand why PDMLink works that way as adding documents in the wtpart implies changing its definition.

Something similar to what Gregory is saying is that part of the OOTB functionality, there could be a type or an association type which allows adding documents without iterating the wtpart.

It would then be up to the business/entreprise to define its rules as to know which document will require the wtpart to be iterated (there needed a new revision if released) and which one not.

Obviously such document will not be reality part of the wtpart definition and be considered as "secondary" or lower level than documents which require wtpart to be iterated.

Best regards

Christophe

[GregoryPERASSO]

Yes Chris,

There's one link OOTB that behave like that. the "image" link between WTPart and a 3d CAD model ...

mostly use for "alternatives" CAD representations of the same part. like for example a same wire with different routing in an asm ... You can add a new CADdoc (new routing), without iterating the WTPart, cause its definition does not change ....

If you've got the "customization Info Modeler" option , you can create from scratch your own link .. but need more advanced customization capabilities .. update DB and model ... UI and processors ....etc ...

regards

Gregory

[Marco_Tosin]

We have a customization, written by a PTC partner consultant, to do this.

Via a WTDocument custom IBA we have a box where we insert WTpart number (separates by a comma if more then one) then, at check-in, customization iterates WTDocument with admin rights regardless ACL rules.

We can't provide customization, but I hope this comment could be useful.

[JeffZemsky]

In 10.2 M020 there is a Configurable Link type called Revision to Revision which will support the ability to link a Document to a Part without iterating.  This will enable you to have certain Document types that can be linked to a Part after its release without having to do a Check out.

Information can be found here:

http://support.ptc.com/cs/help/windchill_hc/wc102_hc/index.jspx?id=WCCG_UICust_CustomizingPSE_ConfigRevLinks&action=show

[HugoHermans]

Hi Bas,

We tackled this issue by creating view versions for the WTPart.  Released or not released, when 'Production' or 'Quality' or 'AfterSales' want to associate their proper documents to a WTPart, they do it in their proper view version.  They will never feel cut-off by access rights from their documents.  And for the rest of the organisation, it's obviously clear where the additional documents come from.  Although is't not generally adopted (yet), people that know and use it, feel comfortable with it.

Regards,  Hugo.

[soerton]

Does this customization allow for these documents to be collected as part of an ECN affected objects collection?

[vbelev]

Hi Jeff,

same question:

- does this Rev-to-Rev Config Link allow collection of objects in ECNs?

- are we able to use the OOTB ESI BOM publishing to SAP with this configurable link ?

- do we need a separate custom table under Related objects to display / link those objects?

- is the behavior of the Rev-to-Rev Link similar to the Described By link?

Thanks & Best Regards,

Valentin

[JeffZemsky]

Valentin,

1)Today we do not support collectors on Configurable links

2) I'll have to check on ESI

3) You need to configure the Tables in.  The tables themselves are not custom.  There are examples in Help.

4) A little different as the name infers - they are revision to revision links rather than master to version, but you can carry foward on a revise.  Eg Revision A Part refers to Revision B Doc.  You can continue to iterate Revision B Doc and it Revision A Part will still be related to the latest Revision B doc.