-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[api] add form signature route #59
Comments
The underlying principle is that the user can only sign their own form. The question is what part of the application decides: the API, or the document database manager? The other question is how to decide whether a form can be signed. Is this set in the form config? Can all forms be signed? Is it a necessary part of the approval process? Do we set an onSign event hook? |
[form] add form event hooks |
Add utils for managing signatures |
Form signatures I think should be based only on the data section of a given document, not the metadata. The reason is that the data, once signed, is expected not to change; the metadata is expected TO change... eg. as approvers sign a document to move it forward. In light of this, we don't want signature validation to fail just because a manager has approved a document. |
[api] Add a validate signature API route |
[api] add a remove signature route |
Originally posted by @signebedi in #39 (comment)
The text was updated successfully, but these errors were encountered: