Hi everyone,
I have a question regarding workflow behavior when changing the class of a document in M-Files.
When I configure a workflow to be restricted to a specific class (e.g., "Class X only"), I would expect that changing the document's class away from that class would either detach the workflow or prevent the class change. However, I've noticed two unexpected behaviors:
1. The workflow "follows" the document even after a class change, meaning the document retains the workflow it was assigned under the original class.
2. Even more critically, the carried-over workflow seems to override and overwrite the workflow configuration that is defined for the new target class.
This raises a broader question for me:
What is the recommended best practice for handling class changes on documents that have an active workflow and for documents that have no workflow assigned at all?
Is this intended behavior? Are there any guards or configuration options to prevent a workflow from being unintentionally carried over during a class change?
Thanks in advance for any insights!
Best regards,
Yves
