Uploaded image for project: 'Hippo CMS'
  1. Hippo CMS
  2. CMS-10965

Docbase field doesn't provide the same order changing and deleting item UI as Link field does

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Normal
    • Resolution: Available for testing
    • 5.0.2
    • 13.2.0
    • None
    • 3
    • Flagged
    • Tiger
    • Tiger Sprint 206, Tiger Sprint 207

    Description

      You can create document relationships by either "Link" field (by having compounds) or "Docbase" field (by having UUID string property) in document type editor.
      Even if a "Docbase" field is set to be "multiple" and "ordered", it doesn't provide the equivalent user experience to change orders and delete items like "Link" field does.
      See the following screenshots for your information:

      Document Type example having both "Link" field and "Docbase" field

      Both fields are configured to be "multiple" and "ordered".

      Document example having both "Link" and "Docbase" field.

      "Llink" field shows "up" and "down" arrows to change orders on mouse-hovering and "delete (X)" item button as well.
      However, "Docbase" field doesn't show those on mouse-hovering. You have to select each again and again to change the orders, which is really inconvenient.

      It would be nice if the "Docbase" field works like "Link" field for ordering and deleting on mouse-hovering.

      Attachments

        1. doc_link_docbase.png
          330 kB
          Woonsan Ko
        2. doctypes_link_docbase.png
          334 kB
          Woonsan Ko
        3. multiple ordered docbase.png
          45 kB
          Bert Leunis

        Issue Links

          Activity

            People

              Unassigned Unassigned
              wko Woonsan Ko (Inactive)
              UX Issues UX Issues
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: