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

As Content Creator, I want to define reusable translations when creating WEM Structures without nested fields or fieldsets

    Details

    • Sprint:
      Data_Engine_7.4_02, Data_Engine_7.4_03, Data_Engine_7.4_04, Data_Engine_7.4_05, Data_Engine_7.4_06

      Description

      As Content Creator, I want to define reusable translations when creating WEM Structures without nested fields or fieldsets

      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 structure
      then the system should save the translation and alow the user to reuse them as needed

      • This must happen with structures with one translation;
      • This must also happen with structures with more than one translation;
      • This must also happen when the structure has duplicated fields;
      • The same behavior must happen when a user is editing an existing structure;

      2- Given a user in Liferay Web Content
      when changing the language of a structure
      then the system should copy the field properties from the default language

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

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

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

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

      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

          Issue Links

          There are no Sub-Tasks for this issue.

            Activity

              People

              Assignee:
              support-qa Support QA
              Reporter:
              luiz.jardim Luiz Jardim
              Engineering Assignee:
              Marcela Cunha
              Recent user:
              Sophia Zhang
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  7.4.13 DXP GA1
                  Master