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
Business event
Technical documentation related to the tskEvent – business event object implementation
event Raising
Rising event is managed by backend. It is initiated automatically or manually
automatic raise
Some objects (currently only tskDefUserTask) could have linked events. They are linked to the object create, delete or status changes. However, changes are relevant to the task created from the definition and the backend implementation should support this linkage between definition and instance for each object type.
manual raise
Manually user initiate process in the application.
Raise processing
Raising events consists of:
- create a new instance of the tskEventInstance object
- raise internal system event (EventManager::raise) that is linked with the created instance.
Objects that are able to react on the event instance catches system event and are processed independently on the raising process
event Catching
Each object that allows starting activity in response to the business event should have its own implementation of the event catching.
Catching event means it implements system event handler that is called in response to the raised event. It should start activity in response. Framework provides support in the communication using the system events but nothing more.