if the purpose is to promote WTdocument and EPMdocument at the same time under one flow, why not putting them together in a WTpart.
for the WTpart represents the definition of the "product" (product as information to manage not necessary as product we sale to our customers), the WTdocument and EPMdocument are only complementary information to fully define the WTpart.
When promoting the WTPart you can collect the dependencies (WTdoc and EPMdoc) and promote them all together.
Now, PTC has to improve something. If I have a WTpart in my workspace and do a Set State, The Set State window allows me to collect object. If I do a Set State from PDMLink, there is no collector. This is one amoung other inconsistency we found about PDMLink.
Forgot to mention, as Raimondas said it. You can also use ProjectLink
Share or check out from PDM anything you need into your Project, create new and once the project is completed, send everything you need at once back to PDMLink
Really, I can't see the advantages in being able to add WTdocument into your ProE workspaces. I think it is down to working habits/methods
All best in finding your most suitable solution
With regards to your statement below are you using Ilink 9.x or PDMLink 9.x?
You can Promote CAD, Docs, and Parts at the same time. The only gotcha is you need to be able to select all the objects at the same time. There are several ways this can be accomplished.
If the objects aren't related, it is very difficult to promote them together, unless they are in the same folder, similar name/number, or are of the same object type. There have been a couple of threads here before stating that it's generally a best practice to not promote unrelated items together. Of course every business has different reasons for doing what they do.
If all of these options don't get you what you need, and you are using PDMLink 9.0 or higher, you can use an ECN without an ECR, possibly soft typed if you want to have more control over "Production Changes" vs promotion type changes, which we would consider "Engineering Changes". The workflow may need to be modified and the process tweaked a bit, but the User Interface for ECNs allows greater flexibility in addition and removal of items to an ECN, even after it's already been created, it can be Reworked and items added and removed.
In Reply to Paul Marshall:
With Windchill I think it goes deeper than workspaces though, as some recent
posts have been discussing, Documents and Pro/E objects must be promoted
Not sure if somebody is using any open source PDM system to manage CAD data. Definitely I can see some movement in that direction but the lack of common BOM data exchange information and process information does not help a lot (Especially for companies that are doing business internationally)