How to extend the Action Button to add custom action ?

Question: Given that you are looking to customise anyway, why don't you add a completely custom button then? It could call your API or do whatever you need to.

It might be easier than attempting to try to extend Action Button, which I feel might become brittle with upgrades as well.

Hi Enrico Simonetti ,

we know how to create custom button with custom code.

But with the new and very cool actionbutton feature, it would be great to define button the same way, with a setting screen but also benefit the actionbutton settings (embed the button in the header or the record layout, the list layout, the focus drawer layout etc.).

So without re-code everything, I was looking for a way to extend core actionButton to define my new action.

Fred

Hi Enrico Simonetti ,

we know how to create custom button with custom code.

But with the new and very cool actionbutton feature, it would be great to define button the same way, with a setting screen but also benefit the actionbutton settings (embed the button in the header or the record layout, the list layout, the focus drawer layout etc.).

So without re-code everything, I was looking for a way to extend core actionButton to define my new action.

Fred

Depending on what you want to do with the custom action, you could perhaps use a custom Sugar Formula to do the dirty work OR go with Enrico's suggestion of creating a completely custom button that's not tied to the ActionButton stuff.
I'd avoid extending it as it seems like asking for trouble down the line.

Hi Frédéric Rinaldi ,

I agree with András Tőkés .

Honestly, I don't think action buttons have been built with custom extensibility in mind, hence why my suggestions. But I am more than happy to be proven wrong if you want to attempt this! You are better off asking for a feature request to Sugar.

For example, some of the components that come to mind are:

• the studio interface to be able to add buttons
• the logic that adds the button to the right place, which needs to be aware of your changes
• the logic that triggers when you press the button
• the API that triggers

All the above are a mix of layouts, views and plugins, which in themselves are not easy to extend. You could override them, and then lose any future upgrades coming from Sugar on this functionality.

Feel free to have a look at all the files with a quick code grep:

grep -Ri "actionbutton" . | grep  -v "min" | grep -v "Minified" | grep -v "lang.php" | grep -v ".md5" | grep -v "autoload_" | grep -v "cache"

and you will see what I mean...

I believe this approach would just be looking for troubles.

Good luck!