State field on scoped application keeps defaulting to Open state when select new choices

[Dazler]

Hi,

I have a custom application that is extended to the task table.  We were asked to add additional choices to the state field for the custom application.  However, when I select the new choice on the form and then save the record it changes the state back to Open.

I set up the dictionary override, but it keeps happening after I save the ticket.  Has anyone ever encountered this within a scope application?  Or how can I fix this?

Any help would be appreciated.

[James Chun]

I would recommend creating a record via background script and seeing what happens to the state. If it changes to 'open' again, it's most likely to be from a server-side script and a BR.

For the server side, try the Script Tracer. - https://docs.servicenow.com/bundle/washingtondc-application-development/page/script/debugging/concep...

For the client side, try the Field Watcher but note that you will need to use the UI16.

https://docs.servicenow.com/bundle/washingtondc-application-development/page/script/debugging/concep...

[Dazler]

@James Chun,

I ran a background script to update the record and it never actually changed the value.  It's almost like my table does not recognize the new choices on that table.  I did run a test and since we are not using the open state, I changed the integer value on the choice list for that new choice (Backlog) to match what open was then it worked.  So it seems to be having trouble with the integer value for my new choices.

Any ideas?

[Dazler]

I figured it out and you were right it was a business rule.  I finally found it.