As Content Creator, I want to leverage the structures’ translations with nested field when creating a new Web Content

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.4.13 DXP GA1, Master
• Component/s: Data Engine
• Labels:
  • 7.4-ce-ga1
  • 7.4_form_builder_replacement_must_have
• Epic Link: Localization to Data Engine
• Sprint: Data_Engine_7.4_04, Data_Engine_7.4_05, Data_Engine_7.4_06

As Content Creator, I want to leverage the structures' translations with nested field when creating a new web content

Context

With the migration of WEM from DDM to DE, we need to make sure that this change is as imperceptible as possible to our clients.

Acceptance Criteria

1- Given a user in Liferay Web Content
when changing the language of a web content
then the system should change the language of everything inside of the nested field

• The system should display the title of the field group from selected language
• The system should display all the labels of the fields from selected language

2- Given a user in Liferay Web Content

when changing the language of a web content created from a structure with nested fields
then the system should copy the content values from the default language

• These values are editable;
• These values must be saved with the translation in the selected language.

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)