![]()
|
Ways To Customize BillerXpertBillerXpert follows the NAS recommendation of using a single AppLogic for a single purpose. This keeps each AppLogic small and focused on a single task. BillerXpert also separates the validation and data access into separate classes from the AppLogic itself. You are not required to follow this model; but object-oriented programming lends itself well to this structure. For example, if you want to use additional data in application business objects, you can derive your own class to access the data. Likewise, if your form accepts different inputs, you can derive your own validation class to verify them.Front-end classes are divided into two kinds, those that are specific to the telco stencil and those that are generally useful for any kind of billing application. The latter classes include the BillerXpert common and core classes. To customize a BillerXpert stencil or application, you can use different
approaches, depending on the level of customization required. Five different
approaches are summarized in the following table, from simple changes to
more sophisticated customization.
Also, if BillerXpert does not provide support for the data that you
want to access from a data repository, you can alter the schema to support
the new data and implement your own component business object class to
provide access to the data.
|