Skip to main content

PLM

Optimize your product development process with Windchill, our PLM software that offers comprehensive capabilities to help manufacturers with all phases of the product development lifecycle.

10000+ Topics
M
MS_109999873-Newcomer
 Windchill
When running a workflow, the message "Not submitted. Cannot perform 'Promote'" is displayed and the

Translated by the Community Moderation using Google Translate -----------------------------------------------------------------------------------------------   Promotion request: Promotion request for reputation management Lifecycle name:HYOUKA_PR_LC Open - Under 1st evaluation - Under 2nd evaluation - Approved Workflow name:HYOKA_WF   With the settings, create a lifecycle and workflow, and use the document created in the product. Start the workflow process from "New Promotion Request". First, the first task will be created, so select the created task and check "Promote". When you click the "Task Complete" button, an error message like the one attached appears and the task is terminated. Unable to complete.

6141
A
1
1102506012-Amethyst
 Windchill
C
CT_101095681-Visitor
 Windchill
J
jrozanc9-Granite
 Windchill
V
VVII10-Marble
 Windchill
Operating when accidentally created manufacturing view part/assembly

Hi, Asking for references how have you operated in the following situation. Version I use is 12.0.2   In BOM-transformer, MPMlink: If parts is created by mistake to manufacturing view that should be in design. (Accidentally click duplicate with propagating, when I should just allocate the design as design to manufacturing side)    What is the back up plan? Is it possible to just remove the manufacturing views of those parts if you detect it immediately? Will the connection link between design - manufacturing view even allow it (admin rights).    This is important because if manufacturing view have been created, it will always use it instead of design, and this is not what I want by accidentally created components.   Thanks in Advance.    

25402
V
A
AR_992045614-Alexandrite
 Windchill
How can I obtain the JSP value as a table in Info-Engine XML?

we write this xml in info engine.<%@page language="java"%><%@taglib uri="http://www.ptc.com/infoengine/taglib/core" prefix="ie"%><ie:webject name="Query-Objects" type="OBJ"><ie:param name="INSTANCE" data="$(@FORM[]supporting-adapter[*])" delim="!" valueSeparator="!" default="<%=com.infoengine.au.NamingService.getVMName()%>"/><ie:param name="ATTRIBUTE" data="Customer1"/><ie:param name="ATTRIBUTE" data="Emmision"/><ie:param name="ATTRIBUTE" data="Engine"/><ie:param name="ATTRIBUTE" data="healthStatus"/><ie:param name="TYPE" data="wt.projmgmt.admin.Project2"/><ie:param name="WHERE" data="()"/></ie:webject>   we write jsp as <%@page language="java"%><%@taglib uri="http://www.ptc.com/infoengine/taglib/core" prefix="ie"%><html><body><ie:task uri="ext/NEWEXAMPLE.xml" processor="com.windchill.wcdev.Windchill"/><ie:webject name="Display-Table" type="DSP"><ie:param n

9112
HelesicPetr
22-Sapphire II
P
PN_507669210-Marble
 Windchill Customization
IBAs, ModeledAttributesDelegate and Workspace limitations

