Related links
Homepage
User documentation
Uživatelská dokumentaceSales & Asset management
Sales related services
Description of a part of the AM module - sales partFI - Finance Management
Framework Core functionality
- AyMINE Framework Server
- frmFrm – provided functionality
- System Rights
- System messaging
- AyMINE Business – Price calculation
- Strings and translations
- Export collection of objects
- AyMINE Framework management FAQ
- The AyMINE licence model
- AyMINE On-premise
- System events
- Mutli-client architecture
- Import collection of objects
- User sessions
- Default server methods
- Client-defined object attributes
- Common Libraries
Module - support for management
Libraries & Lincences
Mobile & Web Application
- Runtime debugging
- System console
- AyMINE Application
- In-line table edit support
- Object scripting API – object lang
- Application object structure
- Multilingual support
- View of a single object – detail
- Is using EVAL / feval method risky?
- Included library – String operations
- Cliplink
- Object API – object <g>
- API – Data object
- Object scripting API – object User
- Object view definition
- Framework support for Drag & Drop
- Common libraries
- Multiple-object update implementation
- fClip & fCliplist
- Offline persistent objects
- Mobile application
HR - Human Resources
System Management (part of framework)
Task, Project, Quality
Task & Task pattern
CMS - Content Management & Web API services
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.