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
Actions and Meeting Agenda
Technical documentation
Relation of objects with meetings
Meeting is linked with tasks, information items and decisions. Other objects can be supported, if necessary.
Relations are stored as tskActivityRec object with the following data:
- principlal object task/information/decision
- source object meeting
- system tyoe SM – system meeting defined and not editable directly from object
- dtActivity start of the meeting
- shortDesc description from meeting – editable through the meeting
- operCode code of the decision made on the meeting; set by button, always readonly in the menu
- timeSpent duration of the meeting
- shortDesc meeting record relevant to the point
- tskAreaID set to the area of the meeting. So that information about meeting is visible only to person the has access to the meeting itself
Relations are created in the moment when object is allocated to the meeting. optCode is null until set by the meeting team (during the meeting)
Meeting preparation
People can allocate task and other objects to the future meetings where they are between members or they are actors of the area of the meeting
During the meeting, only responsible and manager can edit and add records
Records are editable and operations changed until end of the meeting