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

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: Master
• Component/s: App Builder
• Labels:
  • 7.3-app_builder_must_have
  • 7.3-ce-ga6
  • appbuilder_test_manual
  • appbuilder_test_needed
• Epic Link: App Builder - Advanced Forms Tools
• Sprint: App_Builder_7.3_29, App_Builder_7.3_30, App_Builder_7.3_31
• Git Pull Request: https://github.com/jeyvison/liferay-portal/pull/852

As an App Adm, I want to make my App deployed available in different languages.

Design Deliverable

Mockups

Context

Once Liferay DXP is an international product with several customers 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 allows users not only to configure the solution's labels in the DXP default language but also in several others languages supported by Liferay.

That being said, in this Story's scope, App's final users should be able to:

• Check in what languages the App is available;
• Change the language of the entire App to his preference.

Acceptance Criteria

1- Given a end-user navigating in a deploy App created through App Builder,
when the end-user clicks in the Language Localization button in the deployed App,
then the system should list for the user all translations available for the App.

2- Given the situation described in the Acceptance Criteria 1,
when the end-user selects one of the languages available,
then the entire App (Table, Form, Labels, Buttons and Menus Options) should be displayed in the language/translation selected by the end-user.

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)