Hi Zoe,
Well, first of all, K2.net 2003 was never meant to store documents - that would be the function of Sharepoint. I would change the process design to only store a URL or filepath to the document and NOT the document itself.
Secondly, I would recommend taking off the 'Keep audit trail' checkmark on the process level data- or xml field storing the document.
Have you had a look at the Archiving component which allows you to move completed process instances within a specific date range out of the K2Log database and into another archiving database?
Regards,
Ockert
+1Hi,
I'm having K2 process using sharepoint document event.
We would have the document file saved as the process instanae data.
This might be the reason why the ProcessInstanceAuditData in K2Log growing so rapidly.
Is there any methodology to housekeep the log databse?
Many thanks.
Zoe
I'm having K2 process using sharepoint document event.
We would have the document file saved as the process instanae data.
This might be the reason why the ProcessInstanceAuditData in K2Log growing so rapidly.
Is there any methodology to housekeep the log databse?
Many thanks.
Zoe
+1Dear Ockert,
Coz I'm using the Sharepoint 2003 Document event.
When I investigate the code behind (actually, I'm using GUI mode and provide a Virtual Server URL), the server would retrieve the file and store in the K2.ProcessInstance.DataFields("MyFile").
Is it the design of K2? by storing the whole file binary in the K2.ProcessInstance.DataFields("MyFile")?
Kind Regards,
Zoe
Coz I'm using the Sharepoint 2003 Document event.
When I investigate the code behind (actually, I'm using GUI mode and provide a Virtual Server URL), the server would retrieve the file and store in the K2.ProcessInstance.DataFields("MyFile").
Is it the design of K2? by storing the whole file binary in the K2.ProcessInstance.DataFields("MyFile")?
Kind Regards,
Zoe
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.