Hello,
What I mean by an addon is that tabs that you can see when you're displaying a Contact (or other record), the one that allows you to view Contacts or E-mails or other information.
Defining the methods is only part of the work to have addons (including notes) added to Records. What you also need is to tell Record Browser to attach these addons. Tickets are doing this in the install() method:
Utils_RecordBrowserCommon::new_addon('premium_projects', 'Premium/Projects/Tickets', 'premium_projects_tickets_addon', 'Tickets');
The arguments are:
- RecordSet that will have the addon attached
- Main class of the module that will handle the addon
- method in the main class that displays the module
- Label for the addon
Notes addon is usually added using this method:
Utils_AttachmentCommon::new_addon('premium_projects');
You should include these calls in your install file, but if you want to avoid re-installing the module, you can also put these line in body() of your custom module, view the records and then delete these lines. Addons should then appear next time you view one of these records.
As for the pricing on Inventory Manager and eCommerce - the eCommerce requires Inventory Manager to work and each of them cost 300 USD.
If you do not have a Inventory Manager License purchased, you will see the eCommerce price to be 600 USD - that price includes both of these packages.
If you were to buy Inventory Manager first, for 300 USD, you will see that the eCommerce price will then be only 300 USD - because you already have the required module.
Hope this explains the pricing and coding of addons.
Kind regards,
Arek