Maybe you have errors after the rehost process.
You changed the name of windchill host name?
Maybe you have errors after the rehost process.
You changed the name of windchill host name?
how establish the link parts between WTP and CAD doc for bulk parts close to 80k
in our present PDM we had establish the link between drw and part master data(same config as WTP in windchill)
but in windchill the WTP is configured to prt and asm.
how to block the problem request and change process request for the CAD and WTP in work in progress state
Could you send or attach the entire MS log from the startup?
Hi all,
We are in wc 11.0
We are going to use Part Described by document links.
2 questions.,
1. How to show that a used Revision of a document is the Latest Revision or Not Latest Revision? (Remember this is a Described by link)
Strangely the OOTB system attribute "Latest" is for Iteration. Is there OOTB system attribute to know if it is the latest Revision?
2. Is there preference or property to delete from the "Described by" link ---the old Revision of the document and link the Latest Revision of that document?
Because user will not know that the connected document is not the latest Revision. There is a high need for this.
Is this an enhancement done in WC 11.0 or do we need to do customization?
Thanks & Have a nice day!
Hari
Attaching the MS log.
I didn't get any errors after rehost. System is up and running fine but on running WinDU, these errors are coming up.
Thanks for bringing this up. We're having at the moment the same problem with a customer.
Thank you so much!
I'll send this over to my Windchill admins to incorporate.
Thanks Greg, this helps.
Do you have a specific business use case to use only "Describe link" instead of "Reference Link" where the link is Version-->Master unlike describe link which is "Version-->Version".
Yes, there are some use cases. E.g. Software binary code, calculations,.. Documents which are revision specific.
Most of the time the problem starts with the change. In the CN the user revises the WTPart and e.g. the CAD-Document. But then he revises also the calculation and there the problem starts! This new Document revision is not connected to the newest WTPart revision anymore. The user needs to manually disconnect the old revision and add the new revision to it.
I do have a Business Rule written to check this. But that's very late in the change process. So it would be really nice to have some warnings on the WTPart-Document table to see this conflict.
What do you mean with "block"? Cancel?
I was asked to provide a report of the latest version of all drawings at either Released or Prototype Released.
Search allows you to do this because the logic applied is:
- (Filter out anything by state / context that you don't have READ access to)
- Filter out non-latest iteration each Revision (hard-coded in search)
- Use any State criteria; filter out any not any those state(s)
- Depending on preference, return latest of what remains or all (default - latest)
For this data you get B.2 Released as required - essentially search allows you to apply a config spec including state to CAD Doc's (or other)
A.1 In Work
A.2 Prototype Released
B.1 In Work
B.2 Released
C.1 In Work
But, Creating a query builder report to apply the logic in this same sequence turned out to be tricky. By default the qml logic is:
- Filter out non-latest iteration each Revision (direct criteria)
- Find latest using standard sub select on branch id
- Then, apply any State criteria
If you filter out for example In Work, it returns nothing for the data above.
Kudos to tech support engr Jaysel Meledath at PTC who kept with this and figured it out using the appropriate sub select. Seems like it might be helpful to others - leaving it to PTC to make available.
I think there is something wrong the conf branch in the LDAP. Look under the o=configuration, make sure you have the right entries for you search base under .LDAP, .EnterpriseLDAP adapters
I don't think this is possible without a customization. One thing you could do is, remove any transitions defined for change in LC. This will not allow the user to move the state of the object through a change.
Hi Sharath,
If the project is in manual execution, the predecessor wont work.
I also faced the same issue. I searched in PTC regarding this. As per the article below, it doesnt work
Regards,
Logeshwar.J
hello,
i cannot set postpublish.xml file under PUBLISH AND THUMBINAIL CONTROL to publish all assemblies as positioning assemblies.
can you help me?
thanks