AnsweredAssumed Answered

how do fields get set readonly (from dependencies to web page)

Question asked by Andrew Gin on May 3, 2017
Latest reply on May 4, 2017 by Andrew Gin


I am trying to figure out why my dependencies are not working properly (see thread here)

Some fields cannot be made readonly 


I have set some fields to be read only and I want to follow the chain of code that leads to these fields being made readonly on the page when viewed on a browser.


I don't know enough about sugar architecture so I'd like a few pointers on where to look next;


    $dependencies['Opportunities']['lock_opportunity'] = array(
            'hooks' => array("edit"),
            'trigger' => 'equal($sales_stage, "Closed Won")',
            'triggerFields' => array('sales_stage'),
            'onload' => true,
            'actions' => array(
                    'name' => 'ReadOnly',
                    'params' => array(
                        'target' => 'description',
                        'label' => 'LBL_DESCRIPTION',
                        'value' => 'true',


- in the above dependency (which I have stored in custom/Extension/modules/Opportunities/Ext/Dependencies/opportunity_read_only.php), I am making the description field readonly. What happens with the action array (which file/function uses its contents?)

- clients/base/views/record/record.js contains code that makes fields uneditable (noEditFields), but when I comment out all this code, it has no effect on whether fields are readonly or not.