Related links
Sales & Asset management
Sales related services
Description of a part of the AM module - sales partFI - 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
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.