Class change with Property Calculator does not trigger Workflow

Question

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?

e-dox-AJ · Accepted Answer

Thank you Craig Hawker and Juuso Suominen . I will try this. 
 
 It works, thank you again.

Juuso Suominen · Answer

Additionally, if you want add Property Calculator rules to change workflow and state, you also have to change used event handler: Default event handler is triggered too late to do any changes for workflows, but BeforeCheckInChanges let you do that.

Craig Hawker · Answer

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.

Class change with Property Calculator does not trigger Workflow

Top Replies