Change Request State Set to Closed Completely After Task is Completed

[Community Alums]

I'm having an issue with the Change Request state getting set to 'Closed Completely' after the a task is done in the workflow. There is a Create Task - Implement activity in the workflow and when that task is complete, there is a Wait for condition - Wait for Final Review that waits for a custom field called Final Review to be filled out. Does anyone know what might be causing this as I checked the workflow and business rules but can't see what would be causing this issue.

Thanks,

Aryanos

[ohhgr]

Hi Aryanos,

Did you check business rules on the change_task table? If the change request state is getting changed on closure of change task, a business rule on the change task might be causing it.

Hope that helps.

-Mandar

[Community Alums]

Hi Mandar,

I looked at the business rules for change_task and change_request and there is Closed Ticket and marked_closed.

marked_closed has the code but even when I disable the rule the workflow does the same thing

if (current.state > 2) {

current.active = false;

}

Closed Ticket has the condition current.state.changes() && (current.state == 3 || current.state ==4)

and the script below but it still closed the CR when I made it inactive. I have now idea what would be causing this issue.

current.active = false;

current.work_end = nowDateTime();

current.business_duration = gs.calDateDiff(current.work_start.getDisplayValue(),current.work_end.getDisplayValue(),false);

current.calendar_stc = gs.dateDiff(current.work_start.getDisplayValue(),current.work_end.getDisplayValue(),true);

[ohhgr]

Hi Aryanos,

Have you been able to find out the issue? One thing, once the task is closed, are you changing the state of the change request?

There is one business rule "mark_closed" on change_request, that by default closes the change request if the state is greater than "2".

Thanks,

Mandar

[Community Alums]

It isn't the marked_closed rule because even if I disable it and try again it closes the state to Closed Completely so there is something else. We have custom states and change the states in our CR workflow so my workaround was to make our custom states negative and that fixed it. Thanks for the help though.