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
Mobile application
AyMINE offers a mobile app. However, there are a few necessities that the server must meet.
CORS settings
To make mobile application work properly, AyMINE server has to allow certain cross-orgin communication. These permission have to be set up in three places.
- frm/FE/request.php (handled by code)
- sys/FE/sysPoint.php (handled by code)
- nginx configuration (described below)
NGINX configuration
Cross-origin requesting of static files has to be allowed in appropritate .conf file, which has to set Access-Control-Allow-Origin heder to * for files with static extensions (so far:css,js,scss,json,jsonc,png,svg,woff2)
Implementation
"location ~* \.(css|js|scss|json|jsonc|png|svg|woff2)$ {
add_header Access-Control-Allow-Origin *;
}
"