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

UI Policy not working on Catalog Task's Requested_for field which is extended from Request table.

Meenal Gharat
Tera Guru

Hi All,

How can I make Requested_for field editable on Catalog task?

Requested_for field is extended from Request table which is editable on Request table I want to make it editable on Catalog task.

PS : Checked Dictionary and Read Only is unchecked.

Also, checked UI policy and client script on Catalog task and No conflicts I can see.

 

What can be the possible errors ?

 

Thanks and Regards,

Meenal

1 ACCEPTED SOLUTION

Hi,

Ok. I have a solution, so follow along:

Firstly, the dot-walked field for "Requested for" on sc_task seems to have be the requested item's...requested for field which itself...is a dot-walk from request...see below screenshot from Configure > Form Layout:

find_real_file.png

So...you'd want to swap this out and dot-walk from Request table and use that Requested For field.

Once you've made that change. Right-click gray header bar in sc_task record and go to "Configure > Dictionary":

find_real_file.png

Now...from here, you'll see a list of columns that say stuff like "Table, Column name, Type", etc. Click the gear icon to add the "Read only" column to this list view:

find_real_file.png

Now...look for the line item talking about request and you'll see that the Read only setting for this is "true" change it to "false" then go back to your sc_task record and voila...Requested for is now editable.

For fun...I left the original Requested for that was there (that I mentioned in the beginning of my post) and that is still read-only, but the one we added is not...which is why I had you do that 😉

find_real_file.png

https://hi.service-now.com/kb_view.do?sysparm_article=KB0687623

Please mark reply as Helpful/Correct. Thanks!


Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

View solution in original post

13 REPLIES 13

Xavier Cordero
Kilo Sage

Hello Meenal,

There are more places where the issue could be coming from (some of them below).

  • Check the sc_task ACLs to make sure that there aren't ACLs against the table for that field.
  • Check the Data Policies for the sc_task table.

 

Please let me know if none of the above were the issue, so that we can continue to troubleshoot.

Hi Xavier,

 

I checked and found that there are No data policies for sc_task.

Also checked ACL for read and write requested for field it is for users with the public role.

Still I ain't able to make requested_for field editable.

 

 

Thanks and Regards,

Meenal Gharat

Hi,

Ok. I have a solution, so follow along:

Firstly, the dot-walked field for "Requested for" on sc_task seems to have be the requested item's...requested for field which itself...is a dot-walk from request...see below screenshot from Configure > Form Layout:

find_real_file.png

So...you'd want to swap this out and dot-walk from Request table and use that Requested For field.

Once you've made that change. Right-click gray header bar in sc_task record and go to "Configure > Dictionary":

find_real_file.png

Now...from here, you'll see a list of columns that say stuff like "Table, Column name, Type", etc. Click the gear icon to add the "Read only" column to this list view:

find_real_file.png

Now...look for the line item talking about request and you'll see that the Read only setting for this is "true" change it to "false" then go back to your sc_task record and voila...Requested for is now editable.

For fun...I left the original Requested for that was there (that I mentioned in the beginning of my post) and that is still read-only, but the one we added is not...which is why I had you do that 😉

find_real_file.png

https://hi.service-now.com/kb_view.do?sysparm_article=KB0687623

Please mark reply as Helpful/Correct. Thanks!


Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

Hi Allen,

 

Thank You for the suggestion.

I will check and get back to you.

 

Thanks and Regards,

Meenal