When a user deletes a document that was created off of a qForm-based solution, DBXL will still contain data related to the document’s assignment history. This is stored in the system document type called QdEmailFlow. The visual effect of this is easily seen in the Catalog view taskpane: ‘zombie’ users are present even though they do not have any documents assigned to them. There is an advanced customer scenario that depends on deletion: pruning and archiving. This occurs if databases begin performing poorly when there is too much unneeded historical data.
To address these scenarios, DBXL users can turn to Document Deployer to perform the necessary cleanup. After deleting the documents you wish to remove, follow these steps.
1. Copy the Scenario file called CleanupFlow.xml into Document Deployer’s scenario folder. (Click Download, above, to obtain this file.)
2. Launch Document Deployer UI and click on the Custom tab.
3. Select CleanupFlow.xml from the Scenario Path dropdown and click Load.
4. Change the DBXLRoot and DBXLUrl variables to reflect the values for your DBXL instance.
5. Click Run.
You will see a message like this in the Log window:
2008-08-12 05:07:03 Executing action ListFlowDocuments...
2008-08-12 05:07:25 Executing action DeleteFlowDocuments...
2008-08-12 05:07:26 Removing document with id 1...
2008-08-12 05:07:26 Removing document with id 2...
Etc.
2008-08-12 05:07:42 Executing action OutputResult...
2008-08-12 05:07:42 Removed <x> flow documents
When the operation is complete you will see a confirmation message, letting you know that the execution was successful!