 |
The Registry allows you to customize most aspects of your system, including buttons and field labels, alert statements, required fields, pop-up messages, default values, time-outs, payment processing gateways, printer ports and data input limitations. Modifying the Registry affects your entire system and all users and roles. If you want to modify items displayed to a specific group, you should modify items at the group level (permissions, attributes and content) or the user level (preferences) in Application Security. |
Page |
Description |
Used to define the look and feel of the application for all users based on your organization needs. Registry settings can be overridden at the group or user level in Application Security. |
|
Defines system-wide parameters and utilities for low-level support functions of the application, such as password requirements, report databases, currencies and conversion rates, and so on. Most of these configuration options are global to all users and cannot be overridden in Application Security. |
|
Used to purge encrypted customer cardholder payment information, add additional languages and export Registry values. |
All security for each BO and CO resides in the System tab. Against each BO and CO, an 'Actions' attribute is associated to a list.
The list and the contents of the actions are defined as a list in General Configuration (see 'The Contents of the 'TSCustomerBO actions' List' for an example).
By associating each BO and CO with a customized list of actions, the action lists become specific to the needs of the BO and CO. With the infrastructure change defining a created list, no specific coding is required for the individual objects. The infrastructure now allows for quicker development of new BOs and COs without as much intrusion into the existing system.
