Using documents we currently face some strange changes in be way PTC handles the “Documents” relationship in Segments.
As it seem impossible to find a manual/howto that fully describes how it is supposed to work I wrote down all case we can see currently in our system.
>> field Documents contains the project backing item
Document Change Project
>> field Documents contains new the project backing item
Set Field “Root Document” to false
>> field “Documents” becomes empty
EVEN if the current User has NO project administrator permission
Set Field “Documents” to project backing Item (ONLY possible if the current User has project administrator permission)
>> field “ROOT Documents” stays FALSE
Set Field “Root Document” to TRUE
>> field “Documents” stays empty
EVEN if the current User has project administrator permission
Insert or Include a ROOT Document into another Segment
ONLY if the current User has project administrator permission, otherwise
and cannot be modified, unless the current User has project administrator permission
Especially the last case leads to "lost" documents, as once included elsewhere, the document won't appear in a finder dialog anymore.
I am wondering whether I am the only one having issues with this.
Any reply wellcome
quite interesting issue.
I can add that we have
a) aTrigger: MKS.ALM: Relate Root Document to Project
b) a Query: Top Level Documents
c) a Report: Top Level Documents (in Project)
If the behaviour you describe here has any meaning, was intended or not, I cant say.
My guess is that perhaps the ALM trigger is not covering all circumstances correctly?