Getting Error UI Policy Voilation when assigning task or incident from taskboard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-08-2020 12:15 AM
Getting Error UI Policy Voilation when assigning task or incident from taskboard
- Labels:
-
User Interface (UI)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-08-2020 12:22 AM
Hi Surabhi,
UI Policy Violation error is because there are some UI policies written on that field, try to find that UI policy then the issue will be fixed.
Navigate to that table and find the UI policies of that field.
If you try to perform some actions on visual task board which has UI policy written on that field then this kind of error will be displayed.
Thank you.
Hope this is Helpful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-08-2020 12:54 AM
Hi Harish,
VBT is running on task table and there is other task board also running on same table but no error is coming for this taskboard.
Both task board have same configuration but in one error is coming and for other no error is coming
Regards,
Surabhi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-08-2020 02:45 AM
Hi Surabhi,
Please disable some UI policies which are configured on the field you are facing the error.
Then you can find out why it is causing the error.
Mandatory fields should need to be filled in the records, then only you will not face this error in VTB dasboards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-01-2021 01:10 PM
You also may find that the issue is rooted in KB0821210.
If a field is not present on a form, and that field has a UI Policy that makes the field mandatory, this UI Policy will not run on the form because the field is not present on the form.
But this UI Policy is being evaluated on the Task Board.
This issue is at least three years old and it amazes me that SN has failed to fix this problem.