Remove Field-Path Relationship (FPR) in Documentation branch

Users would like to store Generic Documents in the Documentation branch in thier own Folder or Sub Folder. Curently the Documentation branch has a Field-Path Relationship (FPR) with the Discipline and Classification. This limits the ability of the user to store documents in their own folders or sub folders. Unless their is a valid reason to use FPR in the Documentation branch I suggest to remove it to provide more flexibility and useability.

  • Coen Vromans
  • Dec 1 2020
  • Will not implement
  • Attach files
      Drop here to upload
    • Admin
      Arjen Bos commented
      April 20, 2021 19:31

      At this point, this is not planned.

    • Coen Vromans commented
      December 02, 2020 08:56

      A separate hierarchy lookup in the Documentation Branch is more adminstration and configruation work. It also limits the hierachy to two levels only.

    • Rene Vermeulen commented
      December 02, 2020 07:08

      I'm not a fan of allowing users to create their own folders in Documentation branch. I prefer to define a separate hierarchy lookup for the 2 levels in the Documentation branch.