What you see is the expected behavior.  Deleting a process, any process, simply removes that process from the K2 database.  K2 does not reach out to any external systems upon process instance delete.

---

thanks for the reply.  Currently we have a web service method that handles the deletion of a process.  in addition to using the K2Mng to delete the procInst it also does a couple of other things (adds a comment to db table, marks the procInst as 'deleted' in an external reporting table, etc).  We are just thinking of adding functionality to look up all the .xml worklist documents that may be related to it and then going out and deleting them from the SharePoint doc library.  I was just curious if anybody has any comments or ideas on how best to achieve this?  Thanks.

---

U can find orphaned .xml documents under Shared Documents folder in Document Workspace. These xml files for a specific deleted processes can be identified with process instance no. File name of this xml document contains process instance no. e.g SupervisorApproval_12133_22.xml i.e., event name_process Instance no_some no.xml

 

HTH,

Siva

 

---