Related links
CMS - Content Management & Web API services
FI - Finance Management
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
Libraries & Lincences
Module - support for management
Front-End Scripting
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
Sales & Asset management
Sales related services
Description of a part of the AM module - sales partSystem Management (part of framework)
Task, Project, Quality
Task & Task pattern
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