ui policy on list edit

[mrswann]

I just found out about the ability to bulk edit by ctrl+drag!! And realised our teams are using this..

(I always used the header right click , edit selected/edit all - which is restricted to admins so assumed other users had no way to update en masse!)

We learning every day!

However - the UI policy , eg. when moving an Incident to Resolved - is not being honoured via this method of list edit.. ??

So Incidents move to Resolved with no Close Code / Notes etc

I thought this was an easy one but I'm possibly being daft!

I know I can Configure > List Control and restrict the Edit roles ? But I would prefer to just enforce the policy, as opposed to restricting a useful feature!? Any thoughts?

[dvp]

By UI policies you cannot restrict the list operations only way you can restrict is by an ACL list edit operation

[Brad Tilton]

Rather than a ui policy you could use an onCellEdit client script, but dvp's option of using an acl is also a good one.

[Luis Franco]

Hi. 

I was checking some options on this issue because the ui policy is a good way to go for forms but not on the list edit level.

To have database level restrictions you must transform the ui policy into a data policy which is valid at form and at database level but you have less actions available.

Also when testing I found the data policy o be too restrict and yet I haven't used on our processes.

Thank you.

Best regards,

Luis Franco