Adding a new choice in impact field produce problem in change request form.

[Ronald11]

Hello,

I just tried creating a new record in the choice list so that I could have the default 1-High have another display value in the impact field for the change request record.

Did I miss something in the record? I am planning to have different label for each choices and I am just testing first this method. Will these configuration affect risk assessment or the calculate risk UI actions?

[Musab Rasheed]

Hello,

Try changing 'Value' to '5' and see if that works ? if you add like this it will create issues in mapping specially in Look up definitions, check how look up definition is setup for change management

Regards

[Ronald11]

Hello,

After I make the additional choices for others the choices shown is fixed. I just not sure if there will be repercussion down the road even though I make sure that these choices modification is only for the change request table.

Actually I also just followed your advised here:

https://community.servicenow.com/community?id=community_question&sys_id=bcdc80201b885954cd3b33bc1d4b...

Wherein I tried changing the label without changing the value. 

[Musab Rasheed]

See in other thread also I have mentioned you need to check all the places where impact might be referred , specially with addOption() function and check if it is referred in Data look up definition as well, If you are satisfied with all permutation and combination you can go ahead with changes

[Ronald11]

Hello,

After checking for the data look up definitions, I have seen that it is mostly utilized by incident and problem table, and those two table also uses the entry on the priority look up rules, that's why i decided to just create a choice with different label but same value for the change table.