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

As a Form Creator, I'd like to add a Single Selection field to my form



      Acceptance Criteria:

      Adding field

      1. Add field on the page/stage by dragging and dropping it.
      2. Field name should start with its field type as field label and field name, as default behaviour, must import the field label. 

      Tab Basic

      1. after added, the field's label should be "Multiple Selection" (currently it is "check box" please, update it).
      2. Field name (field id) must comes from the field label, but as "camelCase".
      3. it can be populated just manually
      4. Field is switchable - Check the linked issue "-LPS-88149-"
      5. Follow the same behaviour we currently have on Alloy component. 
      6. It should have at least two options
      7. if it has only one option, after add the field type the cursor must be active in label field
      8. it should start with two text area available to add options
      9. the first option must contais the placeholder "Option"
      10. The second one  must contais the placeholder "Enter an Option"
      11. Whenever users interact with the last empty - does not matter its position on option list - another blank option must be available on the end of the list.
      12. the last option (the empty one) mustn't have the icon "X" to be removed 

      Tab Properties

      1. Predefined option must be a select and its options must comes from the options populated on Basic tab.
      2. Show Label must be active by default
      3. repeatable must be deactivate by default
      4. Allow multiple selections must be disable by default
        1. Once disabled, the selector must be a single one.
        2. Once disabled, users will be able to select only an option on Predefined Option Selector.

      Definition of Done:

      • ( ) All Acceptance Criteria were passed;
      • ( ) Related tests created 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 issue related to Story scope (ex.: similar of a FP4, FP5 bug);
      • ( ) Make sure that all system documentation were updated (if necessary).


          Issue Links



              jadson.dantas Jadson Dantas (Inactive)
              alex.candido Alex Candido
              Recent user:
              Alex Candido
              Participants of an Issue:
              0 Vote for this issue
              0 Start watching this issue




                  Version Package