peter_hajdu
New member
Hi<?:namespace prefix = o ns = "urn:schemas-microsoft-com
ffice
ffice" /><?:NAMESPACE PREFIX = O /><O
></O
>
We have the same problems sometimes with not only frozen components but also with frozen features in assemblies.<O
></O
>
The problem is that however there are some frozen elements in the model tree, WF2 still regenerates it and the user should check and verify them before storing.<O
></O
>
If not, than the stored job contains unverified errors. (Sometimes serious)<O
></O
>
What could I do to disable this function and WF2 should fail to regenerate if any reference is missing? Or at least how to get a warning message whes saving in WF2 that there are frzozen elements is the model tree?
We have the same problems sometimes with not only frozen components but also with frozen features in assemblies.<O
The problem is that however there are some frozen elements in the model tree, WF2 still regenerates it and the user should check and verify them before storing.<O
If not, than the stored job contains unverified errors. (Sometimes serious)<O
What could I do to disable this function and WF2 should fail to regenerate if any reference is missing? Or at least how to get a warning message whes saving in WF2 that there are frzozen elements is the model tree?