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

Allow a segment to be used to define the audience of another segment

    Details

    • Epic/Theme:
    • Sprint:
      TANGO | SP_22 | Oct17-Oct30, TANGO | SP_23 | Oct30-Nov13, TANGO | SP_24 | Nov13-Nov27, TANGO | SP_25 | Nov27-Dec11, TANGO | SP_26 | Dec12-Jan03, TANGO | SP_27 | Jan03-Jan22

      Description

      Motivation

      Currently it is not possible to segment users based on both DXP criteria (user profile, organization profile, session) and AC criteria (long term behavior). Also, in order to reuse an existing criteria from one segment to another, editors have to copy the criteria and keep it up-to-date with the original one. The goal of this story is to support the combination of segments (referred segments) to cover the mentioned use cases.

      Design

      The solution will be based on the existing criteria contributor pattern. Therefore a design is not needed. 

      Acceptance Criteria

      Segments can be used to define new segments

      • Given a segment exists
      • When an editor creates a new segment
      • Then the editor contains a section “Segments”
      • And the editor can drag&drop segments to the editor

      Update: For the sake of discoverability, the segments contributor is displayed even if no segments are available. Usability improvements for the segments contributor will be addressed in future stories. 

      Combined segments reflect on member preview

      • Given segment A and segment B 
      • When a new segment C is created with the combination of segments A AND/OR segment B
      • Then the preview member count/list shows the count/list of users that belongs to BOTH/ANY of the segments

      Users are segmented by the segment criteria and the referred segments

      • Given segment A and segment B, and a new segment C  created with the combination of segments A AND/OR segment B 
      • And a page with an experience for segment C
      • When a user that belongs to segments A AND/OR B access a page
      • Then the user is affected by experience C

      Segments which are already based on segments cannot be used to create new segments

      • Given segment A and segment B, and a new segment C  created with the combination of segments A AND/OR segment B 
      • When the editor creates a new segment with segments
      • Then segments A and B can be selected, but no segment C

      User is warned if any of the referred segments is removed

      • Given segment A and segment B, and a new segment C  created with the combination of segments A AND/OR segment B 
      • When segments A is removed and segment C is edited
      • Then the segment editor displays a warning (similar to Custom Fields)

      Test Scenarios

       

      AC ID Test Strategy Test Scenarios Is it covered by FrontEnd ? (JS-Unit) Is it covered by BackEnd ? (unit or integration)
      XX Smoke Segments contributor is shown only if there are existing segments YES
      01 Smoke Segment member preview count shows the correct number of users when segments are combined - YES
      02 Smoke Segment member preview list shows the correct users when segments are combined - YES
      03 Smoke User is assigned to segments with referred segments if they match the condition - YES
      04 Sanity Segments based on segments are not available to create new segments - YES
      05 Sanity Segments editor displays a warning if an entity name is not found YES -
       06 Smoke  Segments editor displays the entity name YES -

       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              carlos.brichete Carlos Brichete Báez
              Reporter:
              angelo.youn Angelo Youn (Inactive)
              Engineering Assignee:
              Eduardo García
              Recent user:
              Kiyoshi Lee
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  7.3.0 CE GA1
                  Master