Just an observation but it seems that renaming a document using workflow or otherwise doesn't count as a modification, i.e. the Last Modified date remains the same. Not an issue as such, it was just something I observed when trying to check how far my workflow had reached when renaming a large batch of documents. FWIW, this is with Laserfiche 11.
Question
Question
Rename doesn't class as a modification?
Replies
The modified date on the parent folder will update every time a document in it is renamed (because under the hood, renaming documents is considered a modification of the parent folder by "moving" a document from its current full path to a new full path).
For starting rule purposes in Workflow, renaming an entry is classified as an "entry changed" event. That was a design choice because we thought classifying it as a move would be too confusing for the user and would require extra conditions to determine when it's a "proper" move versus a name change.
This is consistent with Windows (and I believe Linux/Mac) file system behavior. Renaming (or copying) a file doesn't change the "Date modified" property as the actual contents of the file haven't changed. If you generated checksum hashes of the file before and after the rename operation, they would be the same.