Matching States in RM_Story table

[terrieb]

So I have created a product in Agile to track progress on updating documents.  I also created new "states" for these that with a UI Policy/Action, will only display if this product is selected.  At the same time, there is another UI Policy/Action that also states if this product is selected, to hide the field of State.

The situation I am experiencing is that if a user of the Agile Board adds the new states field to the column and maintains the normal state field, they don't "match"

All the new states, except for one, shows up as "Draft".  I would like them better align.  I tried matching the values, but that does nothing and I tried changing the sequences, and that does nothing.  

The main issue is that some staff are still using the VTB which only shows the default field of "state" so while I am slowly educating them, some just will do it the other way

Any suggestions?

I would like it to match like this:

State                        Process State

Draft                        Review Process

Ready                       Review Complete

Work in Progress    Director Approval

Work in Progress     Submitted for Signature

Complete                 Completed

Thanks!

[Aoife]

What you are showing here are the Display Values, not the Values.  Choice fields typically have a numeric value that corresponds to the Display Value and this internal value is what ServiceNow is matching on, not the Display Value.

Aoife

[terrieb]

So even if I match the Value it doesn't work - is this because I created a new field to use on the form instead of the default of "state"?  Is there a way to back end link them due to the display issue I described originally?

See attachment

[Aoife]

I assume you are asking if there is a way to associate two different fields on different tables together in the tables themselves.  The answer would be no.

Also, reading your OP again, it sounds like you are allowing users to add new state values to the choice list.  When they do that, they have no control over the value that gets assigned, only the Display Value.  you will never be able to match random data you have no control over to anything.  

Also, if two States have the same internal value, it will randomly select one based on what order SQL returns them in on each table.

There's just so much at play here and I'm afraid it may not be easily doable as it will be a moving target.

You could write code that updates the State field based on your custom field values, but you will have to maintain that code as new values are introduced.  This would be a business rule that fires when the custom field value changes.

Aoife

[terrieb · Accepted solution]

Thanks for the input - seems business rule may be the way to go.

FYI - the fields are on the same table, so not crossing tables.  No, only Admins can add new state values to the choice list.

Thanks again!