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 partHR - Human Resources
Generic Time-Base Events
Why system shall support time-based events
Time-based evens allow activation of the back-end process in regularly or in the defined time. Although the system internally doesn't need it, it is necessary for application modules to actively manage processes and system operations.
Generic time-based events simplify programming
Programmes of modules can define their own time-based events. They are important in case that system shall managed large back-end scripts in the predefined order. Module can create chain of events: The end of one step activates the next one by new event raise. However, module administrators often need organise night-time steps like synchronisation with external systems that are not in the process-type chain of operations but that shall start consequently. Independent time-based events are then better solution than chain of consequential calls; they are:
- More reliable
- Easier to manage
- Simpler to control
When using predefined events
System predefined events are intended for small back-end operations that do not need precise time planning. Usage examples:
- Check task that are in the overtime. System generates reminder for responsible
- Control old offers that are no more valid and change their status
- Calculate date-to-date summaries from records
Predefined events:
Most-frequent event timeNew
frm.time.timeNew is the most frequent event raising every 2 minutes.
Event is not intended for back-end processes but for back-end processing of tasks related with user’s agenda. Usage examples:
- Check emails in the server
- Check external server data for servers that do not push data themselves
Events activated periodically
'frm.time.timeHour' => '+1 hour',
'frm.time.timeQH' => '+15 minute',
'frm.time.timeQD' => '+6 hour',
'frm.time.timeIXX' => '+19 minute',
'frm.time.time47min' => '+47 minute'
Events activate in the predefined day time
'frm.time.Noon' => '12:02:00',
'frm.time.Midnight' => '00:02:00',
`frm.time.earlyMorning' => '05:30:00', // Begin of the Day
'frm.time.earlyAfternoon' => '13:12:11', // Early after the lunchtime - last chance to send something to the day-time-workers
'frm.time.BOD' => '07:00:00', // Begin of the Day
'frm.time.EOD' => '18:00:00', // End of the Day
'frm.time.timeNightControl21' => '21:21:00',
'frm.time.timeNightControl22' => '22:22:00',
'frm.time.timeNightControl23' => '23:23:00',
'frm.time.timeNightControl1' => '01:00:00',
'frm.time.timeNightControl2' => '02:00:00',
'frm.time.timeNightControl3' => '03:00:00',
'frm.time.timeNightControl4' => '04:00:00',
'frm.time.timeNightControl5' => '05:00:00',