Uploaded image for project: 'Nuxeo Elements'
  1. Nuxeo Elements
  2. ELEMENTS-1116

nuxeo-data-table should be compatible with a subset of properties of a complex

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.4.0
    • Fix Version/s: HOTFIX_10.10_2.4, 3.0.0
    • Component/s: UI

      Description

      The use case is to fill only a subset of properties of a complex element, e.g.

      • user1 fills in complex:string1
      • user2 fills in complex:string2
        => Only a subset of the complex property should be advertised to each user

      Steps to reproduce :
      1. Take an unused project and go in Modeler
      2. Create a document type “File2” extending « File »
      3. To the File2 document type, add a schema with a multivalued complex “cmplx” made of “string1” and “string2”
      4. Go in Designer, and configure the screens for File2 (create edit view metadata)
      5. In the “create” screen, there is a section Nuxeo-data-table for “cmplx” => edit it and remove “string2” from the subsection
      6. Save the work in progress
      7. In the “edit” screen, leave things as-is
      Now, deploy the project on a Nuxeo 10.10-HF20 + WebUI instance
      8. Boot and create a Workspace and a File2 document and enter values for string1
      => In the File2 create screen, notice that the values for string1 entered do not show up
      9. In the metadata section, notice the number of values entered at create time is known, but the values is string1 is lost
      10. When editing File2, in the edit screen, notice the number of values entered is known, but the values input at step 8 are lost.
      11. In the metadata section, notice the number of values entered at edit time appear as in an expected situation
      Expected result: removing in step 5 the “string2” from the create string (thus enabling the partial initialization of a complex) should leave make the create screen functional

      A workaround has been found in creating an empty column for each missing sub-element... Then, everything happens OK: when filling in a value, the value can be seen and is saved

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:

                PagerDuty

                Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.