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

As a form creator, I want to create masks for my decimal numeric type fields



      Design Deliverable



      In several use cases, to allow the user a better filling/reading experience, it is important to provide the known format of a given information, mainly if we are talking about long numbers. The most common case for masking decimal numbers are currency, but there are other as temperature, volume, length, distance and others.


      After analyzing the complexity of the context, we decided to divide the masking stories between integers and decimal numbers.

      Acceptance Criteria

      1 - Given a form creator,
      when adding a decimal numeric type field,
      then I must be able to add a mask to that field

      2 - Given an user filling a field with mask,
      when seeing the field empty,
      then I should be able to identify that the field has a mask

      3 - Given an user,
      when filling a numeric field with mask,
      then I should be able to read the value in the field mask

      • This must also happen in the view entries

      4 - Given a form creator,
      when creating a mask for a decimal field,
      then the field should be localizable.

      5 - Given a form creator,
      when creating a mask for a decimal field in the default language,
      then the field should be localizable.

      • The value from the default should persist in the other languages until the form creator edits in the specific language
      • If the mask is added in a language different from the default, the mask of the default language and other languages should be empty.

      6 - Given a form creator,
      when creating a mask for a decimal field with decimal separator different from the current language,
      then the separator chosen in the mask has priority.

      7 - Given a form creator,
      when creating a mask for a decimal field,
      then I must only be able to support 2 digits after the digital separator.

      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)


        Issue Links

          There are no Sub-Tasks for this issue.



              luiz.jardim Luiz Jardim
              luiz.jardim Luiz Jardim
              Product Team Bravo Product Team Bravo (Inactive)
              Kiyoshi Lee Kiyoshi Lee
              0 Vote for this issue
              0 Start watching this issue




                  Version Package
                  7.4.13 DXP GA1
         CE GA4