Enabling optional modules

Sometimes buttons or fields that are related to a module are displayed on base SyteLine forms, or back-end SyteLine logic is related to a module. For example, the Pay with Credit Card button on the Customer Orders form is used only with the Credit Card Interface module. These base SyteLine features of the module are handled on a site-by-site basis; you can enable them for one site in a database but not for other sites in the same database.

Use the Optional Modules form to enable the features for a specific optional module at a specific SyteLine site:

• When a module is shown as Disabled on this form for a site, fields and buttons related to that module are not displayed (in some cases) or are displayed but not enabled (in other cases) when any user is logged into that site. In addition, none of the back-end business logic related to that module is executed for the site.

  If a module is licensed for a database, but disabled for a particular site in that database, the site administrator should ensure that authorizations are set so that users cannot access forms which are part of the optional module.

• When a module is shown as Enabled on this form, any fields or buttons related to that module are displayed on base SyteLine forms, and back-end business logic related to that module is executed. Thus, in our example, the Pay with Credit Card button is enabled only when the CreditCardInterface license module is enabled on the Optional Modules form for the site.