M-Files is a 2025 Gartner Peer Insights Customers' Choice for Document Management
️️➡️Download the report!

Options
  • State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 13 subscribers
  • Views 1412 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Class change with Property Calculator does not trigger Workflow

e-dox-AJ

Hi, I have found a strange behavior when I change the class with Property Calculator and wanted to ask if anyone has the same problem.

I have set up an external source for one of our customers. It comes up with a PDF with xml. In the xml is a documenttype. I save this type in a value list and with Property Calculator I customize the class with this abbreviation. The assigned class (e.g. Invoice) has a forced workflow, but after the class change with Property Calculator there is no workflow.

If I change the class manually in the metadata card, it works fine and the workflow is there and in the first state.

Does anyone have the same problem and a solution for it?

Parents
  • 0

    The "forced workflow" is an indication that the client should force the workflow; it's not something forced by the server.  If you're setting the class via the API (which is what PC does) then you would also need to set the workflow (and possibly state) at the same time.

Reply
  • 0

    The "forced workflow" is an indication that the client should force the workflow; it's not something forced by the server.  If you're setting the class via the API (which is what PC does) then you would also need to set the workflow (and possibly state) at the same time.

Children
M-Files
M-Files Support


© 2025 M-Files, All Rights Reserved.