Overview
Symptom: Using Compliance Kit's PDF Processor module, a document is subject to a PDF Rendition instruction, typically triggered by a workflow state change.
From user perspective, PDF processor seems to be triggered duly, as:
- The document gets checked out for several seconds by M-Files Server, as for a typical PDF rendering operation
- Upon document check-in, the value of the property 'PDF Rendition Status' is 'Completed'
However, the PDF file has remained unchanged - there has been no effective PDF treatment.
Solution
The document is probably subject to an immediate automatic workflow state transition (typically: 'Change state after 0 days') right after the PDF rendition is triggered. This causes a clash with PDF treatment, without triggering an error in M-Files.
Adjust the document workflow, either by removing this automatic workflow state transition or by changing the trigger to a property-based condition, for example 'PDF Rendition status' is 'Completed', to ensure that the PDF Rendition is duly completed before the document has its workflow state changed.
