Related links
Homepage
User documentation
Uživatelská dokumentaceFI - Finance Management
Framework Core functionality
- AyMINE Framework Server
- frmFrm – provided functionality
- System Rights
- System messaging
- AyMINE Business – Price calculation
- Strings and translations
- Export collection of objects
- AyMINE Framework management FAQ
- The AyMINE licence model
- AyMINE On-premise
- System events
- Mutli-client architecture
- Import collection of objects
- User sessions
- Default server methods
- Client-defined object attributes
- Common Libraries
Module - support for management
Libraries & Lincences
Mobile & Web Application
- Runtime debugging
- System console
- AyMINE Application
- In-line table edit support
- Object scripting API – object lang
- Application object structure
- Multilingual support
- View of a single object – detail
- Is using EVAL / feval method risky?
- Included library – String operations
- Cliplink
- Object API – object <g>
- API – Data object
- Object scripting API – object User
- Object view definition
- Framework support for Drag & Drop
- Common libraries
- Multiple-object update implementation
- fClip & fCliplist
- Offline persistent objects
- Mobile application
HR - Human Resources
System Management (part of framework)
Task, Project, Quality
Task & Task pattern
CMS - Content Management & Web API services
Mutli-client architecture
AyMINE is modern system since the design root proposed to work in SaaS model for many clients
The multiclient ahrchitecture was proposed in order to serve perfectly in the SaaS model. Thanks to that, its SaaS provision is much simpler than for most of the application desinged for single-company used.
The major multi-client principles
- All clients have data in the same scheme but they are completely splitted
- All SQL views are always linked to the client
- The data and application wall between the clients' space is managed by the AyMINE framework. Developers to not bother about that. It stronly reduce risk of error made by programmer
- Application server processes always runs for single client only
- User application don't see anything about the client definition. It can never skip to another client
It has also some implications to the usage
- Users cannot build up their own SQL queries. Since there are not only their data, self-defined query is always i potential penetration over the wall
- Many counter and pre-defined values are system-defined and clients cannot update them easily. However, there is roadpath how to make them country-related or even customer-related. Thus, it does not hinder customer-related solution when delivered by responsible programmers.