Related links
Framework Core functionality
- Client-defined object attributes
- Common Libraries
- Default server methods
- Export collection of objects
- AyMINE Framework Server
- The AyMINE licence model
- System Rights
- Import collection of objects
- Multi tenant Architecture
- Strings and translations
- Event-based architecture
- System messaging
- User sessions
- User defined fields
Libraries & Lincences
Module - support for management
Front-End Scripting
System Management
Task Management Module
Task & Task pattern
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
CMS - Content Management & Web API services
FI - Finance Management
Sales & Asset management
Sales related services
Description of a part of the AM module - sales partHR - Human Resources
Project roles
The implementation of project roles is closely linked to the support of the methodology.
The project roles are defined as part of the methodology and linked to the sample tasks. Although it is possible to use project roles on their own without a project template, their definition is part of the methodology - therefore, it is necessary to have a methodology defined for them
Project roles are the link between the sample tasks (project steps) and the competences. While non-project tasks are primarily linked to competences, project tasks are linked to project roles.
The Busienss view of project roles is described here.
The assignment of an employee to a project role within a project reflects the occupation of that role as described in the following diagram: