How to debug the condition in a UI action?

[gjz]

I have an issue with an UI Action and I'm having trouble figuring out how to debug it.  I didn't write the UI action, but I've managed to narrow down the issue to one condition in the UI action, but I'm at a loss on how to determine why it is an issue.

The condition that is not working:

The condition that will work:

The original used to work and I assumed it was an ACL write on the state field, but I've checked and the person who is having the issue passes the ACL write for the state field.

Does anyone have any idea where I should start looking or what might be wrong?  This is a scoped app; I did a code search and the only place "canWrite() is used is in the UI Actions, and all of them are current.state.canWrite()

[gjz]

Thanks Sandeep, Access Analyser found the answer.  According to the analyzer, it said the field was "read only".  The field on the form was just changed to read only, once I removed that the UI action came back.

The reason the field was set as read only on the form is because there is code in the UI Action that controls the value in the state field, the users should not be changing it.  I think changing it to current.canWrite() will work since write access to the table requires the same roles.

[Sandeep Rajput]

@gjz I am glad to know that you managed to find the reason for this behavior. 

[AnirudhKumar]

current.state.canWrite() doesn't make any sense at all.

The canWrite() applies to an object of the record, and not on any specific field. 

It simply shouldn't work😊

[Sandeep Rajput]

@AnirudhKumar It does make sense. canWrite() can be used at field level too. Here is the link to the official documentation. https://developer.servicenow.com/dev.do#!/reference/api/washingtondc/server_legacy/c_GlideElementAPI...

[gjz]

Except that is does, I've seen it in OOB UI Actions.