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

As an App Adm, I want to add new number fields on my object

    Details

      Description

      As an App Adm, I want to add new number fields on my object, so that so that I can collect, store and show numbers information in my object

      Design Deliverables:

      Mockups

      The Number Field Type:
      As well known, the number field is one of the most used type of fields for forms and also attribute type of objects. Therefore, we decided to have it as the one of the firsts available field types of the App Builder. In this Story, we aim to allow users to drag, drop and include number fields into their Form Views, and consequently, add number field to the data model of the custom object.

      The Number Field Type should be available with the same features and properties of Forms, but with a few differences:

      • In the App Builder, Number fields will have an "Autocomplete", in which will be a new tab and will only one option:
        • Autocomplete from Data Object (aka Lookup) - (doesn't need to be implemented yet, there will be a Story just for it)
      • The tab "Properties" will be renamed to "Advanced"
        • A few options may have been moved between the two tabs (Basic and Properties,  pay attention to the mockups to get it right.)

      Acceptance Criteria:

      • Given a user in the "Form View Builder" screen of an object, when the user drags and drop a "Number" field type from the sidebar into the Form stage area, then the system must include and display a Number type field into the current Form View.
      • Given a user in the "Form View Builder" screen of an object, when the users includes a new "Number" field type into the Form View , then the system must also automatically include a new "Number" field type into the Data Model of the object.
      • Given a user in the "Form View Builder" screen of an object, when the user is dragging and dropping a "Number" field into the Form stage, then he should be able to choose the place where the number field should be displayed in the Form View.
      • Given that a user has included a "Number" field into a Form View of an Object, when the user highlights/selects the field in the Form View stage area, then the system must provide the user with the same options and properties of the "Number" field available in the Forms module.
        • Including: Change label, set a placeholder, set a help text, required, change field name, enter a predefined value, change searchable options, show/hide label, make repeatable, set a validation, numeric type, etc.
      • Given that a user has included a "Number" field into a Form View of an Object, when a user clicks in the "Duplicate" option of the field kebab menu, then the system must automatically create a copy of the field into the Form View and in the Object model.
        • Obs: use the same behavior of the Forms module.
      • Given that a user has included a "Number" field into a Form View of an Object, when the user clicks in the "Remove From Object" option of the field kebab menu, then the system must remove the field form the Form View and also remove it from the data model of the Object.
        • Obs: When the field is being used by other Form Views, the system must warn the user and propagate the deletion to the other forms.
      • Given that a user has included a "Number" field into a Form View of an Object, when the user clicks in the "Remove from Form" option of the field kebab menu, then the system must remove the field from the Form View, but keep it as an attribute of the object;
        • Obs: When the field is being used by other Form Views, the system must delete the field from the Form View in question, but keep it in those other Form Views.
      • Given that a user has included a "Number" field into a Form View of an Object, when the user drag and drops an existing field in the stage area, then the system must allow the user to reorder the position of the field in the Form View.
      • Given that a user has included a "Number" field into a Form View of an Object, when the user highlights/selects the field in the Form View stage area, then the system must allow the user to see and change the properties of the field.

      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

            Activity

              People

              Assignee:
              alex.candido Alex Candido
              Reporter:
              eduardo.zoby Eduardo Zoby
              Recent user:
              Brian Wulbern
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  Master