Windchill Customization

I am using Windchill PDMLink Release 13.1 and Datecode with CPS 13.1.2.0 and apache activemq 5.18.4Hello,after Upgrading our Windchill Testsystem from Version 12.1.2.9 to 13.1.2.0 the InfoEngineTask com\ptc\windchill\esi\SubscribeQueue.xmlfails with the following error message in Methodserver.log:...[Thread-11] wt.system.out wtadmin - ESI: Administered object "cn=queueConnectionFactory" is not the correct type: expected "ConnectionFactory"The queueConnectionFactory is defined in OpenDJ.The ldif looks like this:dn: cn=queueConnectionFactory,cn=activemq,o=ptcobjectClass: javaContainerobjectClass: topobjectClass: javaObjectobjectClass: javaNamingReferencejavaFactory: org.apache.activemq.jndi.JNDIReferenceFactorycn: queueConnectionFactoryjavaClassName: org.apache.activemq.ActiveMQConnectionFactoryjavaReferenceAddress: #0#brokerURL#tcp://localhost:61616In windchill 12.1. this worked without issue. Why is it not working in Windchill 13 any more? Please help.Best regardsJohannesHere are

 We are querying part information and their associated documents using the same OData request on two different Windchill environments.In our test environment, all documents are returned correctly with the following request:  /Windchill/servlet/odata/ProdMgmt/Parts?$filter=Number eq 'XXXX'& $expand=Versions($filter=State/Value eq 'RELEASED' or State/Value eq 'IMPORTED'; $expand=DescribedBy($expand=DescribedBy($expand=Attachments,Representations)), References($expand=References($expand=Attachments,Representations)), PartDocAssociations($expand=RelatedCADDoc($expand=Attachments,Representations))) However, in our production environment, some documents that are clearly visible in the Windchill UI (under DescribedBy or References) do not appear in the OData API response at all.The document is visible in the UI.We are logged in with an admin account.The same request works fully in the test environment.The issue happens only in production.We would like to ask for guidan

Version: Windchill 13.0 Use Case: I am trying to understand if it possible to ensure that change tasks inherit the number of the change notice to form the prefix of their own unique identifier. For example, if there was a change notice called "12345" which had two change tasks included on it, I would like those change tasks to have numbers of "12345-001" and "12345-002".Description: Can anybody advise if this is possible?

Version: Windchill 13.0   Use Case: Would like to have a change review object template (like we do for change notices) Description: Two part question as I'm starting to play more with change review objects.  These are considered Change objects... so why is it that they can't be templated on the Templates tab like change notices can?  I'd like to add a table to the long description field of the peer review object. Keeping in mind the first question, is there a way to do this without templating the object?  