Hello, in all the years of Windchill projects there is one problem-area that's always coming up:The (Creo) workspace and it's (annoying) limitations. Quite often there is a triple set of related objects: CAD Model, CAD drawing and a related item. (yes, that's somewhat simplified 😉 )Model, drawing and item have usually a different number - which results in the "problem" that in a table view it's hard to group those triple sets or pairs in the table view.A solution we sometimes use is to define an IBA on the EPM documents named "partno"  as well as on the WTParts. that attribute always contains the value of WTPart.number.result: in the workspace it's possible to sort by column "partno" and the objects are grouped together. my customers like that. But... while this is "ok" for smaller installations it's creating a lot of "duplicate" data in the database and especially in the StringValue table which is quite often already huge even without that attribute. Problems

19992
P
V
VVII10-Marble
 Windchill
WT parts (part numbers) with Manufacturing view and design view

Hi, I'm trying to think solution to retrieve all design views that have manufacturing view, which have equivalent part but the link is out out of date. (Example: Manufacturing view A.1 is done from Design (A.1). Those part have valid equivalent link. Design view gets revised and is now B.1 --> equivalent link exists between part numbers but is not pointing to the latest. I think this article can be utilized: https://www.ptc.com/en/support/article/CS72503 This query retrieves latest version of views when searching by part number.First step where I need help. I would like to add check if per part number exists both design view and manufacturing view, then and then only it would return them. By this I could find all latest manufacturing views that have been made from design view.   After that I was wondering the following; I could add to the tables and joins either manufacturing equivalence link or wt.vc.Iterated to get the actual RoleA - RoleB i

11371
V
D
17-Peridot
Dobi17-Peridot
 Windchill
Auto numbering for both CAD centric and Part centric approach

I'm playing around with auto-numbering in my dev environment.For most things in production we'll do a File/New in CAD and then auto-associate/create new WTPart on checkin. That works just fine. For some cases, we'll create the WTPart first (or have a manufacturing view).  In auto-numbering with the part-centric approach, if I create a new WTPart and check the "Create CAD" box both end up having the same Number value based on my sequence and naming. So that works fine.  Keeping the same rules in place, File/New (in NX) creates the correct next in sequence number to replace the file name on save (from Help Center). On upload or check-in though, the auto-associate to create a new WTPart generates the new in sequence value for the Number. The name is fine (same as CAD). This appears to be OOTB expected behavior (Help Center ) Is there a way to turn off auto-numbering for WTParts when the CAD is creating it via auto-associate (CAD centric approach) an

10351
D
17-Peridot
Y
YJ_100687548-Gravel
 Windchill
A
Amirtharaj_K17-Peridot
 Windchill
B
BJ_107532241-Visitor
 Windchill
S
shin1h13-Aquamarine
 Windchill Customization
Authentication methods when calling REST API with workflow robots

Hi experts, We are developing an add-on using some REST APIs(such as NewDownstreamBranch) to automate some UI operations of the BOM Transformer with workflow robot processing. Currently, when calling the REST API, we need to authenticate the workflow initiator, but we face the challenge of not having a way to obtain the user's password information. Is there a good way to obtain the password and pass it to the REST API? Would there be a way to obtain the password if it's an unsupported API? Alternatively, is there another authentication method that does not involve directly passing the password to REST API? If there is no viable method, we are considering requiring users to enter their password for this process.

11422
A
D
DV_109221581-Visitor
 Windchill
A
AJ_TROGLIO14-Alexandrite
 Windchill
How to add part specific information at the upper level assembly

We are performing use case testing as part of our upgrade to Windchill 12.   We have a group of PC hardware and software engineers who need to perform the following activities.   We have a WTpart BOM structured like the following;BLD-PROG-123      Qty 1 ea, 232-281-2-16000 FLASH DRIVE      Qty 2 ea, 128-1393-2 FLASH DRIVE LABEL      Qty 1, ea, 218-229-2 PROGRAM KEY, RED      Qty 1, ea, 112-181-2 SNAP RING This structure represents the parts to 'use' to program the flash drives.  Under each part there are programming and other 'work instructions' that are performed in the context of the upper level assembly build.  What the shop sees in the end is; BLD-PROG-123      Qty 1 ea, 232-281-2-16000 FLASH DRIVE                      PROGRAM FLASH DRIVE WITH 123XYZ FIRMWARE      Qty 2 ea, 128-1393-2 FLASH DRIV

9241
A
R
rleir17-Peridot
 Windchill Customization
S
Shashwath12-Amethyst
 Windchill
BGMS Restarting Continuesly & Publishing Queue are Stuck.

I'm using Windchill 11.1 M020 CPS 30.Any Suggestions / Solution for below Issue Case:CS54402 (2nd Point) One or more transactions execute a large volume of SQL retrieving small numbers of rows each time, but cumulatively results in a large amount of Method Server memory being usedA log file will show a series, usually dozens of 'StatementCache' lines like the one below for the SocketThread12 thread.The thread name will vary but will usually be named SocketThread##, RMI TCP Connection(###) or SimpleTaskDispatcher###.  'hits' in the line below is a rough estimate of the number of SQL statements sent to the database for processing'RMI TCP Connection': generally a user UI actionSimpleTaskDispatcher: often an EPM related operationSocketThread: usually an InfoEngine taskExample of output: [SocketThread12] wt.pom.statementCache - StatementCache: wt.util.Cache%618734817 [size=50, count=48, hits=239727, misses=84, aged=0]If there an OutOfMemoryError generated

11431
HelesicPetr
22-Sapphire II
G
Gucio16-Pearl
 Windchill
D
DKWc15-Moonstone
 Windchill
avillanueva
23-Emerald I
avillanueva23-Emerald I
 Windchill
U
uvex_windchill8-Gravel
 Windchill
M
MarianaSousa14-Alexandrite
 Windchill
1
1102506012-Amethyst
 Windchill
R
rherscher-21-Visitor
 Windchill
L
LR_99796041-Visitor
 Windchill

Badge winners

  • First Topic
    Lukasiakhas earned the badge First Topic
  • First Reply
    KCorriganhas earned the badge First Reply
  • First Reply
    YA_12845300has earned the badge First Reply
  • First Accepted Solution
    gatlashas earned the badge First Accepted Solution
  • First Topic
    gatlashas earned the badge First Topic
Show all badges
Terms & ConditionsAccessibility statement