As Content Creator, I want to leverage the structures' translations without nested fields or fieldsets 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 without nested fields or fieldsets 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 creating a web content using an existing structure
then the system should allow the user to use the translations from the structures

• This must happen when creating web content from structures with one translation;
• This must also happen when creating a web content from structures with more than one translation;
• This must also happen when creating a web content from structure with duplicated fields;

2- Given a user in Liferay Web Content
when changing the language of a web content created from a structure
then the system should display the field properties translation from the structure

3- Given a user in Liferay Web Content
when changing the language of a web content created from a structure
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.

4- Given a user in Liferay Web Content
when changing the language of a web content created from a structure
then the system should copy the title of the web content from the default language

• This title is editable;
• This title must be saved with the translation in the selected language.

5- Given a user in Liferay Web Content
when changing properties of a content the default language of a web content created from a structure
then the system should persist these properties to every correspondent field from other translations that was not edited

6- Given a user in Liferay Web Content
when changing the language of a web content created from a structure
then the system should automatically change the language of the web content summary

• The opposite must also happen, when changing the language in the description the language of the web content automatically changes too.

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)