Cliplink

cliplink functionality implementation

• What is cliplink
• Implementation by framework

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.