Managing Plug-ins

A plug-in is customized functionality that is defined by an interface. After a plug-in is implemented, users with the Administrator role can override the plug-in’s default logic to better fit their organization's needs.

NetSuite provides core plug-ins, which are usually part of a major release. A core plug-in’s interface defines functions that are run within the core NetSuite code. For more information about core plug-ins, see Core Plug-in Overview.

Third-party providers develop custom plug-ins as alternate implementations of an interface, and bundle them in a SuiteApp. For more information about custom plug-ins, see Custom Plug-in Overview.

When a plug-in’s implementations are ready, a user with the Administrator role activates the implementations available for each NetSuite account.

To view the plug-in implementations available in an account, go to Customization > Plug-ins > Manage Plug-ins.

The Manage Plug-in Implementations page lists the core and custom plug-in implementations that are available in the current account. To activate an implementation, check the box. To inactivate an implementation, clear the box.

Make changes as required. Then, click Save.

Viewing Plug-in Implementation System Notes

To view the activity of your plug-in implementation, use the System Notes subtab.

To view plug-in implementation system notes:

  1. Go to Customization > Plug-ins > Plug-in Implementations. Click Edit beside the implementation that you want to view.

  2. Click the System Notes subtab.

    Note:

    Previously, plug-in implementation information was listed on the History subtab, but that subtab is no longer updated. New plug-in implementation activity is captured on the System Notes subtab.

System Notes subtab on the Plug-In Implementation page.

The system note for changes to a plug-in implementation record captures the following information:

For more information about system notes, see System Notes Overview

Important:

NetSuite always uses the current version of the Custom GL Lines Plug-in. An older version of the plug-in may have been used to create a transaction, and may have generated a different result than the current version. If you try to update a transaction in a closed period, and the current version of the plug-in generates a different result, you can't save y updates.

You can either open the period, or branch your plug-in implementation based on the plug-in version date.

Related Topics

General Notices