Related links
Homepage
User documentation
Uživatelská dokumentaceFramework Core functionality
- Client-Defined attributes
- Framework dependency on the open-source 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
- System messaging
- User sessions
- Configuration of the user-defined fields
SOA Architecture
Support for Service Object Architecture and Internal Event ManagementLibraries & Lincences
Module - 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
- clientprogramming_fevaldataobject
- userinterface-objectstructure
- cliplink
- npmlibraries
- fclip
- drag-drop
- AyMINE Application
- objectdefinition_inlineedit
- npmlibraries_stringlibrary
- 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
Sales & Asset management
Sales related services
Description of a part of the AM module - sales partHR - Human Resources
Cliplink
cliplink functionality implementation
What is cliplink
Cliplink is described by user documentation – look there for detail.
Implementation by framework
Cliplink is implemented only by the client (both web based and mobile devices). Server never got information about the cliplink content.
Clip link is persistent, stored in the browser local storage. It does not support any transition of the content between browsers or devices.
Cliplink don’t bother about the stored object. It stores both objectName & objectID and these two values are together stored without any other context. If user lose right to see the object and then uses link stored in the cliplink, he/she can send paste invalid link to the object that changed the status or even was deleted. When paste during the object-selection in the operation-script selection list, back-end server function gets the invalid link or link that might not be allowed in the function context.
The result is that server operation can never trust that the object passed as an attribute to the function is the valid and allowed! However, that’s acceptable “complication” because regardless of the reason, server function can never trust on that.
Once again: Not only because of the cliplink functionality but generally each function at the server should verify all inputs. Cliplink is the only example how user can send invalid request.