Related links
Framework Core functionality
- AyMINE Framework Server
- Configuration of the user-defined fields
- Client-Defined attributes
- Default server methods
- Strings and translations
- User sessions
- Import collection of objects
- Multi tenant Architecture
- The AyMINE licence model
- Export collection of objects
- System messaging
- System Rights
- File Management with End-to-End Encryption
- Server configuration for large files
SOA / Event Management
Support for Service Object Architecture and Internal Event ManagementModule - support for management
Front-End Scripting
System Management
- SaaS Management Module
- Management of the SaaS service client
- Encryted wallet storing access keys for data vault
- Definition and Management users in the SaaS system
- Management of the system users
- System right management
- System role is how user administrator sets the rights
- File access, storing and locking
- Communication geateways
- Private Object Marks, Sign & Notes
Task Management Module
- About TSK module
- Support for voting and decision management
- Support and implementation notes for FMEA
- Support for the Methodology Management
- Project Methodology Support
- Project Roles - Data model and implementation notes
- Actions and Meeting Agenda
- Description of person and supplier competencies
- Business event
- Problem & Helpdesk management support
- TSK module releases
- User Reminder
Task & Task pattern
Mobile & Web Application
- Client-Side Scripting using API
- Application Object Structure
- Clipborad Link - Cliplink
- fclip
- drag-drop
- AyMINE Application
- objectdefinition_inlineedit
- clientprogramming
- mobileapplication
- languagesupport
- objectdefinition_multiupdate
- Object API – object <g>
- clientprogramming_fevallanguage
- clientprogramming_fevaluser
- objectdefinition_viewdefinition
- offlineobjects
- System console
- Runtime debugging
- objectdefinition_detailview
CMS - Content Management & Web API services
FI - Finance Management
CRM - Customer-Relationship Management
Sales & Asset management
Sales related services
Description of a part of the AM module - sales part
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