Do not want Change Record impact field to show default value

[Arijit Saikia]

Hi,

For the Change table [change_request] I have a requirement to disable default value (currently default) for the 'impact' field.

I tried creating a dictionary override by making the default value blank.

It does not work [when I create new Change, the 'impact value now is 'High'].When I inspect the Choice List specification, the "Choice = Dropdown without - None --must specify a value" is causing the issue.

As the 'impact' field is inherited from the task table , and I make any changes to the Choice List specification, it will impact other tables e.g Incident which also uses the 'impact' field.

Please advise.

Refer to screenshots

[GopikaP · Accepted solution]

Hi @Arijit Saikia , so you want to keep the impact field empty while creation only? not after that? So, you don't need an extra choice for the field? Then this onLoad is okay, but test thoroughly to make sure it is not affecting your existing change flows.

[GopikaP]

Hi @Arijit Saikia You can try the following -

• Right click the 'impact' field in change_request table and and select 'Configure Choices'\
• Select Apply to Table as 'Change Request'
• And in your dictionary override, give the default value - the same value you had given in 'Numeric Value here.
• This won't affect other tables that extend 'Task' - 

[Arijit Saikia]

Is it a good idea to create a onLoad client script?

function onLoad() {
// Check if the record is new (i.e., the Sys ID is empty or undefined)
if (g_form.isNewRecord()) {
// Set the Impact field to blank
g_form.setValue('impact', '');
}
}

[GopikaP · Accepted solution]

Hi @Arijit Saikia , so you want to keep the impact field empty while creation only? not after that? So, you don't need an extra choice for the field? Then this onLoad is okay, but test thoroughly to make sure it is not affecting your existing change flows.

[Dr Atul G- LNG]

Hi @Arijit Saikia 

Did you check this earlier or not, on change impact value comes from risk conditions. So soon as the change form is loaded in the backend the risk conditions run and populate the impact. Please check that logic once well and share feedback.