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]

Hi @Dazler,

Sorry, it's not clear what the issue is, do you mind sharing some screenshots?

Also, have you tried creating via 'Configure Choices'?

e.g.

Cheers

[Dazler]

Hi @James Chun,

I did use Configure Choices to create the new choices.  The issue is on the form, when I select one of my new state choices (i.e. Backlog option on below screenshot) and then hit the save button, the state field defaults back to Open state.

[James Chun · Accepted solution]

@Dazler - Thanks for sharing that.

Is it possible that you have some client script or a business rule that is changing the 'state' value?

Note that as your table is task extended, make sure you check the parent tables as well.

Since the 'open' option is in a blue colour, there is likely some script that is setting the value of the 'state' to 'open' even if that option is not part of the available list.

Does this happen on a new record only or when you update an existing record as well?

[Dazler]

@James Chun,

It happens on both, but I don't find a client script or business rule that is updating this.  I will have to look again, but I even added a Cancelled choice and it does the same thing.  Is there a log I could see that will show me what business rule or client script runs during that update.