Add a warning on the role assignment by segment when the option is disabled

• Type: Bug
• Status: Closed
• Resolution: Completed
• Affects Version/s: 7.2.X, 7.3.10 DXP GA1, Master
• Fix Version/s: 7.2.10 DXP FP10, 7.2.10.4 DXP SP4, 7.2.X, 7.3.10 DXP FP1, 7.3.10.1 DXP SP1, 7.3.6 CE GA7, 7.3.X, Master
• Component/s: Segments Editor
• Labels:
  • ee-ts
  • fc_20_11
  • liferay-dxp-72-sp4
  • liferay-dxp-73-sp1
  • liferay-fixpack-dxp-1-7310
  • liferay-fixpack-dxp-10-7210
• Branch Version/s:
  7.3.x, 7.2.x
• Backported to Branch:
  Committed
• Epic Link: tango-segmentation-performance
• Sprint: TANGO | #48 DEV | Oct31-Nov13, TANGO | #49 DEV | Nov13-Nov27, TANGO | #50 DEV | Nov27-Dec11
• Git Pull Request: https://github.com/liferay-tango/liferay-portal/pull/529 https://github.com/liferay-tango/liferay-portal/pull/593

Motivation

As we are disabling the Assign Roles by segment by default, we have to warn users in the role configuration screen that this kind of assignment won't work.

Design

https://www.figma.com/file/DIJlCFD8omCFhHAmqXpPwf/LPS-121943-disable-assigning-roles-to-user-segments?node-id=29%3A6051 

Technical Requirements

• A message will show in the role configuration screen > Segments tab when the Assign Roles by segment option is disabled: **Assigning roles by segment is disabled. To enable Assign Roles by segment go to System Settings.
  • Ideally "System settings" will be a link to System Settings > Segments > Segments Service tab.
  • If this is not possible, we'll include the breadcrumb: Assigning roles by segment is disabled. To enable Assign Roles by segment go to System Settings > Segments > Segments Service
• Users may still add segments to the list by using the "+" button, but assigning won't be accomplished.
• If the user enables the Assign Roles by segment option, then the role will be assigned to all the segments already on the list
• Bulk options existing on this screen will be still available when the Assign Roles by segment option is disabled.

Acceptance Criteria

• Given the Segments tab in the role assignment screen
• When the Assign Roles by segment option is disabled
• Then a message will show: Assigning roles by segment is disabled. To enable Assign Roles by segment go to System Settings > Segments > Segments Service

--

• Given the Segments tab in the role assignment screen
• When the Assign Roles by segment option is disabled and the user adds segments to the list
• Then it won't work until the Assign Roles by segment option is enabled

Test Scenarios

AC ID	Test Strategy	Test Scenarios	Is it covered by FrontEnd ? (JS-Unit)	Is it covered by BackEnd? (unit or integration)	Poshi?
01	Low	When the user accesses System Settings > Segments > Segments Service, the Enable Segmentation option will be enabled and the option Enable Assign roles by segment will be disabled by default	NO
02	Lowest	When the user accesses System Settings > Segments > Segments Service, above the Enable Segmentation option the following text will appear: "Disable this option to prevent user segmentation on every request. If disabled, collections and experiences personalization will not be available."	NO	NO
03	Lowest	When the user accesses System Settings > Segments > Segments Service, above the Enable Segmentation option the following text will appear: "When checked, this option allows assigning roles to users dynamically."	NO	NO
04	Medium	When the Enable Assign roles by segment option is disabled and the user accesses the Segments tab in the role assignment screen, a message will show: "Warning: Assigning roles by segment is disabled. To enable, go to System Settings > Segments > Segments Service."	NO	NO
05	Critical	When the Enable Assign roles by segment option is disabled when the user accesses the Segments tab in the role assignment screen, the user may still add segments to the list by using the "+" button, but assigning won't be accomplished	NO	NO
06	Medium	When the Enable Assign roles by segment option is enabled and the user accesses the Segments tab in the role assignment screen, no warning message is shown and the assigning will be accomplished	NO	NO

Frontend coverage is all NO because the code is in JSP files.