cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

What is the expected/correct behavior for ROOT Documents?

Highlighted
Aquamarine

What is the expected/correct behavior for ROOT Documents?

 

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.

  • Create a new Document
    • Documen create…

    • Enter fields in Dialog
    • Set field “Root Document” to TRUE
      • >> field Documents contains the project backing item

  

 

  • Move a ROOT Document
    • Document Change Project

    • Enter fields in new Project
    • Ensure field “Root Document” is TRUE
      • >> field Documents contains new the project backing item

  

 

  • Branch a ROOT Document
    • Document Branch…

    • Enter fields in new Project
    • Ensure field “Root Document” is TRUE
      • >> field Documents contains new the project backing item

  

 

  • Change “Root Document” to false
    • Set Field “Root Document” to false

      • >> field “Documents” becomes empty

        • EVEN if the current User has NO project administrator permission

  

 

  • RE-Add a NON “Root Document” to Project
    • Set Field “Documents” to project backing Item (ONLY possible if the current User has project administrator permission)

      • >> field “ROOT Documents” stays FALSE

  

 

  • Branch a NON ROOT Document
    • Document Branch…

    • Enter fields in new Project
    • Ensure field “Root Document” is FALSE
      • >> field “Documents” becomes empty

  

 

    

  • Insert or Include a ROOT Document into another Segment

    • Content/Include/Document….
    • Select a ROOT Document from a project
    • Ensure field “Root Document” is TRUE
      • >> field Documents contains the project backing item

        • ONLY if the current User has project administrator permission, otherwise

  

 

  • Insert or Include a NON ROOT Document into another Segment
    • Content/Include/Document…
    • Select a NON ROOT Document from a project
    • Ensure field “Root Document” is FALSE
      • >> field “Documents” becomes empty

        • 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

  

Tags (1)
1 REPLY 1
Highlighted

Re: What is the expected/correct behavior for ROOT Documents?

Hello Matthias,

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?

Volker

Announcements