Description Field Not Showing as Mandatory in SOW View for Standard Change – Need Help

[lakshmi9]

• I’m working on a requirement where the Description field should be mandatory for Standard Change Requests, but only when the State is 'New' and the view is SOW.
• I tried implementing this using a UI Policy, but it didn’t work in the SOW view. I then attempted it using a client Script, and it works fine in the Default view, but not in SOW.
• The field is present in the SOW form layout, so I’m not sure why the mandatory condition isn’t being applied.

If anyone has faced a similar issue or could kindly guide me on how to achieve this, I’d really appreciate your help.

[SD_Chandan · Accepted solution]

Hi @lakshmi9 ,

Please check and confirm if you have selected for a specific view
because it will work.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer

[SD_Chandan · Accepted solution]

Hi @lakshmi9 ,

it is directly coming from template that's why is is not appearing mandatory.

[lakshmi9]

Hi @Pradeep Thipani 

 I also checked the Details tab, and it is showing the same behavior — the field is not mandatory.

I have created a UI Policy with the following conditions:

• State is New

• Type is Standard

In the UI Policy Actions, I’ve set the Description field to be mandatory. It's not working so i have created on load script then it's showing mandatory in default view but not sow view.

[SD_Chandan]

Hi @lakshmi9 ,

Use a UI Policy scoped to the SOW view, with conditions: type is standard change and state is new

In the UI Policy Actions, set Description as mandatory

Hope this works 

[lakshmi9]

Hi @SD_Chandan 

I have tried that method also. showing same behavior.

[SD_Chandan · Accepted solution]

Hi @lakshmi9 ,

Please check and confirm if you have selected for a specific view
because it will work.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer

[lakshmi9]

Hi @SD_Chandan 

• I’m trying to make the Description field mandatory only for Standard Change requests when in the "New" state, specifically in the Standard Operating Workspace (SOW).
• I’ve already implemented the logic, and it's working fine for Normal and Emergency change types in SOW. However, for Standard Change, the field is not showing as mandatory in the same view/state.

Also, could you please let me know if it's working for Standard Change in SOW on your instance?