users able to bypass mandatory fields by changing view

[RW-43]

If users open an incident using a view other than 'default' many of the mandatory fields are not displayed and the form does not check for them when resolving the incident.

For example, if an incident is opened using the Self-Service view it can be resolved without entering the Impact, Contact Type, Category, Subcategory, Assignment Group, Resolution Code or Resolution Notes. All of which are mandatory when using the Default view.

The only way around I've put in place so far is a view rule forcing the Default View on all users for this form, however, I can't see that being a solution for all modules.

[RW-43]

That is essentially what I was getting at with the View Rule. Can you accomplish this without a different rule for every form?

[Dave Smith1]

Yes. Set up a data policy to make the fields mandatory, rather than a form.

However, if a mandatory field doesn't show on the form, the form submit will be rejected - hence why it's often done at form level.

Alternatively, as mentioned: restrict accessibility to the views... or ensure every view used has the same controls in place.