Change request is moving to close status when active change to false

[tbenbenisti]

Hello,

We created a new custom state for the change request record called "Rolled Back", and the active field should change to active = false once the user clicks on the "Roll Back" ui action.

Once the active field is changed to false, the state is overridden to "closed" and ignores my state population to "Rolled Back".

Any idea what causes this behavior?

[Its_Azar]

Hi there @tbenbenisti 

When active = false on a Change Req, the platform usually forces the record into a closed state automatically, which is why your custom “Rolled Back” state gets overridden.

I’d check:

• Business Rules on change_request
• TaskStateUtil / change state handler scripts
• close state mappings for the state field

Most likely your custom state just isn’t configured as a valid close state yet.