Request for variable Showing empty in SC TASK List View

[Dileep Raju]

Hi Team
In my instance " Request for variable Showing empty in SC TASK List View. "

Can some explain me why it is happing and also What I need to do for Request For Variable in order to fill after submission of Ticket

[Anks26 · Accepted solution]

Hi Dileep, 

There could be few reasons why this could be happening, as there is an historical issue with ServiceNow request in my experience and tricky to explain.

There is a "requested_for" field on sc_request and a "requested_for" on RITM/Task, make sure you are displaying the right one on the list view. 

Previously, in your catalogue variables, you would use would ask "who is this request for" using reference "sys_user" table which would set "sc_request" requested for but not RITM requested for and different organisation handled it differently. i.e. using BR/workflow to keep them in sync but the ServiceNow introduced a "requested_for" variable type 
which fixed this issue. Not sure what variable you are using so try updating it to this type and it may fix the issue. 

 

 

Let me know if you have any other questions. As I said it's a little hard to explain. 🙂

Thanks

Anks

[Dileep Raju]

@priyasunku 
Thank you so Much
Could you help me how to check It is custom or OOB and Also
If Possible Please provide me for custom and OOB Requested for Field is empty. What we need to do ?

[priyasunku · Accepted solution]

please share screenshot I can help you then.

if you want to check OOB or custom. you have to do right click on the field and  check what is the backend name.

if the field name doesnt contain u_ then it is OOB.

If my answer solved your issue, please mark my answer as ✅Correct & 👍Helpful

[Dileep Raju]

@priyasunku 
Thank you so much for information

It is a OOB

[priyasunku]

@Dileep Raju  you are not sharing screenshot and i dont know to which table that fields belongs to as well.

so can you try below code in business rule after insert

current.requested_for= current.request_item.request.requested_for;

If my answer solved your issue, please mark my answer as ✅Correct & 👍Helpful