#5674 (New plugin "approval" or "signing")

by Luc Saffre · in Developers · assigned to Luc Saffre

Résumé

First usage: user's approval of the site's terms and conditions. Second usage: generated invoices or service reports would have to get approved by a human before they are sent to their recipients.

In a first step only one database model: Invitation(Controllable, UserAuthored) with 3 fields user (the user who is asked to sign), owner (the db object to approve) and approved (a DateTimeField).

Concepts sous-jacents

Commentaires

2 ans, 3 mois ago by Luc Saffre about #5674 (New plugin "approval" or "signing") : No. None of these two use cases need such a plugin. Whether a site user agrees to the terms, is done with a timestamp field in the User model and a new type of message, similar to welcome messages, but more intrusive. And "signing" sales invoices will never be done each invoice one by one, it is rat...
2 ans, 3 mois ago by Luc Saffre about #5674 (New plugin "approval" or "signing") : The first implementation is almost done, but I still need to connect it to users.User. The users std fixture currently creates a "Welcome letter", and the User model a SendWelcomeMail action, but I think that wen want to review these approaches.
2 ans, 4 mois ago by Luc Saffre about #5674 (New plugin "approval" or "signing") : Maybe add other fields to approval.Invitatuon: due_date, remark, revoked_at, revoked_reason...
2 ans, 4 mois ago by Luc Saffre about #5674 (New plugin "approval" or "signing") : An approval invitation can be linked to any kind of db object (not only to a voucher). For example in an application like Doccle or Agrello users can upload a document and ask others to sign it.
2 ans, 4 mois ago by Luc Saffre about #5674 (New plugin "approval" or "signing") : Created new Ticket #5674 (New plugin "approve" or "signing").