Mass update needs to be disabled or made 'invincible'

[rehlers]

Issue:
Mass update needs to be disabled or made 'invincible'
Reason: obvious, various sales and marketing personell can 'update at random and create havock.

I understand there different ways of doing so, theroratically we don't need that module at all. So the simplest way is probably the best.

Version 5.0.0a (Build 3120)

Thank you.

R.

[eggsurplus]

This not upgrade safe but:
include/MVC/View/views/view.list.php:

Find $params = array('massupdate' => true); around line 122. Change to:

  
        global $current_user;
        $params = array('massupdate' => (is_admin($current_user)?true:false)); 
  

This will make it so that the MassUpdate area only shows for admin users.

[rehlers]

Hmmm.

Actually - it didn't do anything different. Not even an error message. Mass update is still available to every user.

I haven't changed code back yet as I am thinking about it. If you have any other ideas, please let me know.

I believe this is a very common request, we really want to upgrade and use Sugar, I start loving it. I have 2 more issues to sort - nothing big, ha, ha. Like module doesn't work

This first, IF anybody could help - would be great.

Thanks,

R.

[URtech]

Hi eggsurplus,

Your recommendation worked for me; however, it looks like it also restricts selecting records and using export or merge duplicates features if you're not an admin which is an undesired side effect. Therefore, it's not exactly as granular a control over locking down the mass update than I'm looking for.

I've got to believe Sugar will be adding this kind of control to the Roles functionality. Anyone from Sugar care to chime in?

In the meantime, I found a helpful approach to hide mass update here: http://www.sugarcrm.com/forums/showt...t=33384&page=2

Cheers, Sean

[wynn]

This is really a problem, you can only make it display:none.

now, your checked value all stores in the Massupdate form. and Delete, export all make use of this form. And in future release, the pagination will use this form to aviod a pagination bug.


So I think you'd better make it to be in a <div style="display:none;">

[kuske]

In module \include\Massupdate.php you can change the Definition of the div

$html = "<div id='massupdate_form'>" . get_form_header($app_strings['LBL_MASS_UPDATE'], '', false);

to

$html = "<div id='massupdate_form' style='display:none;'>" . get_form_header($app_strings['LBL_MASS_UPDATE'], '', false);

as wynn described it.

You can define dependencies like which module was called
if ($_REQUEST['module'] == 'Accounts') ...

or who is the caller
if ($current_user->user_name == 'admin') ...

or whether the caller is admin
if ($current_user->is_admin == 1) ...
etc. pp.

Example:
$hyde = "";
if ($current_user->is_admin != 1)
$hyde=" style='display:none;' ";
$html = "<div id='massupdate_form' ".$hyde.">" . get_form_header($app_strings['LBL_MASS_UPDATE'], '', false);