All Collections are mixed if the setting to "Combine Assets from All Segments in Asset Publisher for Dynamic Collections" is enabled

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.4.13 DXP U17, Master
• Fix Version/s: 7.3.10 DXP U18, 7.3.X, 7.4.3.35 CE GA35, 7.4.13 DXP U35, 7.4.3.36 CE GA36, Master
• Component/s: Collections > Collections Personalization
• Labels:
  • 7.3.10-u18
  • 7.4.13-u32
  • backend_test
  • ee-ts
  • liferay-fixpack-dxp-18-7310
  • liferay-update-update-dxp-18-7310
• Branch Version/s:
  7.3.x
• Backported to Branch:
  Committed
• Fix Priority: 3
• Sprint: TANGO | #75 DEV | Mar18-Apr18, TANGO | #79 DEV | Jun20-Jul04, TANGO | #80 DEV | Jul05-Jul18, TANGO | #81 DEV | Jul18-Aug01
• Git Pull Request: https://github.com/liferay-tango/liferay-portal/pull/2619
• Bug Type: UX / Visual - Desktop

Activating the setting of "Combine Assets from All Segments in Asset Publisher for Dynamic Collections" is mixing all Contents from all existing collections in Asset Publishers mapped to a collection.

 

Steps to reproduce

1. Create a new Structure with some fields. Let's call it Structure 1
2. Create one Content using this new Structure
3. Create another Content using the Basic Web Content Structure
4. Configure a Collection to filter all contents belonging to the Structure 1
5. Configure another Collection to filter all contents belonging to the Basic Web Content structure
6. Create a page and add a Asset Publisher into it and connect it to the first Collection. Publish it
7. Confirm that by default, you only see contents created with the Structure 1
8. Change the setting in System Settings > Assets > Collection: check "Combine Assets from All Segments in Asset Publisher for Dynamic Collections"
9. Refresh the page

Expected result

As we haven't define variations, you still see the same amount of contents: only the one that is based on the structure that is filtered in the Collection and connected in the Asset Publisher

Actual result

You now see two contents: the structured content and the basic web content because with this setting the system is using all collections instead of the configured one in the Asset Publisher. The idea of this setting in theory is to get all variations from the configured collection in the Asset Publisher, but not no mix all Collections

 

Additional Notes

This happens also with Manual Collections and activating the setting for Manual Collections (same place)

To simplify the steps, I am not adding Variations at the Collection Level as it doesn't seem to be needed. But maybe for the Expected results it's better to have some variation and then test that you get more assets when checking the setting.