Please allow for configuration of which fields within an object can be bulk updated. This way, bulk update can honor the fields that are editable in a task view.
Please do not force update/selection of controller fields. I understand why you would be forced to update dependent fields if you are bulk updating controller fields, but it does not make sense that when bulk updating a dependent field, you need to update a controller field. For example, on risks, our users need to select an Action, "Accept", "Mitigate", "Transfer" or "Avoid". The actions they have available are dependent on the Risk Ranking on the risk. For example, Accept is not available if the Risk Ranking is High. It makes sense that if you bulk updated the Risk Ranking, you would need to clear out or bulk update the Actions, since they might not be valid for the updated controller Risk Ranking field. However, if you are bulk updating the Action to mark risks as "Mitigate", you should not need to update the Controller Risk Ranking field (which, like many Controller fields, is a read only field in the Risk Task View and users should not be able to update via bulk update, per point 1.)
|Component||End User UI|
|Priority||Medium - Important|