I am working on a workflow and a key requirement is that if a user in the Audit Task in the Change Notice decides to choose "rework" I need the workflow to re trigger the change task and run through the assignee and reviewer tasks again.
I can't figure out how to get back into the Change Task. Does anyone know how to do this?
We want to prevent a user from approving their own documents. However, this users may be an approver of the same document type created by another user.
Hi,
I want to migrate date from an existing WC8 to WC10.2.
WC8 contains only documents, that I exported via Export/Import Manager.
Result of the data export is a XML file and the document itself.
However, the information in the XML file is insufficient.
The attributes "Modified by", "Last Modified", "Created by", "Created", "Updated by", "Last updated" are not included.
Can someone help me and tell me how to extract that data?
I think best solution to have a SQL query that outputs the number and the attributes mentioned above in a list.
Unfortunately I do not know the correct query.
Only the newest version of the document is necessary.
Thank you in advance.
--- One update ---
I was also advised by PTC to use the QueryBuilder to the get out the necessary data. But I do not know how to use it. Does someone have experience?
All Change Tasks are assigned by Change Admin during creation of the Change Notice/Change Task to the concerned team leader. The team leader distribute/reassigns the Change Tasks to a team member.
Is it possible to display the new Assignee in the Implementation Plan for each task? Is it possible to replace the Original Assignee (team leader) by the new Assignee (team member)? Today, the only way to find the new Assignee is in the Task History.
Hello all,
I'm trying to add some custom attributes to publication structures, but I'm having some difficulties.
I can add the attributes to the pub struc just fine. However, the attributes do not appear in the dialog box when doing Edit Attributes. How do I edit custom attributes on publication structures or add them to the Edit Attribute dialog?
I thought this would be similar to adding and editing attributes for DynamicDocument, but it appears pub strucs have some differences.
Thanks,
-Jeff
Hello all,
Is there a way to modify the search dialog used for adding content to a publication structure? The OOTB fields are name and number. I'd like to add some custom attributes. Is this a layout that can be modified?
Many thanks!
-Jeff
Hello there,
Do you know company who sells this product in Bulgaria?
I am looking for the this and more about this product information translated in Bulgarian:
http://www.ptc.com/File%20Library/PLM/PTC_PLM_Cloud.pdf
Thank you in advance!
Gergana Nikolova
Hi,
Can any one help me in getting "Synchronize" component in javacode.
Thanks in advance
Regards,
Archana
Hi Folks,
We are upgrading our system from Windchill 10.2 M010 to M030 and we would like to exchange experience with users that already done it with the goals to mitigate risks in this process through specification, tests and etc.
Our main concerns are integration, customization and parameters that already done in the system.
It will be pleasure to hear you
It has been a while since I had to rehost my production machine to a test server, but I recently upgraded to 10.2 and would like my test server to reflect the 10.2 production server so that I have a fresh start. I would like to use the Rehost 2.0 tool to help me since I do not want to go through a manual rehost. I do have Solr turned on, some customization and connect to our corporate LDAP. I have an app server and a database server in production and am moving to the same on two virtual servers. Which method would be better and why?
Does anyone know what the difference is between the production and non-production environment in the Windchill 10.2 installer? It's on the same screen as whether you want to configure to send data to PTC.
Thanks,
Mary-Ann
Hi,
I am building a secure remote apache server located in a DMZ, which will be used to allow select external internet based customers/suppliers access to our (up to now) Internal Windchill System - there is hence a high requirement for security on such a system.
In order to protect the Windchill Application, I have installed and configured the mod_security module for apache that strips out various types of known attacks (its a web application firewall) and thus protects the Windchill Application from being attacked.
Unfortunately, the recommended mod_security rule set seems to be rather over-zealous in protecting the application, to the point that several of the Windchill pages do not render properly.
Has anyone configured mod_security to work with their Windchill Apache server, and if so, do they have a ruleset or advice that they would be willing to share?
Thanks in advance
Rgds
Gary
Attached is a .qml report that returns all the outstanding change work items with links to the related change objects.
A good starting point for change object related reports. Includes the following object types
Implements both of the following very handy references
https://www.ptc.com/appserver/cs/view/solution.jsp?n=CS153902&source=tssearch
https://www.ptc.com/appserver/cs/view/solution.jsp?n=CS63595
Regards
Darren
Hello everyone,
I am wondering if any one of you have benchmarked Windchill against Teamcenter and/or PLM360 from Autodesk.
I know that there are many aspects to consider and what can be good for one company may not be suitable for another one. However, as I have worked with Windchill for over 8 years now, I would like to stay with this software in my new company and therefore try to ensure we select Windchill.
We will soon consider those 3 solutions. So if you have (not too old) information about those software and why Windchill is better this will help my case ;)
So far we have Inventor with Vault
Thanks a lot
Best regards
Are you new to Windchill Visualization? Would you like WVS Jobs to be processed more efficiently or to just have more control over how they are processed? This blog will cover the fundamental concepts behind WVS Job Processing and how WVS utilizes Windchill Processing Queues to achieve this. In addition, I have included links to key Technical Support knowledge base articles for your reference.
The primary TS knowledge article CS149619 - How Windchill Visualization Services uses Windchill Queues for processing WVS Jobs.
Since Windchill 10.0 there are three types of WVS Jobs:
All three WVS Job types are managed and processed using Windchill Processing Queues but WVS utilises these in a unique way.
At start-up, for Publish Jobs, WVS creates three Prioritized ‘Waiting Queues for High, Medium and Low priority jobs, and a single Numbered ‘Processing’ Queue where the work is actually done. These together are referred to as the default (unnamed) WVS Queue Set. WVS also creates similar Queue Sets for processing Clash and Print Jobs but including the respective queue set names, CLASH and PRINT, i.e.:
Queue Set Name | ‘default’ | CLASH | |
Prioritized ‘Waiting’ Queues | PublisherQueueH PublisherQueueM PublisherQueueL | PublisherQueueCLASHH PublisherQueueCLASHM PublisherQueueCLASHL | PublisherQueuePRINTH PublisherQueuePRINTM PublisherQueuePRINTL |
Numbered ‘Processing’ Queues | PublisherQueue1 | PublisherQueueCLASH1 | PublisherQueuePRINT1 |
An Administrator can optionally then create additional Numbered ‘Processing’ Queues to which WVS will attempt to distribute the entries from the Prioritized ‘Waiting’ Queues equally, thereby spreading the publishing load across multiple queues in parallel. Although, if publishing large numbers of small and quick publish jobs (simple parts), only the lower queue numbers will be loaded (Refer to TS knowledge article CS42096).
WVS processes each logical WVS Job using a combination of two physical Windchill Processing Queue Entries:
Note: Clash and Print Jobs do not currently support all the capabilities that are supported for Publish Jobs; for example, Clash and Print Jobs cannot be processed in Dedicated Publisher Queue Set or using Dedicated Workers (see below).
The following shows a conceptual diagram of the traditional WVS Publisher Queue mechanism in the context of the overall WVS architecture:
WVS adds queue entries (that execute the queueJob method) for each newly submitted Publish Job to the relevant Prioritized ‘Waiting’ Queue, based on the type of the content to be processed and source of the request. The mapped priorities for the type and source combinations can be configured using property settings in the wvs.properties file (refer to TS knowledge base article CS28472).
Note: Similar settings are available for prioritizing Print and Clash Jobs (refer to the wvs.properties.xconf file alongside wvs.properties).
All Windchill processing queues are FIFO (First in First Out) queues. Queue Entries initially have a READY state when they are created, EXECUTING state when they are being processed and COMPLETED state once processing completed successfully. Since Windchill 10.0, the NONEVENTFAILED state is used when processing completed but unsuccessfully; the Windchill Queue Entry states COMPLETED and NONEVENTFAILED now map to the WVS Job completion states JOB SUCCESSFUL and JOB FAILED respectively. Refer to TS knowledge article CS37569 for details of the different Windchill Queue Entry states and how to manage the related queue entries.
Queue Entries in the WVS Prioritized ‘Waiting’ Queues are processed one-at-a-time, so there should only ever be one EXECUTING entry in each queue and the rest waiting in the READY state. All entries in the High priority queue are processed before those in the Medium and all those in the Medium priority queue before those in the Low. An EXECUTING ‘Waiting’ Queue Entry (queueJob) is simply looking for an idle Numbered ‘Processing’ Queue that has no READY or EXECUTING entries. When it finds one, it creates a new ‘Processing’ Queue Entry (doJob) within it, initially in a READY state. The related ‘Waiting’ Queue Entry is then COMPLETED and is automatically removed by the Windchill Queue Service.
Note: Out-of-the-box, this process is repeated every 5 seconds for all ‘Waiting’ Queues in every defined WVS Queue Set, based on the value of the publish.publishqueuepollinterval property in wvs.properties.
Queue Entries in the WVS Numbered ‘Processing’ Queues are also processed one-at-a-time, so there should only ever be one EXECUTING entry in each queue and the rest already processed in the COMPLETED state. An EXECUTING Queue Entry (that executes the doJob method) will identify and execute the Document Publisher (for WTDocuments) or the respective CAD Publisher (for EPMDocuments) configured using the Authoring Application specific CadConvert properties in wvs.properties, e.g. for Creo Parametric, with an internal Authoring Application of PROE, the publisher class defined by the publish.cadconvert.PROE property is used. It is the Publisher that controls the execution of the publishing process for its respective CAD application data type.
Upon successful completion of publishing, the ‘Processing’ Queue Entry state is set to COMPLETED and depending on the Numbered ‘Processing’ Queue name and the value of the respective wt.queue.removeCompleted.<QueueName> property in wt.properties, will automatically keep or remove it (refer to TS knowledge base article CS32811). After publishing is complete, the Publish Job Details log is added to a BLOB data column in the COMPLETED queue entry, so removing the queue entry also removes the logging. At Windchill 10.0 the new state NONEVENTFAILED was added so that completed unsuccessful Publish Jobs are not automatically deleted by this mechanism.
Since Windchill 9.1 M010, WVS has also supported the concept of Dedicated Publisher Queue Sets. The purpose of this capability is to extend the ability to manage and control specific categories of Publish Jobs using a completely separate and dedicated publisher queue set. For example, to separate the publishing of Parts, Assemblies and Drawings, or to separate publishing of different CAD authoring application content, so that all the Numbered ‘Processing’ Queues in each dedicated publisher queue set can be dedicated to optimally loading the CAD workers for the same application. These Dedicated Publisher Queue Sets can also be combined with Dedicated Worker Sets for even greater control over which workers should process Publish Jobs from specific Publisher Queue Sets.
For a detailed example configuration, including sample filter code, refer to TS knowledge article CS132318 - Windchill PDMLink 10.0: An example of how to configure WVS Dedicated Publisher Queues and/or Workers to process Publish Jobs based on custom criteria.
I hope you find the information in my blog post interesting and of use. As always, your comments and feedback are very welcome.
Hi All,
How do I reset these!?!
I created custom \codebase\wtcore\images\bblks\l_ptc_splash.gif and \codebase\netmarkets\images\22A_windchill_logo_x20.png files and replaced the OOTB ones.
Now, I've copied the OOTB ones back and they are not showing, e.g. my custom ones show inthe web browser even though the files are changed.
I have; 1. deleted the \instances 2. restarted everything 3. Cleared webbrowser cache
It must be caching these somewhere I'm missing. Any idea?
Thanks!
-V
A user deleted the org admin group
Now if we go to the organization>administrators tab and try to add users we get the message
Unable to update the delete group "Org Administrators"
How do I recreate this group??
WINRU will help to resolve this.(ie principal validator check)
While developing workflows we are running into an issue where the workflow fails to clear a step. The step shows executed, but when we look into the actual step we find a null-pointer error. In Checking the method server we find the following error:
2015-06-24 09:15:25,386 INFO [ajp-bio-8010-exec-4] wt.system.err Tech - wt.util.WTRuntimeException: Cannot restore "wt.workflow.robots.WfExpressionRobot.103962692" because it no longer exists. Nested exception is:
2015-06-24 09:15:25,386 INFO [ajp-bio-8010-exec-4] wt.system.err Tech - (wt.fc.fcResource/32) wt.fc.ObjectNoLongerExistsException: Cannot restore "wt.workflow.robots.WfExpressionRobot.103962692" because it no longer exists.
We cannot figure out why it would be throwing this error, we have checked all the code in the workflow and it is working. We can get it to run on our development server but when we move to production the workflow fails. The expression robots clearly exist in the workflow, could this be a server communication issue?