In Tiki23 Plugin signature allow a user with editing permissions to save inline (inside the plugin code) a signature: "stored within the plugin content as image/png base64"
https://doc.tiki.org/PluginSignature
While this is visually nice, it doesn't really fit possible use case where a user signature is needed as acceptation or approval of "things" like terms acceptance, money transfer, administrative documents approval, administrative authorisation, etc. Saving plugin code into the page has a tendency of helping page and plugin content breakage (like with the plugin convene).
The signature should be save as a file in the file galleries.
With it, Tiki admin should be able to add essential parameters to make the feature useable (not only nice to see but to fit real life case).
For exemple if the signature is used as formal approval or authorisation and need to be matched later with a user acceptance we certainly need things like:
So later a Tiki admin or the owner of the Tiki can match document (version) and signature (user) and is able to prove "this" user with IP xx.xx.xx.xx signed this document on the xx/xx/xx.
Information exist in log more of less (username, action, ip, date, etc) we need it to be stamped with the signature file.
It would be nice this "stamped" information can be displayed easily.
IE: This signature was used by "username/ip" for "object" (version?) on the "xx/xx/xx at xx:xx"
A mechanism to reuse or forbid reusing is something we can think of.
IE : One signature for page, item and account approval.
Counter-IE: It should not be possible to reuse a signature (twice or later or after a document is changed)
By extension the file and approval can be then attached to an object (not only I a wiki page plugin body) and can be used for tracker items (important for forms, shopping, registration, etc) calendars event or other feature, etc.
filename | created | hits | comment | version | filetype | ||
---|---|---|---|---|---|---|---|
No attachments for this item |