Web Based Framework

The Claromentis Framework and all of the significant business applications within it build up a powerful and configurable modular system. Although all applications are in some ways independent from each other, they all use the same tools existing inside the system.

Those tools are: global users accounts, unified permissions system, database abstraction, classes autoloading system, powerful templates and skin system. This makes Claromentis a true Framework rather than just a normal intranet web system.

Core Applications

As even core applications are almost like plugins, it’s easily possible to create bespoke applications to match specific client needs. On a technical level core applications don’t have any significant inherent benefit from the fact that they are included into the Claromentis distributive. It’s only developers skills and experience that limits what can be created within the Claromentis framework.

Open Documentation

Though all core code is encrypted, we maintain in our API fully open documentation on all classes and functions - this allows non-core developers to understand the internals of the system.

Many components are described in further details - in a special wiki where core developers create content and describe the ways of using the Claromentis Framework utility classes and components. This documentation contains a detailed description of components, usage examples and hints.

And if even this is not enough, the Claromentis core team is still open to provide direct help to external developers or create required bespoke application themselves.

Direct application interfaces

Many existing applications provide ready-to-use ways for customizations and programming interfaces to extend their functionality in those cases where the default is not sufficient. This includes InfoCapture plugins, custom reports, special login handlers, templater components and, of course, templates themselves.

Upgradable yet still customizable

The structure of the system is such that it can take customizations and still be easily upgraded without affecting custom code/templates. Sometimes changes in the core code as we evolve our software affect previously existing API and may cause an incompatibility. We keep track of such changes and can always provide this information by request.