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

As an form creator, I want to have a hidden field in my form to trigger rules




      Today, in many cases we have the need to trigger our rules with information from external information retrieved from APIs or even from internal information, as calculation results in the form that should trigger a rule but the final user wouldn't have to see it.

      Use case:

      • If a user is selecting multiple products and each has a value, I want to calculate the total in a hidden field so this triggers a rule where I can suggest the best plan.
      • If a user wants to collect data from the user for a insurance policy and the user is married (information from external souce), then the field for filling the partner's information must be shown and required.

      Design Deliverable


      Acceptance Criteria

      1 - Given an form creator,
      when adding a text or numeric field,
      then I should be able to define a field as hidden

      2 - Given an user,
      when filling a form with hidden fields,
      then I must not be able to see those fields in any way

      3 - Given an admin user,
      when editing a form with hidden fields,
      then I must be able to identify which fields are hidden

      4 - Given a form creator,
      when adding rules with the ''Show'', ''require'' and ''enable'' actions,
      then the hidden fields should not appear in the listed fields that follows as option

      5 - Given a form creator,
      when defining a field as hidden,
      then following properties of the fields should be disable:

      • For text fields: Required Field, Validation, Require Confirmation, Autocomplete, Show Label, Repeatable.
      • For numeric fields: Required Field, Validation, Require Confirmation, Autocomplete, Show Label, Repeatable, Mask.

      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



              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.2 CE GA3 DXP 7,4
                  7.4.13 DXP GA1