Even for me PTC gave same reason, works as per spec, but they are not able to give us valid technical reason on this. I saw many customer have reported this issue and PTC need to come up with the solution either by fixing the issue or by coming up with new preference setting to make it work.
Below is the enhancement request raised by one more customer. I think we all should go and vote for it.
Greetings,
What I did for my particular application was create a definition variable concatenating the desirable attributes. The code snipped is as follows:
<AttributeValues obType="wt.doc.WTDocument">
<VarDef id="generatedNumber" algorithm=ext.xxxxxxxx.doc.DocNumberGenerator"> (xxxxxx can be your unique identified; name etc.; this generates a sequential unique identifier)
<Attr id="Attribute1'/>
<Attr id="Attribute2'/>
<Attr id="Attribute3'/>
<Arg>-</Arg> (if you want to separate the concatenated attributes with a hyphen)
</VarDef>
<AttrValue id="number">
<VarRef id="generatedNumber"/>
</AttrValue>
{Basically, the above snippet concatenates all your attributes and stores them in the variable 'generatedNumber', then recalls the value and places it in 'number' holder in Windchill.} - [For example; this would result in "Attribute1-Attribute2-Attribute3-001]
Hope this helps!
Cheers
Jas Virdee
Please see attached.
Can't get these preferences or .ini file settings to work so far.
thanks in advance
PREFERENCES
Upload CAD/Dynamic Document and Attachment Filter= (create one for SolidWorks)
Search Path for Automatically Attach Files on Upload=C;\autoattach
EQUIVALENT WGM INI FILE SETTINGS (EXAMPLE GIVEN FOR AUTOCAD)
wgm.autoattach=*.dwg,*.pdf,GENERAL
upload.autoattach.searchpath=C:\autoattach
Has this question been answered? If so then please mark it as such.
Dave,
Did you ever get a template? I'm just starting this process too.
Regards,
David
Hello friends,
I am setting my Distribution as it is working fine for me currently with Windchill 11 but it is not sending inflammations of Alternate parts along with the main part to my PLM connector.
While setting Distribution target information manually from 'Manage Distribution' from Site->Utilities, i am getting this error on clicking the 'Yes'.
Screen shot of an error has been attached with this discussion.
Kindly help me to set up the parameters here so that i can work in it.
Regards,
Sunil Chauhan
Is there a workaround that gives permission to a user to change the filename of a CAD Document, without also allowing change of number?
The permission group MODIFY IDENTITY seems to tie these two things together.
I think separating them into 2 permissions would take a fair bit of coding and changes to the structuring.
Training and company documentation on what is allowed for changes may be the way to go.
I have created a tool to generate an NMLoader XML file from VBA.
ftp://ftp.sonic.net/pub/users/bubblecdn/Create_Document_Upload_XML.xlsm
This spreadsheet assumes that you have 0 or 1 Describe-By document, and 0-2 Reference-By documents to upload. If you need a different configuration, you need to put on your VBA hat, and edit the code. Note that cell labels are used extensively.
Hello,
I am trying to rename a system and running into this problem. The system is a clone of production that will be a test system. Windchill 10.2 M030 CPS-11. The SQL Server and PTC Directory server are running, per the rehost documentation.
I have created the rehost.properties with the guidance of this document:
"How to rename Windchill 10.x using Rehosting Utility 3.0 in Windchill PDMLink"
https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS249543
I have also tried the suggestions in this document:
"Rehost Utility throws error "ANT_HOME is set incorrectly", but ANT_HOME is actually set correctly for Windchill PDMLink 10.1"
https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS121851
(which indicates it covers versions 10.1 thru 11)
The Rehost utility documentation says that it is not necessary to escape the characters anyway. I am using the windchill shell (get the same error when in a windows shell, fwiw).
I have made sure that I have a proper psi_iir file under my windows user profile that points to the installation. Check and doubled checked the values in the rehost.properties file against the site.xconf and db.properties. Tried a ton of different combinations of values. Used the new "test.prop.values.only" and "rehost.log.passwords". I never see any logging under buildlogs or the rehost utility directory. Set, reset, unset "ANT_HOME". Moved the utility to the same drive as the windchill installation. Rebooted. This is all I ever get:
E:\rehostMED-61138-CD-102_M010>rehost.bat conf\rehost.properties
usercase = rename
modules = InfoEngine,Database,Apache
apache.home = E:\PTC\Windchill\HTTPServer
wt.home = E:\PTC\Windchill
wt.usernam =
rehost.properties = E:\rehostMED-61138-CD-102_M010\conf\rehost.properties
setup env
wt_home =E:\PTC\Windchill
JAVA_HOME =E:\PTC\Windchill\Java
ANT_HOME is set incorrectly or ant could not be located. Please set ANT_HOME.
E:\rehostMED-61138-CD-102_M010>
BTW, I don't know why "wt.usernam" is not set. I have populated "target.wc.username". File comments from what I can tell that isn't required for what I am doing here.
I would welcome any suggestions from those who have this working and perhaps know the quirks or any tricks.
Regards,
MLS
Customers create lots of document during CAPA process. They like to add those documents along with the task they receive during CAPA workflow.
Also folder view for those documents added for a specific CAPA.
Please post this here: Windchill
When i share an object to a project, it is hidden. To be able to see the object in the folder, I have to select the folder context "All - including hidden objects". What causes the object to be hidden? Where's the setting?
Thanks
Hi Paul,
It's a strange problem.
The only difference between 'All' view and 'All - including hidden objects' are the following filters.
So, ideally, if you remove these filters from 'All' view. It will solve your problem.
But it's not recommended at all to change the default OOTB view.
Regards,
Kaushik
So we figured out how to remove the Default Change Activity because we create our own from various types and create the Change Name. In 9.1 we had this removed, and if we started the change notice from the object, it would still populate in our new change task on the affected objects. Where do I edit to get the object to populate on the affected objects table in 11.0 after removing the default change task?
Also I noticed the order of the Change Task subject is displayed different. We prefer the Change Name, Type, Number rather than Type, Number, and Name in the subject. Is there a preference setting to switch this back?
Thanks.
Kristie,
The Identity was updated at 10.0 F000.
There are several new features to be aware of -
You can see more in my 2016 conference presentation here:
Best Practices for Supporting Change Management with Flexible Change Association
Thanks for your answer Jeffrey, but we don't use Problem Reports. We are just trying to migrate and work as similar as possible for now from 9.1. We can explore updating workflow templates later, but we are limited on time for go live.
I need to use our own Change Task. It's usually a 1 task per CN, but some processes can included 2 tasks. But I need the changeable to populate on that task? How do I do that?
Also how do I switch the subject name to begin with the Name of the Task rather than the type?
You would define a rule so that your type of Change Notice gets your Change task. This is defined on the Business Rules page in the Site Utilities page. The Change Association Rules table lets you define what Change Tasks should be related to which Change Notices types.
You can see in this example the Sustaining CN type can have Supply Chain Task, CAD Task, Mfg Task and BOM Task related as 1:many. The Prototype CN can have a Simple Task related and is 1:1. By default the CR will propagate data to the default task (and if you use Relationship constraints should only give the the right objects to the task - say WTPart to the BOM Task and EPMDoc to the CAD Task)
For example if you have myChangeNotice with myChangeTask related on a 1:many. By default you will get at least 1 myChangeTask and could create additional.
Do we have to put the Default Change Activity back in for this to work? We also don't use the Change Requests. So no need to propagate from there.
I just added a new rule, to see, but nothing changed? Our workflows are at the Org level, does that matter?
The Default Change Activity preference is deprecated with these new configuration methods, however I am not sure if your customization is effecting this.
Oh - key thing to use these new features is to enable Change Association mode - without this nothing will take effect and you will use legacy behavior.