"prevent adding user owned component" pre-condition failing with other operation
We have enabled:
"prevent adding user owned component" pre-condition for "default role".
But this now behaves strange. If a user tries to acquire a lock on a file or try to "unlock" a file, the team advisor pops up with this error message:
------------
Problem
An unhandled exception occurred during "Prevent Adding User Owned Component ".
Wrong type of argument: null
Reason
Prevent adding user owned component
-----------------
Strangely this action has nothing to do with "User Owned component"!!.
When remove this pre-condition, the lock action and unlock action works fine without any errors.
Is somebody else have experienced the same?
"prevent adding user owned component" pre-condition for "default role".
But this now behaves strange. If a user tries to acquire a lock on a file or try to "unlock" a file, the team advisor pops up with this error message:
------------
Problem
An unhandled exception occurred during "Prevent Adding User Owned Component ".
Wrong type of argument: null
Reason
Prevent adding user owned component
-----------------
Strangely this action has nothing to do with "User Owned component"!!.
When remove this pre-condition, the lock action and unlock action works fine without any errors.
Is somebody else have experienced the same?