PTC Community: Message List

Couple of thoughts.

1. Make sure that these documents are "Reference Document" or a created sub type of them - such that the Revision of the Document which is retrieved with a WTPart is the latest Rev (Reference relationship to WTPart floats to latest - RELEASED state or as configured).

2. Can load a whole bunch of these relationships from spreadsheet and may be worth doing so- once, but it's a major maintenance headache in general, so may want to consider if all these links are helpful.

3. Might want to associate all that apply only to the End Item for each Product - which is what we did at previous company. It doesn't directly give the list of documents for each component / sub assembly / assembly but was good enough - from the End Item, get a relationship report and then get the list of all applicable reference documents. Can supplement with relationships where needed to individual Parts.

4. Create query builder Reports such that people can get the reference documents and output to Excel quickly and easily (same as from the WTPart page but saves a few clicks.

I have a system file in PTC Windchill Quality Systems 11 with several large fault trees. I'd like print them to large landscape sheets and show as much of the trees as I can on individual sheets while minimizing the number of transfer gates needed...to facilitate reviewing. It becomes extremely cumbersome when the reviewer has to jump back and forth through a several hundred page document (with many pages containing only 2 or 3 gates) in order to follow the logic paths in a given branch.

This is difficult because 1) the software won't let me print landscape, 2) the software automatically creates transfer gates when I print greatly increasing the number of pages (I haven't found a way to control this), and 3) I haven't found a way to choose a larger size sheet or to scale the tree size down to make it (or large portions of it) fit on one sheet.

Has anyone encountered this same problem? If anyone has some pointers on printing off large trees in a reasonably user friendly manner I'd greatly appreciate your input.

Thanks.

It doesn't seem like anyone is concerned with this and that I am overly-concerned.

This works well for the primary object. Is there a way to adjust the script so that it would also check the 'descendants' of the primary object? For instance, we are starting workflows on maps which have several maprefs (english doc, french doc & metadata doc). At any given time one of the maprefs could be checked out, but not the map (primary object). Is it possible to have the script stop the workflow task if one of the maprefs is checked out?

Is there any way to include descendants with primaryBusinessObjects? if(wt.vc.wip.WorkInProgressHelper.isCheckedOut((wt.vc.wip.Workable) primaryBusinessObject)) { throw new java.lang.Exception("The workflow document is checked out, Please check it in to complete this task!"); }

The error in Conflict management reads as follows

Attribute values cannot be added ,removed or changed

Hello,

Question to PTC : Have you any plan to make WPA reviewed by IPC ?

As far as I know, WPA is not listed in previous IPC reports.

(link to IPC document : https://ipc.kavi.com/kws/public/download/6079/Review process for IPC 1752A solution providers.docx)

Regards,

Pierre.

Hello,

According to the European court of justice decision, the threshold should not be considered at the product level but at the article (component) level. As product manufacturers, we must communicate where the concerned substances are located in our products and what are the instructions for safe use.

-> How can we record these new sets of data at the parts level (data received from our suppliers) ?

-> How can we report this set of data at our products level (in BOM reports) ?

Regards,

Pierre.

Is there a workaround??? The article hasn't been updated in over 9 months.

In the release 1.2 there are synchronization capabilities that the users do not need to be created manually

I'm not aware of any tools of that. But add the column Context to the preference table. Expand everything and search for User. Then you will find the settings the user did by his own and set those to default again.

I just pinged tech support. There is no workaround and the SPR is tentatively planned to be addressed in Windchill 11.0 M030.

Lori,

Yes everything is working now...the mistake i was making was using the parent WTpart and not the name of the sub-type. Once I inserted the sub-type name in the mapping field it worked perfectly.

We have implemented the SSO in our Test environment using Shibboleth and ADFS. Everything works well, except the following:

1. SSO will only works for IE 11 and Chrome. It will not work for Firefox.

2. Command-line Bulk Upload command will no longer working. (including any customization of bulk upload in WC UI that use the bulk loading command in the background).

3. Running Query report with Excel link will fail.

3. Creo Parameter connecting to your Windchill will also not work with SSO.

The workaround solution we have is to write a SSO Turn On and Turn Off script at Apache level, but it is not perfect! (and it defect the original purpose).

If you can live with the above, you can use the SSO.

Sincerely,

Thomas Chao

Thank you so much for the help

Hi,

We are in process to upgrade. I installed windchill 11.0 M010. Put all customization files(class files, custom xconf etc) through build. When i am trying to propagate the changes it throws following error

com.ptc.windchill.structconf.xconf.XconfException: Error parsing file:/F:/ptc/Windchill_11.0/Windchill/codebase/wt.properties.xconf, line 218 (starting at rootdoc file:/F:/ptc/Windchill_11.0/Windchill/declarations.xconf)

at com.ptc.windchill.structconf.xconf.XconfParser.parse(XconfParser.java:241)

at com.ptc.windchill.structconf.xconf.XconfParser.parse(XconfParser.java:203)

at com.ptc.windchill.structconf.xconf.XconfUtil.processDeclarationXconfFiles(XconfUtil.java:141)

at com.ptc.windchill.structconf.xconf.XconfUtil.processAllXconfFiles(XconfUtil.java:192)

at com.ptc.windchill.structconf.RebuildAnalyzer.scanXconfsForDependencies(RebuildAnalyzer.java:360)

at com.ptc.windchill.structconf.RebuildAnalyzer.outOfDate(RebuildAnalyzer.java:525)

at com.ptc.windchill.structconf.RebuildAnalyzer.shouldPropagate(RebuildAnalyzer.java:781)

at com.ptc.windchill.structconf.StructConfManager.propagate(StructConfManager.java:194)

at com.ptc.windchill.structconf.Propagate.execute(Propagate.java:57)

at com.ptc.windchill.structconf.StructConfManagerCommand.execute(StructConfManagerCommand.java:102)

at com.ptc.windchill.structconf.StructConfManager.execute(StructConfManager.java:259)

at com.ptc.windchill.structconf.StructConfManager.execute(StructConfManager.java:273)

at com.ptc.windchill.structconf.StructConfManager.main(StructConfManager.java:820)

Caused by: org.xml.sax.SAXParseException; systemId: file:/F:/ptc/Windchill_11.0/Windchill/codebase/wt.properties.xconf; lineNumber: 218; columnNumber: 296; Attribute "unlessAssembly" must be declared for element type "Property".

at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)

at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)

at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)

at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValid

ate(Unknown Source)

at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)

at org.apache.xerces.impl.dtd.XMLDTDValidator.emptyElement(Unknown Source)

at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)

at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)

at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)

at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)

at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)

at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)

at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)

at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)

at com.ptc.windchill.structconf.xconf.XconfParser.parse_(XconfParser.java:573)

at com.ptc.windchill.structconf.xconf.XconfParser.recurseIntoHrefFor(XconfParser.java:524)

at com.ptc.windchill.structconf.xconf.XconfParser.access$1400(XconfParser.java:41)

at com.ptc.windchill.structconf.xconf.XconfParser$Handler.startElement(XconfParser.java:890)

at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)

at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)