Related links
Front-End Scripting
CMS - Content Management & Web API services
Task, Project, Quality
Task & Task pattern
System Management (part of framework)
HR - Human Resources
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
Framework Core functionality
- prices
- managementfaq
- prices_private-installation
- clientdefinedattributes
- phplibraries
- servermethods
- io_export
- AyMINE Framework Server
- The AyMINE licence model
- System Rights
- servermethods_frmfrm
- io_import
- multiclient-architecture
- servermethods_stringsandtranslations
- frmevent
- System messaging
- usersessions
- User defined fields
Libraries & Lincences
Module - support for management
FI - Finance Management
Sales & Asset management
Sales related services
Description of a part of the AM module - sales part
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.