The CreatorCon Call for Content is officially open! Get started here.

Field State Validation - FAILURE: Expected field 'number' to be read only but it was not read only. See screenshot

mikecole
Tera Contributor

While impersonating a member of the Help Desk, the 'number' field which is read only is being perceived by automated testing to not be read only.

FAILURE: Expected field 'number' to be read only but it was not read only. See screenshot
FAILURE: Expected field 'opened_at' to be read only but it was not read only. See screenshot
FAILURE: Expected field 'opened_by' to be read only but it was not read only. See screenshot
FAILURE: Expected field 'number' to be visible but it was not visible. See screenshot
FAILURE: Expected field 'opened_by' to be visible but it was not visible. See screenshot

 

6 REPLIES 6

shivanipatel
ServiceNow Employee
ServiceNow Employee

Hey Michael,



We are glad you took advantage of the ServiceNow Community to learn more and to get your questions answered. The Customer Experience Team is working hard to ensure that the Community experience is most optimal for our customers.



If you were not able to receive the answer you hoped for but you do believe that you received clarity in terms of how to proceed, we would greatly appreciate if you could mark the appropriate thread as "Correct Answer". This improves the ServiceNow Community experience.



If you are viewing this from the Community inbox you will not see the correct answer button.   If so, please review How to Mark Answers Correct From Inbox View.



Thanks!


Shivani Patel


Unknown-1.png


mikecole
Tera Contributor

Roger Marquez (NOW)

2017-06-20 14:27:46


29d ago


Hi Michael, After looking into this, it appears that you are running into a known issue, which I am associating with this incident: -- PRB689175: g_form.isReadOnly does not work for most fields when marked read only on their dictionary record For your reference, here is the corresponding Known Error article: -- https://hi.service-now.com/kb_view.do?sysparm_article=KB0622815 This issue is under review and we will update this incident as more information becomes available regarding a fix or workaround. I'll also mark this ticket as Pending Problem. Please let us know if you have any questions about this.