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

    • Type: Story
    • Status: In Design
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Data Engine
    • Labels:

      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

      • 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 de position of the section (as a whole group of fields) in the Form.
      • 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.
      • 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.
      • 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.
      • 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.
      • 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.
      • 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.
      • 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

          Activity

            People

            • Assignee:
              felipe.pires Felipe Pires
              Reporter:
              eduardo.zoby Eduardo Zoby
              Recent user:
              Matheus Xavier
              Participants of an Issue:
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Packages

                Version Package