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.

[tbenbenisti]

Hi @Its_Azar,

Thank you for your reply.

I deactivated two business rules on the task table; there is no business rule on the change request table that runs the TaskStateUtil.

* task closer

* Task Active State Management

I will check it more, but it seems to be helpful

[tbenbenisti]

I think it's the task closer business rule since it's happening even without state changes, for example, when I'm changing the active from true to false directly from the list view.

OOB BR (Task Active State Management) has a condition for state changes

[Tanushree Maiti]

Hi @tbenbenisti 

Can you elaborate your business justification for adding Roll back UI action. 

As per your requirement "active field should change to active = false once the user clicks on the "Roll Back" ui action" , what you require, OOB Close UI Action typically does the same and terminates a process normally.

At backend, there is OOB BR (Task Active State Management) in place which check close state and mark Active is false.

Link of BR : https://<your_instance_name>/now/nav/ui/classic/params/target/sys_script.do%3Fsys_id%3D9782b8dac0a80...