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 partModule installation
Module installaction loads necessary data from the module definition into the system
- What makes installation
- Common errors from module installation
- Right defined in the module definition file is not imported
What makes installation
Procesing m_Conf file and each object
Installation loads all objects to the system. Objects shall be defined by the m_Conf file in order in which they are imported. Thats importan to load abstract ancestor, or generally ancestors, before the descendant. The process seaches for derived information into the data stored about the ancestor so that they should be loaded before.
Instllation:
- Fill data about each object
- Stores all information from m_Conf file to the system:
- What system rights are defined
- What user-defined counters are supported
- Instal event handlers into the system
Common errors from module installation
Wrong data about object
Be carefull that you don't have the same object name in several files. Although it might sound stupid it is common error – when you create several objects by copy-paste from another object, invalid name might remain in some field
Right defined in the module definition file is not imported
Rights are imported only in case that all objects are sucessfully loaded. If import of some object fails, rights are not updated.