I am trying to make the Engagement field on the sn_vdr_risk_asmt table non-mandatory. However, the field continues to be enforced as mandatory, and I have been unable to identify the source of this behavior.
To troubleshoot, I have already performed the following:
- Reviewed Clien Script Policies
- Checked UI Policies
- Checked Data Policies
- Used Session Debug to trace field behavior
- Tested changes in policy order and precedence
- Evaluated potential Client Script impacts
Despite these efforts, none of the above appear to be responsible for setting the field as mandatory, and Session Debug does not indicate the source of the mandatory enforcement.
I am specifically looking to understand how this field is being marked mandatory out of the box or through platform logic, rather than suggestions such as creating additional UI Policies, Client Scripts, or adjusting execution order, as those approaches have already been explored.
Has anyone encountered this behavior on sn_vdr_risk_asmt or identified whether the mandatory state is being enforced through:
- Dictionary attributes - checked it , mandatory is false here
- Workspace Form Rules - NA as this is happening in native UI
- Scripted APIs
- Vendor Risk Management application logic
- Any other framework-level enforcement mechanism
Any insights into where this mandatory setting originates would be greatly appreciated.
@Pradeep Sharma
