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

As a FragmentRenderer developer I can make the programmatic fragment configurable to non-technical users

    Details

      Description

      As a FragmentRenderer developer I want to make the programmatic fragment configurable to non-technical users so that this type of fragment can also benefit from configurability

      Motivation

      LPS-96685 has introduced the ability for fragments to have configuration. The goal of this Story is to extend this capability to fragments developed using FragmentRenderer.

      Non-technical users adding a configurable fragment created as a FragmentRenderer to a page should be able to configure it using the same UI as for any other configurable fragments.

      Design Deliverables

      Not needed

      Technical considerations

      It should be evaluated whether the definition of the configuration should be done with the same JSON conf definition file as for other fragments or with a configuration interface (which should then be automatically converted to the JSON)

      Acceptance Criteria

      1. Deployment of a new FragmentRenderer fragment

      • Given a FragmentRenderer implementation which provides a configuration
      • When deployed into a Liferay server
      • Then the fragment can be added to a page and configured with a floating panel

      2. Deployment of a FragmentRenderer fragment with a change to the configuration

      • Given a FragmentRenderer implementation which provides a configuration and has been added to one page already
      • When the configuration changes and the fragment is re-deployed into a Liferay server
      • Then the fragment can be added to a page and configured with a floating panel shows the changes in the configuration
      • and the fragment already added to a page shows a floating panel with the new configuration 

      3. Staging with one experience in a page

      • Given a site with local or remote staging enabled
      • and a page of the site which has configurable fragments with an specific configuration
      • When the page is published to live
      • Then the page should be published with the fragment
      • and its specific configuration

      4. Staging with several experiences in a page

      • Given a site with local or remote staging enabled
      • and a page of the site which has configurable fragments with a specific configuration
      • and several experiences in a page
      • When the page is published to live
      • Then the page should be published with the fragment
      • and its specific configuration for each experience

      5. Staging with one experience in a page

      • Given a site with local or remote staging enabled
      • and a page of the site which has configurable FragmentRenderer fragments with an specific configuration
      • when the page is published to live
      • then the page should be published with the fragment
      • and its specific configuration

      6. Staging with several experiences in a page

      • Given a site with local or remote staging enabled
      • and a page of the site which has configurable FragmentRenderer fragments with a specific configuration
      • and several experiences in a page
      • when the page is published to live
      • then the page should be published with the fragment
      • and its specific configuration for each experience

      7. Personalized Experiences for a specific experience

      • Given a page of a site with several personalized experiences
      • when the configuration of a FragmentRenderer fragment is changed for a specific experience
      • then the configuration change should only affect that experience
      • and not others.

      8. Personalized Experiences for a default experience

      • Given a page of a site with several personalized experiences
      • when the configuration of a FragmentRenderer fragment is changed for the default experience
      • then the configuration change should not affect any other experience of the page.

      Features that don't need to be implemented (yet)

      • Validation of the configuration on deployment

        Attachments

        There are no Sub-Tasks for this issue.

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Packages

                Version Package
                7.2.X
                Master