Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-98077

As a Developer, I want to the ability to nest fields

    Details

    • Sprint:
      Data_Engine_7.3_17, Data_Engine_7.3_18, Data_Engine_7.3_19, Data_Engine_7.3_20, Data_Engine_7.3_21, Data_Engine_7.3_22, Data_Engine_7.3_23, Data_Engine_7.3_24, Data_Engine_7.3_27, Data_Engine_7.3_25, Data_Engine_7.3_26, Data_Engine_7.3_28

      Description

      Design Deliverable:

      Mockups

      As a Developer, I want to implement the ability to nest fields.

      Context:

      Nested fields is a feature of DDM that allows users to place a field nested into other fields. By nesting fields, the users can achieve two things:

      1. Visual indentation for nested fields;
      2. Possibility to repeat an entire the nested fields as a whole group

      In Data Engine (new form builder), we want to replace this nesting feature by using the element "Sections". When creating a new form, users will be able to place fields inside a section, which will work as a group that can be repeatable, just like it was on DDM nesting.

      In addition, users should also be able to:

      • Place section inside section;
      • Configure a section to be repeatable or not;
      • Configure a section to be Collapsible or not (a feature that adds the possibility to expand and collapse the fields of a section).

      Behavior on tab 'Structures' (builder):

      • The components reorganizes themselves when you take a component upon their.
      • The center of the dragged component is used as his reference target.

      Behavior on tab 'Web Content' :

      • Render the nested field arrangement built before
      • Drag/Drop interaction is not allowed

      Behavior on sites:

      • Nest arrangement is not present in this state.
      • Drag/Drop interaction is not allowed

      Acceptance Criteria

      • 1 - Given that a user is creating a Data Definition for an App, when the user is defining the fields of the Data Definition, then users should be able to define that two or more fields are grouped into a section.
        • Users should also be able to drag and change the de position of the section (as a whole group of fields) in the Form.
      • 2 - Given that a user has created a section of fields in a Data Definition, when the user is configuring the section, then he should be able to define the section as repeatable.
      • 3 - Given that a user has created a section of fields in a Data Definition, when the user is configuring the section, then he should be able to define the section as collapsible.
      • 4 - Given that a user has created a section of fields in a Data Definition, when the user decides to create a second section, then he should be able to place this second section inside the first section (nesting).
        • Users should be able to create the second section already inside the first one;
        • Users should be able to move an existing section to be inside (nest into) another existing section.
      • 5 - Given that a Data Definition is being rendered in a Form by the taglib and the form has a repeatable section, when the user clicks on the repeat button of the section, then the system should repeat the entire section for the user to fill it.
        • Users should be able to repeat the section also when submitting new records for the Data Definition through API calls.
      • 6 - Given that a Data Definition is being rendered in a Form by the taglib and the form has a collapsible section, when the user clicks on the collapse button of the section, then the system should collapse the fields in that section.
      • 7 - Given that a Data Definition is being rendered in a Form by the taglib and the form has a collapsible section, when the user clicks on the expand button of the section, then the system should expand and show the fields in that section.
      • 8 - Given that a Data Definition is being rendered in a Form by the taglib and the form has a section inside (nested into) another section, when the users see those sections in the form, then he should be able to identify that a section is inside(nested) another section.

      Definition of Done (DoD):

      • All Acceptance Criteria were passed;
      • Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
      • Verify if the test labels were added;
      • Code with peer review completed;
      • Validated by QA, Product Designer and/or PM;
      • No critical bug related to Story scope (ex.: similar of FP4, FP5);
      • Make sure that all system documentation were updated (if necessary)

        Attachments

          Issue Links

          1.
          [DS] Mockups LPS-107150 Technical Task Closed Matheus Xavier  
          2.
          [FE] Initial bulk work covering most use cases (listed in the description) LPS-109943 Technical Task Closed Bruno Basto (Inactive)  
          3.
          [FE] Given that a user has created a section of fields in a Data Definition, when the user is configuring the section, then ser should be able to define the section as collapsible LPS-109939 Technical Task Closed Bruno Basto (Inactive)  
          4.
          [FE] When moving all fields out of a section, it should no longer exist LPS-109940 Technical Task Closed Alexandre Araujo  
          5.
          [FE] Multiple levels of nesting should be allowed LPS-109941 Technical Task Closed Bruno Basto (Inactive)  
          6.
          [FE] Resizing columns inside sections should be allowed LPS-109942 Technical Task Closed Bruno Basto (Inactive)  
          7.
          [FE] [BE] Rename field from "Section" to "Fieldset" LPS-110003 Technical Task Closed SE Support  
          8.
          [FE] User should be able to select a nested field by clicking on it LPS-110136 Technical Task Closed Brian Chan  
          9.
          [FE] It should be allowed to resize fields of a section LPS-111130 Technical Task Closed Bruno Basto (Inactive)  
          10.
          [FE] It should be able to render a Form with nested fields and values (for editing) LPS-111568 Technical Task Closed Bruno Basto (Inactive)  
          11.
          [FE] Rules editor should list nested fields, but not the "Fields Group" field. LPS-111882 Technical Task Closed Bruno Basto (Inactive)  
          12.
          [FE] Indentation of nested fields do not look like mockups LPS-112393 Technical Task Closed Bruno Basto (Inactive)  
          13.
          [BE] Saving a nested field throws Exception LPS-112699 Technical Task Closed Bruno Basto (Inactive)  
          14.
          [QA] Review ACs and Draft TCs LPS-113028 Technical Testing Closed Alex Candido  
          15.
          [QA] Manual validation - Round 1 - FAILED LPS-113029 Technical Testing Closed Alex Candido  
          16.
          It is not possible to save a second form containing one of the field types already used in another section of an existing form LPS-113202 Impedibug Closed Bruno Basto (Inactive)  
          17.
          Fields are duplicating when dragging and dropping a new field between the existing ones of a section LPS-113203 Impedibug Closed Alex Candido  
          18.
          The "Repeatable" icon for the sections are badly positioned on the Form View Builder LPS-113213 Impedibug Closed Alex Candido  
          19.
          The "Repeatable" button for the sections are badly positioned on the Form View (published app) LPS-113214 Impedibug Closed Alex Candido  
          20.
          Form View builder breaks when clicking (object sidebar) in the fields that were added to a section LPS-113275 Impedibug Closed Alex Candido  
          21.
          [QA] Manual validation - Round 2 - FAILED LPS-113216 Technical Testing Closed Alex Candido  
          22.
          Form Builder breaks when resizing a field added to a section LPS-113768 Impedibug Closed Alex Candido  
          23.
          Form Builder breaks when deleting a section from a form view LPS-113773 Impedibug Closed Alex Candido  
          24.
          [QA] Manual validation - Round 3 - FAILED LPS-114210 Technical Testing Closed Alex Candido  
          25.
          It's not possible to save a form after duplicating a field group (section) LPS-114358 Impedibug Closed Guilherme Freire  
          26.
          Editing a field of a duplicated section is editing its parents fields LPS-114361 Impedibug Closed Guilherme Freire  
          27.
          [QA] Manual validation - Round 4 - FAILED LPS-114389 Technical Testing Closed Alex Candido  
          28.
          Field Group name is not shown on Form View and on app deployed (it is only shown if the collapsible property is set) LPS-114816 Impedibug Closed Guilherme Freire  
          29.
          Form/Table View breaks when reopening a form with a group field (created by dragging and dropping a field from the form view body instead of the sidebar) or creating a new table LPS-114818 Impedibug Closed Alex Candido  
          30.
          Repeatable property is not working on a Field Group available on the deployed app (it is only working if the collapsible property is set) LPS-114884 Impedibug Closed Guilherme Freire  
          31.
          [QA] Manual validation - Round 5 - Forms - FAILED LPS-114889 Technical Testing Closed Guilherme Freire  
          32.
          [Impedibug] Field or Field Group is being removed from the object when clicking to Remove from form view body LPS-114929 Impedibug Closed Alex Candido  
          33.
          [Impedibug]It is not possible to add and save a second form containing one a field group already used in another section of an existing form LPS-114354 Impedibug Closed Alex Candido  
          34.
          [QA] Manual validation - Round 6 - Web Content - FAILED LPS-115100 Technical Testing Closed Guilherme Freire  
          35.
          [Impedibug] The entries are not shown in Forms details once they make part of a Group Field LPS-115196 Impedibug Closed Cleyton Magalhaes  
          36.
          [Impedibug] The entries details are not shown in Forms details once they make part of a Group Field LPS-115198 Impedibug Closed Leonardo Barros (Inactive)  
          37.
          [QA] Manual validation - Round 7 - PASSED (Forms) LPS-115324 Technical Testing Closed Cleyton Magalhaes  
          38.
          Taglib Builder breaks when the user creates a field group with three fields (one of them not making part of the Group Field) LPS-115339 Impedibug Closed Guilherme Freire  
          39.
          It is not possible to create a Field Group using a field that is already part of a field group LPS-115426 Impedibug Closed Matuzalém Teles  
          40.
          [QA] Manual validation - Round 8 - Web Content - FAILED LPS-115728 Technical Testing Closed Paloma Nunes (Inactive)  
          41.
          [Impedibug] Error when editing a Web Content Structure adding a field group with a field which already is present - PASSED LPS-116545 Impedibug Closed Alex Candido  
          42.
          [Impedibug] It is allowed edit Structures with no fields - PASSED LPS-116629 Impedibug Closed Alex Candido  
          43.
          [Impedibug] Repeatable does not work for field groups - PASSED LPS-116632 Impedibug Closed Alex Candido  
          44.
          [Impedibug] Error when removing a duplicated field when it is in the middle of other duplicated fields - PASSED LPS-116635 Impedibug Closed Alex Candido  
          45.
          [Impedibug] It is being possible to publish a Web Content when it is with errors ("Oops! An error happening. Try again!") - PASSED LPS-116637 Impedibug Closed Alex Candido  
          46.
          [QA] Manual validation - Round 9 - Web Content - Test Scripted - PASSED LPS-117370 Technical Testing Closed Alex Candido  
          47.
          [QA] Manual validation - Round 10 - Forms - Brief Validation - PASSED LPS-117371 Technical Testing Closed Alex Candido  
          48.
          [QA] Manual validation - Round 11 - Documents and Media - Brief Validation - PASSED LPS-117372 Technical Testing Closed Alex Candido  
          49.
          [QA] Manual validation - Round 12 - Web Content LPS-117750 Technical Testing Closed Manoel Cyreno  

            Activity

              People

              Assignee:
              alex.candido Alex Candido
              Reporter:
              eduardo.zoby Eduardo Zoby
              Engineering Assignee:
              Bruno Basto (Inactive)
              Recent user:
              Kiyoshi Lee
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  Master