summaryrefslogtreecommitdiff
path: root/postgresqleu/digisign/models.py
AgeCommit message (Collapse)Author
2023-11-14Download completed digital contracts and store them in the dbMagnus Hagander
For now, also allow viewing of the contracts from the administrative interface by organizers, but not yet by the sponsors themselves (no reason not to, just one step at a time).
2023-10-27Track and show processing dates of digital contractsMagnus Hagander
Instead of just keeping track of that a contract has been signed, explicitly track *when* it was sign. Also track when a contract is partially signed (for confsponsor that's signed by the sponsor but not by the organizers). And show this information on the sponsorship dashboard and the sponsorship details.
2023-07-12Implement re-sending of sponsorship contractsMagnus Hagander
For e-mail based contracts, this just re-generates the PDF and sends it. For digital contracts (only available if supported by the provider), it will both cancel the old contract and create/send a new one.
2023-06-02Add a log view that shows full debug details of digisign logsMagnus Hagander
2023-06-02Add support for digital signature providersMagnus Hagander
This adds a new type of provider to the system for handling digital signatures. Initially the only consumer is conference sponsorships, but it could be added for other parts of the system as well in the future. Regular "old-style" sponsorship contracts are still supported, but will gain the feature to auto-fill sponsor name and VAT number if wanted. The sponsor signup workflow is adjusted to support either one or both of the two methods. Initially the only implementation is Signwell, but the system is made pluggable just like e.g. the payment providers, so other suppliers can be added in the future. This should be considered fairly beta at this point, as several parts of it cannot be fully tested until a production account is in place. But the basics are there...