State Changes when Active is set to False for a scoped application

[Arijit Saikia]

I have a scoped application with a table that extends the task table. The state field is inherited from task table but I have created my own choices [Choice and Numeric Values] -

Open   1,

Work in progress 2,

Pending 3,

Resolved 5,

Closed complete  7

Closed Incomplete  8

When I mark the Active state to false the state automatically changes to pending. 

[Viraj Hudlikar · Accepted solution]

Hello @Arijit Saikia 

Look for any business rules that might be affecting the state field. Specifically, check if there is a rule that sets the state to "Pending" when the Active field is set to false. The "Task Active State Management" business rule is a common one that might be involved.

And I firmly believe this is due to OOTB BR [Task Active State Management] only which is working for your extended table and since the state even being newly created where pending is 3 while ootb is closed complete either redesign choices aligning with ootb choices, so your process logic is not affected rather than configuring ootb BR.

If my response has helped you hit helpful button and if your concern is solved do mark my response as correct.

Thanks & Regards
Viraj Hudlikar.

[Arijit Saikia]

Thanks Viraj. I changed the values to realign with OOTB State choice values matching the task table. Works fine now.

[robertoalva]

Since your table extends task, it inherits the default task state behavior.

To resolve this, you should override the dictionary attributes for the state field in your table:

1. Go to System Definition > Dictionary and open the state field for your table.
2. Create a Dictionary Override for your specific table.
3. Check Override attributes and add the following:
   • default_close_state=7 (or the correct value for your Closed Complete state)
   • close_states=7;8 (listing all valid close states)
   • ignore_filter_on_new=true (this ensures the filter is ignored when creating new records, avoiding any automatic changes to state based on filters)
4. Save the changes and test again.

[ralvarez]

Since your table extends the task table, it inherits the default task state behavior.

Checking Business Rules is not the best approach in this case, since the issue is related to the dictionary configuration rather than business rule logic.

To resolve this, you should override the dictionary attributes for the state field in your table. 

1. Go to System Definition > Dictionary and open the state field for your table.
2. Create a Dictionary Override for your specific table.
3. Check Override attributes and add the following:
   • default_close_state=7 (or the correct value for your Closed Complete state)
   • close_states=7;8 (listing all valid close states)
   • ignore_filter_on_new=true (this ensures the filter is ignored when creating new records, avoiding any automatic changes to state based on filters)
4. Save the changes and test again.

Note: I apologize for not being able to edit or delete my previous message with my other account. Thank you for your understanding.