Related links
Framework 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
System events
System event internally automates system and build up platform for loosely coupled modules
Technical documentation and notes for system events (frmEvent object).
processing time-based events
Time-based events are not stored in the list of events but generated directly by the manager in the planTimerEvents method
processing stored events
Processing is managed by runTimer methods. Steps are:
- planStoredEvents
- loads events waiting for processing and change the status to inProcess – the processing will never be called twice
- puts all events to the internal FIFO queue including frmEventID
- processEventFromList process:
- starts processing
- changes status to completed or error
Error handling for event processors
Event processor should inform about the error. They can do:
- Fails with an exception – that is cough by the processor
- Return error status and message in response
In both cases status of the message in the stored. Queue processing register error and set the message processed with error so that it is never processed again. The error message is stored.