Related links
Homepage
User documentation
Uživatelská dokumentaceFramework Core functionality
- Client-defined object attributes
- Common Libraries
- Default server methods
- Export collection of objects
- AyMINE Framework Server
- The AyMINE licence model
- System Rights
- Import collection of objects
- Multi tenant Architecture
- Strings and translations
- Event-based architecture
- System messaging
- User sessions
- User defined fields
Libraries & Lincences
Module - support for management
Front-End Scripting
System Management
Task Management Module
Task & Task pattern
Mobile & Web Application
- clientprogramming_fevaldataobject
- userinterface-objectstructure
- cliplink
- npmlibraries
- fclip
- drag-drop
- AyMINE Application
- objectdefinition_inlineedit
- npmlibraries_stringlibrary
- clientprogramming
- mobileapplication
- languagesupport
- objectdefinition_multiupdate
- clientprogramming_fevalglobal
- clientprogramming_fevallanguage
- clientprogramming_fevaluser
- objectdefinition_viewdefinition
- offlineobjects
- System console
- Runtime debugging
- objectdefinition_detailview
CMS - Content Management & Web API services
FI - Finance Management
Sales & Asset management
Sales related services
Description of a part of the AM module - sales partHR - Human Resources
Support for helpdesk management
Helpdesk integrates functionality from communication, documentation and process management
New message about the problem
Helpdesk servers all kinds of clients’ problems that are not related with project. Messages about a problem could come by any channel - from the omnichannel communication.
The following scheme is valid for all kinds of input (external) messages
Storing a ticket
Ticket is internally a problem - tskProblem record. That's the object from the TSK module, so that communication according to a new problem-ticket integrates several modules.
The sequence scheme in the next diagram describes the communication in detail:
