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

As a Form Admin, I want to customize the label of the Submit button



      As a Form Admin, I want to customize the label of the Submit button, so that I can adapt the term accordingly to my business context.

      Design Deliverables



      Once Liferay (and Forms) are a multi-use solutions, we may have different customers with different business context and purpose for creating Forms and in some of those use cases, the label of the button to "Submit" (or "Submit for Publication") are not the best fit for the context.

      To solve that, we should allow Form builders to customize the label they want for the submit button.

      Acceptance Criteria

      1- Include an option in settings to customize the label of the submit button

      Given an user in Liferay Forms Builder,
      when the user accesses the "Settings" of the Form,
      then the system display a option to define which label should be displayed in the Submit button of the Form.

      • The customized label must be a text and have between 1 and 25 characters.
      • Special characters and numbers should be allowed, as long as it doesn't have potential to break the UI or anything else.

      2- Show the customized label for the end-user when filling the Form

      Given that a user successfully reached the scenario of Acceptance Criteria 1, defined a customized label for the submit button and published the Form,
      when an end-user accesses the Form,
      then the button displayed to submit the entry should be using the label defined by the user in the settings.

      3- Support for Localization

      Given that a user is building a multilingual Form in Liferay,
      when the user customizes the label of the submit button of the Form,
      then he must be able to customize the submit button label of each supported language of the Form.

      • The language in the forms and the modal must always match

      4- Restoring default value

      Given that a form admin is editing the submit button,
      when the user leaves the field empty and clicks out,
      then the system must restore the default value of the submit button.

      • This must happen for the default value of each language

      5- Workflow powered forms

      Given that a form admin user has edited the submit button label,
      When creating a form powered by workflow,
      Then the system must replace the default value (''Submit for Publication'') by the new submit button label.

      6- Customization feedback

      Given a form admin,
      When customizing the submit button,
      Then the system must label the supported languages that are customized and the ones that are not.

      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
              matheus.xavier Matheus Xavier (Inactive)
              Recent user:
              Sophia Zhang
              Participants of an Issue:
              0 Vote for this issue
              1 Start watching this issue




                  Version Package
                  7.4.13 DXP GA1