Collections Personalized Variations to be reordered for prioritization purposes while accessing the details

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: 7.2.10 DXP FP1, Master
• Fix Version/s: Master
• Component/s: Segments Editor
• Labels:
  • d_21_08
  • d_21_10
  • ee-ts
  • fc_21_11
  • fc_22_01
  • liferay-update-dxp-3-7413
  • liferay-update-dxp-4-7413
  • liferay-update-dxp-6-7413
  • pt-app-security-review
  • pt-upgrade-review
• Epic/Theme:
  • Segmentation
• Epic Link: tango-collections-variations-prioritization
• Sprint: TANGO | #65 DIS | Aug09-Aug27, TANGO | #66 DIS | Aug27-Sep17, TANGO | #67 DIS | Sep20-Oct08, TANGO | #68 DIS | Oct11-Oct29, TANGO | #69 DEV | Oct29-Nov19, TANGO | #70 DEV | Nov19-Dec10, TANGO | #71 DEV | Dec10-Jan14, TANGO | #72 DEV | Jan14-Feb04, TANGO | #73 DEV | Feb04-Feb25
• Git Pull Request: https://github.com/liferay-tango/liferay-portal/pull/2031

It's not clear how personalized variations are ordered.

The result is that creating variations doesn't often work as expected.

Design

I have included the previous versions to refine and decide which one is the best:
Figma File

Requirements

• Variations can be reordered with a drag and drop action
• New variations created will be placed by default at the end of the list
• Collections will have always a "Default" variation - the "Anyone" one (no empty state)
• There will be a accessibility mode using the elipsis menu and the different options: Prioritize, Deprioritize and Delete

Acceptance Criteria

Requirements	Acceptance Criteria	Test Strategy	Covered by frontend test? (Yes/No)	Covered by backend test? (Yes/No)
Variations can be reordered with a drag and drop action	Given the personalized variations list of a Manual Collection When the user keeps click over a variation and moves it up or down in the variations list Then the selected variation is positioned where the user release the click in the list	High	Yes	No
	Given the personalized variations list of a Dynamic Collection When the user keeps click over a variation and moves it up or down in the variations list Then the selected variation is positioned where the user release the click in the list	High	Yes	No
New variations created will be placed by default at the end of the list	Given the personalized variations list of a Manual Collection When the user creates a new variation Then the new variation is positioned at the end of the variations list	High	No	No
	Given the personalized variations list of a Dynamic Collection When the user creates a new variation Then the new variation is positioned at the end of the variations list	High	No	No
Collections will have always a "Default" variation - the "Anyone" one (no empty state)	Given the personalized variations list of a Manual Collection Then the variations list always contains the "Anyone" variation	High	No	No
	Given the personalized variations list of a Dynamic Collection Then the variations list always contains the "Anyone" variation	High	No	No
There will be a accessibility mode using the elipsis menu and the different options: Prioritize, Deprioritize and Delete	Given the personalized variations list of a Manual Collection When the user opens the elipsis menu of a variation Then the options Prioritize, Deprioritize and Delete appear in the menu	Medium	Yes	No
	Given the personalized variations list of a Manual Collection When the user opens the elipsis menu of a variation and clicks on Prioritize Then the variation name is moved upwards in the list of personalized variations (unless is the first variation of the list)	Medium	Yes	No
	Given the personalized variations list of a Manual Collection When the user opens the elipsis menu of a variation and clicks on Deprioritize Then the variation name is moved downwards in the list of personalized variations (unless is the last variation of the list)	Medium	No	No
	Given the personalized variations list of a Manual Collection When the user opens the elipsis menu of a variation and clicks on Delete Then the variation name is removed from the list of personalized variations	Medium	No	No
	Given the personalized variations list of a Manual Collection When the user opens the elipsis menu of the first variation of the list Then the Prioritize option of the elipsis menu is disabled	Medium	Yes	No
	Given the personalized variations list of a Manual Collection When the user opens the elipsis menu of the last variation of the list Then the Deprioritize option of the elipsis menu is disabled	Medium	Yes	No
	Given the personalized variations list of a Dynamic Collection When the user opens the elipsis menu of a variation Then the options Prioritize, Deprioritize and Delete appear in the menu	Medium	Yes	No
	Given the personalized variations list of a Dynamic Collection When the user opens the elipsis menu of a variation and clicks on Prioritize Then the variation name is moved upwards in the list of personalized variations (unless is the first variation of the list)	Medium	Yes	No
	Given the personalized variations list of a Dynamic Collection When the user opens the elipsis menu of a variation and clicks on Deprioritize Then the variation name is moved downwards in the list of personalized variations (unless is the last variation of the list)	Medium	No	No
	Given the personalized variations list of a Dynamic Collection When the user opens the elipsis menu of a variation and clicks on Delete Then the variation name is removed from the list of personalized variations	Medium	No	No
	Given the personalized variations list of a Dynamic Collection When the user opens the elipsis menu of the first variation of the list Then the Prioritize option of the elipsis menu is disabled	Medium	No	No
	Given the personalized variations list of a Dynamic Collection When the user opens the elipsis menu of the last variation of the list Then the Deprioritize option of the elipsis menu is disabled	Medium	No	No

Note.- Check the table where prioritization is saved.

Also review wether the variations order is affecting the prioritization when Collection is used (see LPS-141797)

Upgrade path

As customers coming from previous versions will have variations ordered top-down (Anyone, CV1, CV2), we need their collections to be reordered so the position of collections gets inverted (CV2, CV1, Anyone).

 

Enable FF

 echo "enabled=B\"true\"" > ../bundles/osgi/configs/com.liferay.asset.list.web.internal.configuration.FFCollectionsVariationsPrioritizationConfiguration.config