cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Deleting PDMLink Terminated or Executed Workflows

Newbie

Deleting PDMLink Terminated or Executed Workflows

We have ~ 200,000 "Executed" workflows in our PDMLink system. Does anyone
have any thoughts on deleting or not deleting Executed workflows?

David Graham
CAx/PDM Administrator


Emhart Glass Manufacturing Inc.
123 Great Pond Drive | PO Box 220 | Windsor, CT 06095-0220 | USA
Telephone +1 (860) 298 7377 | Telefax +1 (860) 298 7397
Mobile +1 (203) 376-3144 |
4 REPLIES 4

Deleting PDMLink Terminated or Executed Workflows

RE: Deleting PDMLink Terminated or Executed Workflows

In Reply to Dhananjay Sandbhor:

https://www.ptc.com/appserver/cs/view/solution.jsp?n=132792

hth
Regards,
Dhananjay Sandbhor

I'm curious about this as well. The link provided below just informs (and warns) about how to delete processes not answering the original question of "should we".

Joe

Deleting PDMLink Terminated or Executed Workflows

as best practice you should only delete wf proceses which does not have PBO
associated with them.
Regards,
Dhananjay Sandbhor



RE: Deleting PDMLink Terminated or Executed Workflows

Most workflows have a Primary Business Object (PBO) linked to them. It is best practice not to delete, but there are cases where this causes huge performance issues when they are:

  • terminated
  • completed
  • executed
  • hung
  • legacy running

There are cases where the lifecycle spawns multiple task or workflows. So, its the process that has to be deleted and a more efficient Lifecycle and its WF process has to be implemented. So what to do...

Deleting a terminated, completed orexecuteddoes not change the history of the PBO. I've been at some customers where we have to delete the processes because it is taking up the resources of Windchill app due to queries in large number of process:

Best practice:

  • create a mirrored test server
    • list a fewPBO's that have these types of processes tied to it. It may have both terminated and running.
    • change the state of running hung process to terminate
    • change legacy running legacy processes to terminate
    • search for process that are terminated, and delete(you may have to do this in the back end using the wt.queue.QueueManager, if the front end takes too long showing all the processes in a browser page)
    • search for process that are executed, and delete (you may have to do this in the back end using the wt.queue.QueueManager, if the front end takes too long showing all the processes in a browser page)
    • search for processes that are completed, and delete (you may have to do this in the back end using the wt.queue.QueueManager, if the front end takes too long showing all the processes in a browser page)
    • Create new objects to see if the WF service is has been revived or has a better performance or is frozen in thequeue manager
    • test the PBO's to see if the running at still operational, and continue the processin the test system
  • If all is good, proceed to do the same on production after a complete backup.

Good Luck,

Patrick

Announcements
LiveWorx Call For Papers Happening Now!