We've found a possible functionality hole which we'd appreciate being reviewed and potentially updated by yourselves if it's not already possible to achieve with the current product.  We're using SC+ 7936 on MSSQL 2012 and Windows 2008R2.

  We've recently discovered that, whilst we have a number of Mandatory incident properties set in our system, these can effectively be bypassed when Support Reps use the inline field-by-field editing feature.  When this is done, SC+ allows users to change the value of individual and linked fields, correctly checking that those specific fields are populated if they're mandatory, however it doesn't then cross-check any other fields.

  This means that, for example, an incident can be assigned to a Support Rep by changing that field, however the priority need not be set even though it's a mandatory property and critical to our workflow and SLA adherence.

  Any thoughts of what we could do and whether or not you'd be able to trigger a full-property mandatory check under these circumstances would be much appreciated.

Kind regards,

  Andy