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

As an App Adm, I want to make my form view available in different languages

    Details

    • Story Points:
      8
    • Sprint:
      App_Builder_7.3_23, App_Builder_7.3_24, App_Builder_7.3_25, App_Builder_7.3_26, App_Builder_7.3_27, App_Builder_7.3_28

      Description

      As an App Adm, I want to make my form view available in different languages

      Design Deliverables

      Mockups

      Context

      Once Liferay DXP is an international product with several customer that handles business all around the world, we need our solutions to be usable in different languages. To achieve that, we offer a capability named "Localization" that allow users not only to configure the solution's labels in the DXP default language, but also in several others langagues supported by Liferay.

      That being said, in this Story's scope users should be able to use Liferay DXP Localization capabilities in his App Builder Form Views.

      Acceptance Criteria

      1- Given that the translation component of a Form View is set to the default language,
      when the user defines the labels of the Form View's Fields,
      then the names defined by the user should be set as the Fields labels whenever the Form View is set to be shown in the default language.

      2- Given a user in the Form View Builder of App Builder,
      when the user clicks in the localization component at the top of the Form View,
      then the system should display for the user all languages supported by Liferay for translation.

      • The system should display which language is the Default, which ones already have a translation set and which ones doesn't have a translation set yet.

      3- Given that a user has selected a "Not Translated" language in the Localization component in App Builder's Form View,
      when the user defines the labels for each Form View Field,
      then the names defined by the user should be set as the Fields labels whenever the Form View is set to be shown in the that selected language.

      • After that, the selected Language should now be shown as "Translated" in the Localization component;
      • Those translations should be stored at Object Level, in a way that others Form Views (and Table Views) should reuse the translations of each field.

      4- Given that a user has set several language translations for a Form View in App Builder,
      when a user acesses that Form View in a deployed App,
      then all languages translations for the Form View should be available for the end-user.

      5- Given that a user is in the Form View Builder of a Fieldset,
      when the user defines translations for the Fieldset's fields,
      then those translations should be available whenever the fieldset is included in a Form View.

      6- Given that a user is in the Form View Builder that has a Fieldset in it,
      when the user defines translations for the fields in the Fieldset,
      then the translations should be saved and updated on all instances of the fieldset.

      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)
      • Make sure that it has the extensions points needed to allow GS and customers to customize the feature (If applicable)

        Attachments

        1.
        [DS] Mockups LPS-108834 Technical Task Closed Matheus Xavier  
        2.
        [PM] Acceptance Criteria LPS-112312 Technical Task Closed Matheus Xavier  
        3.
        [FE] Add the ClayLocalizationInput component to choose the untranslated language LPS-112388 Technical Task Closed Adriano Interaminense  
        4.
        [FE] Change the laguage for the Form view title LPS-112399 Technical Task Closed Adriano Interaminense  
        5.
        [BUG] Error after saving a Custom Object with a language other than English LPS-112508 Technical Task Closed Gabriel Albuquerque  
        6.
        [QA] Review ACs and Draft TCs LPS-112514 Technical Testing Closed Alex Candido  
        7.
        [QA] Manual validation - Round 1 - FAILED LPS-112515 Technical Testing Closed Alex Candido  
        8.
        [BUG] The user is not able to save an Object when the portal instance language is other than English LPS-112678 Impedibug Closed Adriano Interaminense  
        9.
        [FE] Update FormView to use editingLanguageId LPS-113209 Technical Task Closed Bruno Farache (Inactive)  
        10.
        [FE] Fix MultiPanelSidebar variant LPS-113224 Technical Task Closed Adriano Interaminense  
        11.
        [BE] Adapt fixed filters to support localized fields LPS-113456 Technical Task Closed Gabriel Albuquerque  
        12.
        The Save button on Form View became disabled after selecting any NOT-TRANSLATED language in the localization component LPS-114433 Impedibug Closed Guilherme Freire (Inactive)  
        13.
        The labels fields are not shown translated until the user clicks on a field LPS-114461 Impedibug Closed Guilherme Freire (Inactive)  
        14.
        [Impedibug] It's not possible to save/edit an existing form view when the current default instance language is different than the default instance language the form was created LPS-114466 Impedibug Closed Guilherme Freire (Inactive)  
        15.
        Object/Form name is missing when the current default instance language is not the same when the object/form was created LPS-114462 Impedibug Closed Guilherme Freire (Inactive)  
        16.
        [QA] Manual validation - Round 2 - FAILED LPS-114555 Technical Testing Closed Guilherme Freire (Inactive)  
        17.
        [Impedibug] It is not possible to create Objects when the default language is different from English LPS-115623 Impedibug Closed Guilherme Freire (Inactive)  
        18.
        [Impedbug] When the user tries to type the translation on a Select from List, Single Selection or Multiple Selection field, the focus changes to the input label from the default language LPS-115898 Impedibug Closed Guilherme Freire (Inactive)  
        19.
        Create feature flag for translation manager LPS-116378 Technical Task Closed Jeyvison Nascimento  
        20.
        [QA] Manual validation - Round 3 - FAILED LPS-116473 Technical Testing Closed Guilherme Freire (Inactive)  
        21.
        [Impedibug] Options from Select from List, Multiple Selection and Single Selection fields are losing options after translation LPS-116601 Impedibug Closed Guilherme Freire (Inactive)  
        22.
        [Impedibug] The translated fields are shown like language's default fields when the user tries to use them in different Forms from the same Object LPS-116625 Impedibug Closed Guilherme Freire (Inactive)  
        23.
        [Impedibug] The save button is disabled when the user tries to save a form view with other languages than the default language LPS-116793 Impedibug Closed Gabriel Albuquerque  
        24.
        [QA] Manual validation - Round 4 - PASSED LPS-117027 Technical Testing Closed Guilherme Freire (Inactive)  

          Activity

            People

            Assignee:
            support-qa Support QA
            Reporter:
            eduardo.zoby Eduardo Zoby
            Engineering Assignee:
            Adriano Interaminense
            Recent user:
            Kiyoshi Lee
            Participants of an Issue:
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Packages

                Version Package
                Master