Task not being set as Inactive

[guiguille]

Hey guys,

I'm having a strange issue in my instance. I have created a new table extending from task. I created new state choices, but I kept the values to avoid messing with the closed states. In this case, I have two states that need to set the ticket as inactive, and those are Closed (3) and Canceled (7). These are two of the values that when they are set, the task should be set as Inactive.

I'm moving from a previous state to Closed in a workflow activity. When I do this, I see that the "Task Active State Management" is skipped, because the BR doesn't recognize that the state is changing. When debugging, it seems that the state is getting updated later, and the BR doesn't "get" the state modification.

As a workaround, I added a 2 seconds timer in the workflow, and when I do that, the task is set as inactive.

This is the workflow with the workaround. When I run the workflow without the timer, the task never gets set as inactive. The thing is that I don't want to leave the timer there, because it's a mess for the users, the page is refreshed and the values are not modified yet, I'd like to avoid that.

Any ideas?

Thanks!

[SanjivMeher]

I am not sure, why it is skipping the BR. But you can add few logs to check, whats going on in that BR. Remove the conditions and add few gs.log or gs.print statements.

Also if that doesnt work, what if you set both State and Active flag in the workflow in the setValues box.

[guiguille]

Hey Sanjiv,

The issue is that the state update comes after the BR, can't understand why. I'll do what you said as a workaround, setting the active state is more user friendly.

Thanks!