Custom Record.php blocking Escalate button after upgrade

Hi Daniel Hill ,

The record view is basically an array, the ['buttons'] sub-array, and in particular the ['actiondropdown'] sub-array within that, controls what you see in the as the actions menu.

That is where the "Escalate" button lives, in the default Cases record view ( see: modules/Cases/clients/base/views/record/record.php ); it's the second element in the array at $viewdefs['Cases']['base']['view']['record']['buttons'][actiondropdown']['buttons']

                [
                    'type' => 'escalate-action',
                    'event' => 'button:escalate_button:click',
                    'name' => 'escalate_button',
                    'label' => 'LBL_ESCALATE_BUTTON_LABEL',
                    'acl_action' => 'create',
                ],

If your custom view overrides the buttons too, as mine does, then any new ones that are added don't automatically get populated.

I know, it's a bit odd since sugar DOES add new fields to our custom views, like the "is_escalated" badge that was automatically inserted into the ['panel_header'] of the view.

If you don't mind working in code, you will simply have to add the escalate button code found in the standard view to your custom code in the$viewdefs['Cases']['base']['view']['record']['buttons'][actiondropdown']['buttons'] section of the array and do a QRR for the Escalate option to show in your actions menu.

If you don't work in code, then I guess you have two options: restore the default layout of your Cases module from Studio and then re-customize your layout to what you wanted it to be, or ask support to add the Escalate button to your custom view and let them do it through code.

FrancescaS

Thanks Francesca Shiekh ! I've added it via the method you mention, I was hoping there may be an automated way as we have 100+ containers to do this on potentially. But glad to know I'm going down the right route. Thanks!

Thanks Francesca Shiekh ! I've added it via the method you mention, I was hoping there may be an automated way as we have 100+ containers to do this on potentially. But glad to know I'm going down the right route. Thanks!