Related links
Homepage
User documentation
Uživatelská dokumentaceFramework Core functionality
- AyMINE Framework Server
- Configuration of the user-defined fields
- Client-Defined attributes
- Default server methods
- Strings and translations
- User sessions
- Import collection of objects
- Multi tenant Architecture
- The AyMINE licence model
- Export collection of objects
- System messaging
- System Rights
- File Management with End-to-End Encryption
- Server configuration for large files
SOA / Event Management
Support for Service Object Architecture and Internal Event ManagementModule - support for management
Front-End Scripting
System Management
- SaaS Management Module
- Management of the SaaS service client
- Encryted wallet storing access keys for data vault
- Definition and Management users in the SaaS system
- Management of the system users
- System right management
- System role is how user administrator sets the rights
- File access, storing and locking
- Communication geateways
- Private Object Marks, Sign & Notes
Task Management Module
- About TSK module
- Support for voting and decision management
- Support and implementation notes for FMEA
- Support for the Methodology Management
- Project Methodology Support
- Project Roles - Data model and implementation notes
- Actions and Meeting Agenda
- Description of person and supplier competencies
- Business event
- Problem & Helpdesk management support
- TSK module releases
- User Reminder
Task & Task pattern
Mobile & Web Application
- Client-Side Scripting using API
- Application Object Structure
- Clipborad Link - Cliplink
- fclip
- drag-drop
- AyMINE Application
- objectdefinition_inlineedit
- clientprogramming
- mobileapplication
- languagesupport
- objectdefinition_multiupdate
- Object API – object <g>
- clientprogramming_fevallanguage
- clientprogramming_fevaluser
- objectdefinition_viewdefinition
- offlineobjects
- System console
- Runtime debugging
- objectdefinition_detailview
CMS - Content Management & Web API services
FI - Finance Management
CRM - Customer-Relationship Management
Sales & Asset management
Sales related services
Description of a part of the AM module - sales part
Single module description
System modules are registered and installed. Object module describe the installation state
The purpose of the module definition is:
- Evidence what system modules are installed in the environment
- Documentation of the last installation process results (Modules could be reinstalled repeatedly when changed)
- Linkage to the module options
Module is master object for several other objects that described module settings for clients.
Module object – data model
Related objects
Event Handlers
Each module could defined handlers for events – both system events and events from related modules. More information about system events is here. Events are loaded during module installation
Object
Object describes each object supported by module. It stores attributes and data necessary for server automation.
Right
Rights are low-level system rights. They are not directly used to set up users' rights but they are linked via system roles
Complete right management is subject of the system module but rights available for management are defined by modules and objects.
Translation
Translation imported to the database are only those that are used by the server – back-end functionality. Front-end application does not uses them.
Back-end translations are used for back-end generated pages, email messages and automatically generated reminders. They are defined by the back-end translation modules m_
Enum – Counters
Imported counter are used mostly for report generation and for generation of the code during the development. The back-end code does not regularly use them because they work with internally defined counter constants. However, the constants are generated from this table.