Restrict editing of records

[seanmh]

I'm trying to lock users out of editing specific opportunities if certain conditions are met. I've tried the security suite without success as it prevents the users from creating new accounts. Anyone know where I can start to find information on how to do this?

[andopes]

Hi seanmh

Let us know all conditions which are going to restrict editing Opportunities.
I'm sure we can help you, but the implementation / customization depends on specific conditions.

Best regards

[seanmh]

I want to lock it based on a users role, a built-in field, and a custom field. Do you need more specifics?

Thanks!

[andopes]

Hi seanmh

It is getting clearer but additional details would be helpful.

Cheers

[meeric]

Hi

You can use hooks if you know code PHP script

regards

[seanmh]

Hi seanmh

It is getting clearer but additional details would be helpful.

Cheers

If the opportunity sales stage is "Closed Won" and there's an 'ops approval date' (custom field) I want to lock that user that is of the role "Sales" out from editing the opportunity.

I am familiar with PHP but I'm not sure how to access certain variables within Sugar. Like the users role.

I hope this helps. Let me know.

Thanks!

[andopes]

Hi seanmh

Create the file custom/modules/Opportunities/controller.php with this content:

 <?PHP
require_once('include/MVC/Controller/SugarController.php');
 
class OpportunitiesController extends SugarController {
    function action_editview() {
        global $current_user;
    
        if($this->bean->sales_stage == 'Closed Won' && $this->bean->ops_approval_date != '' && ! $current_user->check_role_membership('Sales')) {
            $this->view = 'noaccess';
        } else {
            $this->view = 'edit';
        }
 
        $GLOBALS['view'] = $this->view;
    }
}
?>  

Probably you need to fix the name of the custom field

Cheers

[seanmh]

Wow! I wasn't expecting you to give me code. Thank you! It doesn't seem to work, here's what I have:

 <?php
require_once('include/MVC/Controller/SugarController.php');
 
class OpportunitiesController extends SugarController {
    function action_editview() {
        global $current_user;
 
        if($this->bean->sales_stage == 'Closed Won' && $this->bean->ops_approval_date_c != '' && ! $current_user->check_role_membership('Sales People')) {
            $this->view = 'noaccess';
        } else {
            $this->view = 'edit';
        }
 
        $GLOBALS['view'] = $this->view;
    }
}
?>  

I'm assuming that the custom field has to be the full name from the database? Should the edit button disappear or should they just not be able to go in to the record? After I made the changes I rebuilt the relationships and did a quick repair. The user of the role 'Sales People' still can see the edit button and edit the opportunity. Any input is appreciated.

Thanks again!

--EDIT--

I spoke too soon. I modified it a bit and got it work. I really appreciate your help. Thank you.

[andopes]

Hi seanmh

You need to create a view.detail.php to remove the button Edit from layout if the user can not edit this record.

Cheers

[seanmh]

I'm not familiar with this file. I see that one exists but I'm not sure what I'd need to change to remove the edit button for the same rules above.