State Field showing incorrect State

Mudit4
Kilo Expert

I have defined a Change Model consisting of:

Scheduled ->Implement, Pending Customer

Pending Customer-> Scheduled, Implement

Implement-> Review, Pending Customer

When I transition my change request into Pending Customer State, The state field shows 'Scheduled'. On checking the state in the List of change requests, the state is Pending Customer. Also, when the request is first loaded it shows Pending customer but Changes to 'Scheduled'

What is happening. I know the request is in pending state but why does the state value change to Scheduled.

find_real_file.png

But on opening-> State value initially is Pending but switches to "scheduled" on loading

find_real_file.png

1 ACCEPTED SOLUTION

Yes it is a custom state. I created it by following the same documentation you mentioned. I still dont know why the problem occured. But somehow it got resolved over the weekend without me making any changes

View solution in original post

14 REPLIES 14

Hello,

Can you share the change modal screenshot of the transition state similar to below:-

find_real_file.png

Hi Saurav,

Here is the Screenshot you requested.

find_real_file.png

Also I think the default value '1' was for all choices in Task table. The override for change_request table is '-5'

Hello,

Can you open the scheduled and Pending option and choose me what is configured inside:-

find_real_file.png

Also is the pending state a custom state? Did you follow all the steps mentioned don the below article

https://docs.servicenow.com/bundle/sandiego-it-service-management/page/product/change-management/task/t_AddANewState.html

Please mark answer correct/helpful based on impact.

Hi Saurav,

I dont know why or how but the state value is now showing the correct value! I did not make any changes though.

 

 

hello,

No what I am asking is Pending Customer an custom state? Because I cannot see it in my PDI ? So if it was an custom state I think there have been some issue when implementing it because of which this issue is occuring.

Please mark answer correct/helpful based on impact.