|
|
 |
|
 |
| |
Every business is as unique as the individual operating them.
With that fact in mind we gave the CBP a modular plug-in architecture that allows existing functionality to be customized (or removed) and new functionality to be added.
With the CBP nearly anything can be created via a plug-in - applications, modules, forms, sections within a form and more. Fully object orientated, plug-ins can be reused again and again speeding development and providing a consistent user experience.
As flexible as it is powerful
To make the plug-in framework as flexible as possible, all plug-ins are dynamically loaded at runtime based on the records contained in the local “plug-in” table. This makes customizing CBP applications as easy as adding or modifying records in the plug-in table.
Entirely self contained yet able to inherit and overload existing functions, the CBP plug-in architecture allows your resellers and system integrators to customize your application or module for a single client without breaking the future upgrade path.
Designed with the global marketplace in mind
To ensure that applications developed with the CBP can meet the needs of the global marketplace, we developed the plug-in architecture to be multi-national ready and include support for the 238 largest countries in the world with new countries easily added. With the CBP, developers can write global applications whereas 95% of the functionality is the same across all regions, but 5% of the functionality has been localized to better meet the cultural and legislation requirements of that market.
Designed with the individual user in mind
The CBP was designed with a “User Role” architecture that allows the system to be customized (plug-in assigned) for each “User Roles” a company may have. With this powerful feature, CBP developed applications can show different module, menus, screens and more for each user role within an organization giving a system administrator the power they need to fine tune the application to the individual employees of their company.
|
|
|
 |
Plug-In Form - A container for any type of plug-in. Allows users to customize the toolbar and menu and save the customization as part of the plug-in settings.
Plug-In Tab - A container for all member plug-in tab pages in the specified plug-in form.
Plug-In Tab Page - A container for all member plug-in section in the specified plug-in tab. Allows CBP developers to easily add new tabs to existing forms
Plug-In Section - A container for a single or multiple units of plug-ins that can be added or replaced and has a customizable layout that is persisted as part of the plug-in unit.
|
 |
|
Plug-In Module - A container for any type of plug-in and has a customizable toolbar menu layout that is persisted as part of the plug-in form. Allow CBP developers to create entire modules that plug-in to existing CBP powered applications
Plug-In Dashboard - Create forms and mini-applications that work in conjunction with the dashboard menu. |
| |
|
|
|
 |
|
 |
|