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

As a Form Admin, I want to define my Field's Label without impacting the Field's ID (Name)

    Details

    • Epic Link:
    • Sprint:
      Forms_7.3_26, Forms_7.3_27, Forms_7.3_28, Forms_7.3_29, Forms_7.3_30

      Description

       Context

      During the validation of LPS-109657 (As a Form Admin, I want to check a summary of responses for my multiple selection field question), we identified that when a label is changed in a Form, the field name is changed too. We also verified that the user is able to change the field name of an option of a field (multiple selection, single selection, for example).

       Steps to reproduce

      1. Go to content and data > Add a Form
      2. Add a multiple selection field
      3. Put a label
      4. Change the label
      5. The field name is changed.

      Obs.:

      • 1 - the same behavior happens in ALL FIELDS and options (when the field has option);
      • 2 - consider the impact of this in Rules.

      To solve this problem, we must:

      • Removing the link between the Field Label and Field Name;
      • Auto generating unique Ids to be the Field Name;
      • Allowing each product that leverages on the Form Builder to define if the Field Name should be editable or not in the Product's UI.
        • Rename the field from "Field Name" to "Field ID";
        • Make it read-only in the Forms Portlet.

      Acceptance Criteria

       
      1- Given a user in a Liferay Form Builder,
      when the user adds a new field into the Form,
      then the system should automatically generate an unique Id as the Field's Name.

      • In Forms Portlet, the Field Name (id) should not be editable in the UI;
      • This also applies for the Options' Name in selection field types (Single Selection, Multiple Selection, Select from List, etc.);
      • This also applies when inserting Fieldset's Fields (old Element Sets).

      2- Given that a user has created a new field in a Form.
      when the user updates the Field's Label (or makes any other modification in the Field's configs),
      then the system should not automatically change the Field's Name (Id).

      • This also applies for the Options' Name in selection field types (Single Selection, Multiple Selection, Select from List, etc.).
      • This also applies when inserting Fieldset's Fields (old Element Sets).

      3- Given a product leveraging on Liferay Form Builder,
      when a developer is configuring the Form Builder properties,
      then the developer should be able to define if the Field Name (Id) should be available or not for edition in the UI of his product.

      • This also applies for the Options' Name in selection field types (Single Selection, Multiple Selection, Select from List, etc.).

      4- Given that a user updated an existing Form's Field Label,
      when the user checks this Field in the Rules, Reports or any other Form feature,
      then feature (rules, reports, etc.) must display the Field's new Label without losing the reference (understand as being still the same field).

      Side effects care

      Every change on Form Builder can generate side effects on App Builder and on the clients of Data Engine, therefore after finish each task of this story, specially the task of renaming the Field Name to Field Id on the UI, it's important to execute the tests of these two products. For App Builder, run its specific test suite (ci:test:app-builder).

      Definition of Done (DoD):

      • All Acceptance Criteria were passed;
      • Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
      • 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)
      • Make sure that it has the extensions points needed to allow GS and customers to customize the feature (If applicable)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              matheus.xavier Matheus Xavier (Inactive)
              Reporter:
              cleyton.magalhaes Cleyton Magalhaes (Inactive)
              Engineering Assignee:
              Renato Rêgo
              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
                  7.3.4 CE GA5
                  7.3.10 DXP GA1
                  Master