Adding a new Choice to State on HR Case table that will be considered Inactive

[kareng]

We added a new Choice to State in the dictionary for HR Case and made it a value greater than 8 (Closed).  Based on reading DOCS it should have made this choice an Inactive State.  That is not the case.  Not sure how to make that State as Inactive so that is does not show up on the list of active cases.  Suggestions?

[Kiel Sanders]

Hi Karen

The best way to define your new custom state as inactive is to modify the closed_states attribute on the state field.  The steps below should help you configure this.

1. Navigate to the HR Case table.  Right click the State field and click Configure Dictionary.
2. Since the state field is extended from Task, you will want to see modify the attribute specific to the HR Case table.  Scroll down to the Dictionary Overrides related list and open the record for sn_hr_core_case (or whatever case table the new status was added to).
3. Modify the attributes field to include the numeric value associated to the new state you added.  This should be a semi-colon separated value under close_states.  The example below adds the status value of 49 to the list of inactive statuses associated to this table.
   

The TaskStateUtils documentation explains how this works at a more technical level.

[kareng]

Kiel,

Very useful info- thanks.

I added the State to the sn_hr_core_case Dictionary Override Attributes.  In testing it, a the case was moved to Inactive but it changed the State to what appears to be the default_close_state of 3 -Closed Complete. I want it to remain as the chosen state of Withdrawn (26) .

Would this happen if the state was not defined in the Task table (since we put it in the HR Case table)? Here is what the attribute looks like now:

[Kiel Sanders]

The "task closer" business rule is likely what is overriding this but I recommend submitting a HI incident to investigate and confirm.