Visual Task board gives a UI Policy error when used

[nomemon]

We have recently upgraded to Fuji Patch 6 on our non-prod environment

Not sure if others are facing this issue, but when our admins and ITIL users use the visual task board to change priorities on incidents, or re-assign incidents to different members of the same assignment group, or change states on an incident - we get an error 'A UI Policy has prevented you from making a change', and it does not work.

Is there something else we need to do in order to allow users use the Visual task board as intended?

Thanks!

[kopp820]

Hi Nomaan - UI Policies are applied to Visual Task Boards in addition to the form itself. Priority is read only since it's driven by a matrix of Impact X Urgency. You would not want someone to override that.

I assume you have other UI policies which are making assigned to and state read only as well.

First I would understand the use case behind why those were set to read only, and then evaluate whether you should update those policies or not.

You can check your UI policies here:

https://[your instance].service-now.com/sys_ui_policy_list.do?sysparm_query=table%3Dincident%5EORtab...

[Paul Curwen]

I have came across the same issue. The 'A UI Policy has prevented you from making a change' message makes no sense to an end user. I've put in an enhancement request to improve thew wording something like Form validation restrictions have prevented movement of this VTB card. It would then be useful if it left an information or warning entry in the logs so you could easily track sown the culprit.

[Sudhakara Redd2]

Make sure there is no mandatory field while assign the values.

Example: If you want to change the assignment group but worknotes are mandatory in normal cases. If that is the case, you can use visual board.
If any field is not mandatory while changing the assignment group, it will not through any error.

[Abhishek Raj3]

HI Nomaan,

Its a Known issue in Fuji Patch 6 and till now this issue has not been resolved in any of the upgrade.

I have the same issue and we raise a hi ticket for same and they told still they are working on the problem ticket once they got any workaround/update will let you know.

Thanks,

Abhishek