Frequently Asked Questions
Frequently Asked Questions: M-Files
Assignment Assigned To Values Removed From Workflow State Transition Fix
Posted by Devansh Parekh (M-Files) on 03 January 2019 11:21 PM
 
Steps to reproduce:
1. Creation of separate assignments as part of one workflow step (E.g. In Progress)
2. Assigning separate assignments to one specific responsible user as part of the workflow step
3. Transition into another workflow step (E.g. Ready for Signature)
 
Actual Result:
The assignments are not assigned to the user any more. The "Assigned to" property for these assignments was reset
 
Expected Result:
The assignments that were assigned to to the responsible user are still assigned to the defined user after the transition to the new workflow step.
 
Tracker Item:
We have an existing improvement "ID 130092 - Do not clear "Assigned to" from separate assignments."
 
Workaround:
you can prevent M-Files from clearing out the "Assigned to" property from workflow assignments by adding the following script to the state that creates the assignment (select Run Script in the state's Actions tab):
Vault.ObjectPropertyOperations.RemoveProperty ObjVer, 79
That line removes the linking between the workflow and the assignment, so M-Files will no longer make changes to the assignment based on what is happening in the workflow. The assignment will then remain assigned to the correct user when the workflow moves forward.
(1 vote(s))
This article was helpful
This article was not helpful

Help Desk Software by Kayako case