Project

General

Profile

Actions
Copy link

Bug #11504

closed

product-uem 7.0.0 GA - Task #11893: Improvements For Policy UI

Regex validation in policy UI does not stop the user from policy creation

Added by Oshani Silva 10 months ago. Updated about 1 month ago.

Status:
Closed
Priority:
High
Assignee:
Sathira Perera
Start date:
21/01/2025
Due date:
22/01/2025
% Done:

100%

Estimated time:
Device Type:
Component:
Type:
UI

Description

When checking any policy items which has a regex validation even-though the issue is highlighted in red it does not stop the user from continuing the policy creation. Hence the user can create policies with invalid payload if message shown is not taken into account.

Expected behavior

Once the user enters a value which is invalidated by the regex the continue button should be disabled till the proper value is inserted.

Files

Download all files
clipboard-202409091252-n5vmj.png (14.4 KB) clipboard-202409091252-n5vmj.png Oshani Silva, 09/09/2024 07:22 AM
clipboard-202409091252-zomqa.png (32.4 KB) clipboard-202409091252-zomqa.png Oshani Silva, 09/09/2024 07:22 AM
Screenshot from 2025-03-31 08-51-13.png (90.6 KB) Screenshot from 2025-03-31 08-51-13.png Arshana Atapattu, 31/03/2025 03:21 AM
Actions
Copy link
 #1

Updated by Oshani Silva 8 months ago

  • Due date set to 21/10/2024
  • Assignee set to Oshani Silva
  • Priority changed from Medium to High
  • Start date changed from 08/07/2024 to 17/10/2024
  • Parent task set to #11893
  • Type set to UI

When checking any policy items which has a regex validation even-though the issue is highlighted in red it does not stop the user from continuing the policy creation. Hence the user can create policies with invalid payload if message shown is not taken into account.

Expected behavior

Once the user enters a value which is invalidated by the regex the continue button should be disabled till the proper value is inserted.

This seems to be specifically happening only items added to Custom Table Component

Actions
Copy link
 #3

Updated by Oshani Silva 5 months ago

  • Project changed from product-uem 7.0.0 GA to product-uem 7.1.0 GA
Actions
Copy link
 #4

Updated by Oshani Silva 4 months ago

  • Project changed from product-uem 7.1.0 GA to product-uem 7.0.0 GA
  • Due date changed from 21/10/2024 to 22/01/2025
  • Assignee changed from Oshani Silva to Sathira Perera
  • Start date changed from 17/10/2024 to 21/01/2025
Actions
Copy link
 #5

Updated by Sathira Perera 3 months ago

  • Status changed from New to Implementation
  • % Done changed from 0 to 80
Actions
Copy link
 #6

Updated by Sathira Perera 3 months ago

  • % Done changed from 80 to 90
Actions
Copy link
 #8

Updated by Sathira Perera 3 months ago

  • % Done changed from 90 to 100
Actions
Copy link
 #9

Updated by Arshana Atapattu 3 months ago

  • Project changed from product-uem 7.0.0 GA to product-uem 6.4.0 GA
Actions
Copy link
 #10

Updated by Sathira Perera 2 months ago

  • Status changed from Implementation to QA
Actions
Copy link
 #11

Updated by Arshana Atapattu about 1 month ago

Not working

Actions
Copy link
 #12

Updated by Sathira Perera about 1 month ago

  • Status changed from QA Reject to QA
To test this, it is possible to test the following fields:
Under Android:
  • App restriction settings: Give a negative value for Maximum limit.
  • Access point name: For name, give a value with more than 100 characters.
Under Windows:
Actions
Copy link
 #13

Updated by Arshana Atapattu about 1 month ago

  • Status changed from QA to QA Accept

Fixes are working

Actions
Copy link
 #14

Updated by Arshana Atapattu about 1 month ago

  • Status changed from QA Accept to Closed

Closing due to QA accept

Actions
Copy link

Also available in: Atom PDF