I have a scenario where I need to traverse to to the Upstream eBOM part using following API -> wt.fc.PersistenceHelper.manager.navigate(mfg_Part,wt.associativity.EquivalenceLink.UPSTREAM_ROLE, wt.associativity.EquivalenceLink.class); Above API returns QueryResult for all iterations of upstream WTPart which had equivalent link between them and mBOM part. However if the user iterates eBOM part but does not update equivalent link manually, I would still need to be able to traverse to previously linked upstream part  Need assistance with finding link to previous Non -Latest eBOM wtPart to fetch further associated documents from it  QueryResult upstreamResult = wt.fc.PersistenceHelper.manager.navigate(parentPart,wt.associativity.EquivalenceLink.UPSTREAM_ROLE, wt.associativity.EquivalenceLink.class);LOGGER.debug(">>>>> upstreamResult : " + upstreamResult.size());while (upstreamResult.hasMoreElements()) {Object partObj = (WTPart) upstreamRe

Version: Windchill 13.0 Use Case: I have managed to find the "com.ptc.windchill.pdmlink.change.server.impl" package on my PC but there is no package that exists in there called "WorkflowProcessHelper". According to the Javadoc that is available via the client, this class exists. It is also called in one of the OOTB workflow robots.Description: I am trying to establish where classes, that I am unable to see on the server but are called in workflow robots, are stored. Can anybody shed light on this? 

I am using Windchill PDMLink Release 12.1 and Datecode with CPS 12.1.2.16Microsoft Edge navigation with IE Compatibility turned on is not working as expected for Edit Wizard.

Version: Windchill 12.1   Use Case: understand why some documents visible in the Windchill UI are not returned in the OData API response and to identify the required configuration to make both environments consistent. Description:   Hello, We are querying part information and associated documents using the same OData request on two different Windchill environments. In our test environment, all documents are returned correctly with the following request: /Windchill/servlet/odata/ProdMgmt/Parts?$filter=Number eq 'XXXX'& $expand=Versions($filter=State/Value eq 'RELEASED' or State/Value eq 'IMPORTED'; $expand=DescribedBy($expand=DescribedBy($expand=Attachments,Representations)), References($expand=References($expand=Attachments,Representations)), PartDocAssociations($expand=RelatedCADDoc($expand=Attachments,Representations)))   However, in the production environment, some documents that are visible in the Windchill UI under DescribedBy or References do not a

Version: Windchill 12.1Organization> Type and Attribute Management > Manage Global enumerationUse Case: Hi everyone Does anyone know the API URL of Manage global enumerations or any other way to access it in API I'm using Workato and need to GET/POST to that list on Windchill Thank youDescription: Hi everyoneDoes anyone know the API URL of Manage global enumerations or any other way to access it in APII'm using Workato and need to GET/POST to that list on WindchillThank you

Hi Team,Is there anyone knows how we can create custom OData rest service in Windchill, please share here if anyone have any solutions. Thanks in Advance.

Version: Windchill 13.0   Use Case: Autoassociate preference is turned on and a custom class that extends DefaultAutoAssociatePartFinderCreator implements AutoAssociatePartFinderCreator runs to select the correct subtype based on Product context. Autoassociate created WTParts don't have the particular subtype defaults. Description: I customized the AutoAssociatePartFinderCreator class to look at the product context a CAD document is being checked into and based on the context selects the appropriate subtype of WTPart to auto associate.  This works as expected and the correct WTPart subtype is associated on check in based on context name.    However, the subtype defaults and cascading attribution I set up for that particular subtype doesn't carry over. Instead, it looks as though the WTPart subtype is created based on the default parent WTPart.    When I create a new part in the context, it follows the WTPart subtype attributes and defaults I set up. 

When I click on the + button, a new row should get created, creating a new row is also working fine with the below code. in the JSP page, I first created a table like below<table id="attachmentTable" style="border-collapse: separate; border-spacing: 12px; font-family: Arial, Helvetica, sans-serif;"> <!-- pickerCallback="BUEPMDocumentPickerCallBack" --> <tbody id="rows"> <tr> <td> <wctags:itemPicker id="buObjectPicker" label="Document Picker" showTypePicker="false" objectType="WCTYPE|wt.epm.EPMDocument,WCTYPE|wt.doc.WTDocument" componentId="buObjectPicker" pickerTitle="Object Picker" displayAttribute="name,number" pickedAttributes="name,number,version,iteration,view" editable="true" pickerCallback="BUEPMDocumentPickerCallBack" pickerTextBoxLength = "40" readOnlyPickerTextBox="true" /> </td> <td style="border-collapse: separate; border-spacing: 12px; fo

Version: Windchill 13.0   Use Case: Using PersistableAdapter to get IBA values of a cascading attribute, the obj.get("attribute_internal_name") for the cascading attributes specifically returns the internal names of the underlying global enumeration item instead of the display name. Description: I have a WTPart subtype that has several cascading attributes.      Is this expected behavior? Is there a way to get the display value of the enumerated value that is used to set up the cascading attribute? PersistableAdapter, when used to get the original value ("Reason for Classification" in my case) returns the enumerated value list internal value instead of the display value.    Setup:  

Version: Windchill 13.0 Use Case: We have a customized Workflow that has a Date as variable (actually, I would prefer a date like LocalDate for the user, but Windchill is still proposing the java.date.Date). I would like that a user can set the date during a User Task.Description: The variable is shown a a text, without any format hint for the user, and the conversion to Timestamp depends on the timezone of the user (if the String is not completely filled) ...How could we provide a date picker as input instead of a input text ? 

Version: Windchill 13.0 Use Case: I am trying to include information within the context of a part instance that tells users where the part instances are allocated. But, I only want to show the parent part instances which the child is allocated to which are at a state of "Released". For example, I have part instance A which is a child of part instance B. Part instance B is at a state of "Released" at revision C. When I create a new revision of part instance B, the first iteration of revision D includes part instance A as a child within its structure. I can then remove part instance A from the structure of part instance B, revision D before setting the state of part instance B, revision D to "Released". If I then navigate to part instance A and look under the "Allocations" tab, part instance A is still said to be allocated to revision D of part instance B, despite part instance A not featuring in the structure of the released iteration of revision D of part instance B.Description: I

Version: Windchill 12.1 Use Case: Scenario is the bulk loading of document links seeing if this can be achieved through WRS or needs some customization.Description: Unable to find any OOTB WRS Services in Document Management Domain to achieve creating DocumentUsageLinks for linking of documents. 

Version: Windchill 13.0   Use Case: Not sure if it's a problem between the keyboard and the seat, but my Windchill JavaDoc isn't showing the wt.vc.wip.WorkInProgressService class. Description: I'm working on some customization and using the wt.vc.wip package. The javadoc (Windchill 13.0.2) isn't showing the WorkInProgressService class page.  There's no scroll bar and it shows a random (but repeatable) few methods in what looks like the middle of a page.    I tried downloading the javadoc from PTC's website too and it behaves the same. Is this a "me" problem?   

I am using Windchill PDMLink Release 12.1 and Datecode with CPS 12.1.1.2How to set value on ComboBox on onchange of the Table builder.tableActionComboBox.addJsAction("onchange", "" );Here are the errors that I facedN/A

Hi, I have to develop a Windchill Rest API that needs to take OAuth 2.0 authentication type. Can we create OAuth accounts in Windchill server?. Thanks in advance.

Version: Windchill 13.0 Use Case: We have a custom REST servlet that works correctly on Windchill 13.0.2 but fails with 404 errors after upgrading to Windchill 13.1.1. The exact same code, deployed identically on both versions, exhibits different behavior in how RESTEasy calculates the PathInfo for incoming requests. Environment:Windchill 13.0.2 (working)Windchill 13.1.1 (not working)Same custom plugin deployed on both versionsApache proxy with AJP connector Configuration:Our REST servlet is configured in web.xml as follows:<servlet> <servlet-name>oslc-connect-servlet</servlet-name> <servlet-class>org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher</servlet-class> <init-param> <param-name>jakarta.ws.rs.Application</param-name> <param-value>com.sodius.oslc.app.wc.server.common.services.OslcConnectApplication</param-value> </init-param> <init-param> <param-name>resteasy.servlet.mappin

Hi,   Is it possible to retrieve the value of Alternate user names of WTUser with API?  

Which licenses are required to use Windchill Information Modeler?Is Windchill Information Modeler included with Windchill PDMLink?

Version: Windchill 12.1 Use Case: Trying to get arbortext to work with WindchillDescription: I'm having an unusual issue. We are starting to use arbortext with our Windchill system (version 8.3 and 12.1.10) and there some odd behaviors. Initially, when I open the application and try to check an object into the server I get this error:The autonumbering feature should be enabled for "WCTYPE|wt.epm.EPMDocument|com.acme.us.DynamicDocument" soft type  It does that for any PRODUCT context or Library. However, if I connect to a PROJECT workspace and checkin the object it works. The weird thing is, it started at 000000032 and increments by -1 every time I create a new object and then it allows me to check in objects into product or library workspaces. Hours later, I attempted again and this time it started at 000000042 and started going down. Here is my OIR for the "Dynamic Document" type  <AttributeValues objType="wt.epm.EPMDocument"> <!-- set the fold

I am making requests to /Windchill/servlet/odata/v4/DynamicDocMgmt/DynamicDocuments and need to interact with potentially thousands of documents. What we have found is the $top parameter doesn't override the server's page size limit. I also tried a header odata.maxpagesize=1000 but that didnt help either. Any ideas on how to adjust the number of results returned from the API?

I have requirement to search object using queryspec which can have number with leading zero(to make it 8 digit length) or without leading zeros.e.g. I am to search object number 66, query should be able to find object 66, 066, 0066 etc. I got regular expression to search( ^0*66$ ) need to know how to use in queryspec.