Signature Platform - Copy this React, Tailwind Component to your project
Platform:-Sign-+-example-integration-with-webhook-and-outgoing-url-We-want-to-support-the-organization-sends-out-the-documents-to-their-customer-for-signing-and-sending-back-to-them.-That-can-be:-•-A-single-Signatory-signing-a-File-or-multiple-Files.-•-Multiple-Signatories-signing-a-single-File-or-multiple-Files.-•-Multiple-Signatories-in-same-Company-signing-a-single-File-or-multiple-Files.-Terminology:-Three-types-of-Sign-actions-will-be-introduced:-•-Signature-Request-(SR)-is-meant-for-a-single-signatory-and-contains-all-the-files-to-be-signed-and-additional-cover-letters.-Recipient-declares-as-an-end-user-who-will-sign-documents.-•-Signature-Order-Request-(SOR)-is-meant-for-multiple-signatories-and-contains-all-shared-files-to-be-signed-amongst-the-multiple-signatories.-A-"group-signing-ID"-is-included-on-each-Action-to-mark-the-Signature-Order-to-be-created-based-on-the-files-specified-in-the-Sign-Action.-Recipient-declares-as-“ANDET"-means-this-is-a-TECHNICAL-message.-•-Signature-Action-Request-(SAR):-contains-additional-cover-letters-(not-be-signed),-and-a-reference-to-SOR-via-the-"group-signing-ID".-Recipient-declares-an-end-user-who-will-sign-documents.-In-brief,-the-sign-flows-will-be:-Flow-1:-A-single-Signatory-signing-a-File-or-multiple-Files-+-Multiple-Signatories-signing-a-single-File-or-multiple-Files:-•-The-customer-sends-the-Signature-Request-(SR)-or-SOR-+-SAR-to-the-end-user(s)-(aka.-Signatory-or-signatories).-•-The-MeMo-will-be-distributed-to-the-end-user(s).-•-(Each)-end-user-can-read-the-documents-before-signing.-•-Then,-the-end-user-signs-document(s).-•-After-signing,-the-end-user-can-see-the-success-receipt-(or-failed-receipt).-•-After-the-sign-request-is-completed-(all-signatories-signed-it),-the-customer-will-receive-the-Action-result-contains-document(s)-signed-by-all-signatories.-•-If-the-customer-subscribes-to-the-feature-to-send-the-signed-document,-and-they-specify-on-MeMo,-then-the-end-user-(signatory)-will-receive-the-message-containing-signed-documents-under-'Sent'-tag-with-the-sender-as-the-customer.-•-If-the-end-user-rejects-signing,-the-customer-will-also-receive-the-Action-result-contains-the-rejected-message.-•-The-customer-can-receive-the-bill-including-the-sign-feature.-The-sign-actions-should-be-billed-like-others.-Flow-2:-Multiple-Signatories-in-same-Company-signing-a-single-File-or-multiple-Files:-like-Flow-1.-However,-the-end-user-(now-are-an-employee)-needs-to-define-how-many-signatories-in-the-documents-before-signing.-•-The-customer-A-sends-the-SR-to-the-company-B-mailbox.-•-When-the-first-employee-(B)-sees-a-Sign-message-in-the-VC,-he/she-needs-to-define-a-number-of-Signatories.-•-After-signing-the-files,-the-employee-(B)-will-see-the-receipt-based-on-the-signing-status.-•-When-the-employee-(B)-has-finished-signing,-an-action-result-containing-the-number-of-signed-signatory-and-signatory-identity-id-will-be-sent-to-sender-customer.-•-When-the-last-employee-(B)-has-finished-signing,-there-will-be-an-Action-Result-containing-the-signed-files-with-seal-sent-to-the-customer-(A).-•-When-the-number-of-signatories-reaches-the-total-required-number-of-signatories,-the-employee-(B)-can-see-the-completed-action-status.-•-The-customer-(A)-also-receives-the-Action-result-contains-document(s)-signed-by-all-signatories.-•-If-the-customer-subscribes-to-the-feature-to-send-the-signed-document,-and-they-specify-on-MeMo,-then-the-end-user-(signatory)-will-receive-the-message-containing-signed-documents-under-'Sent'-tag-with-the-sender-as-the-customer.-•-Customers-should-be-able-to-configure-on-each-MeMo-they-send-out-whether-they-want-to-send-back-the-signed-and-sealed-documents-to-the-signatories.-AP:-•-NC-admin-can-see-and-enable-subscription-Sign-feature-in-the-Feature-Page-for-the-company.-The-feature-list-is:-◦-Sign-(parent-feature)-▪-Automatic-delivery-of-signed-documents-to-signatory-for-specific-messages-▪-Automatic-delivery-of-signed-documents-to-signatory-for-all-messages-▪-Sequence-of-multiple-signatories.-•-New-page-for-Sign-to-describe-the-feature.-•-Customer-admin-can-see-Sign-feature-card-on-Overview-&-in-the-navigation-bar.-•-Multilingual-text.-VC:-•-In-Homepage,-the-end-user-can-recognize-a-Sign-message-by-a-Sign-icon.-◦-Sign-icon-can-be-colored:-Active-action.-◦-Sign-icon-is-greyed-out:-Inactive-action.-It-can-be-completed-or-expired.[TN1]-•-The-end-user-can-see-the-Go-to-Sign-action-in-the-message-view-(figma).-•-When-clicking-to-the-Go-to-Sign-action-button,-the-end-user-can-see-and-read-signing-file(s)-individually-before-signing-(figma).-◦-Some-roles-can't-sign-on-behalf-of-another-owner-mailbox.-For-example,-in-mit.dk,-the-end-users-with-the-role-LEGAL_OWNER_OF_CLOSED_COMPANY-who-will-not-be-able-to-complete-sign-actions-in-the-mailbox.-End-users-with-this-role-will-be-able-to-read-messages-but-the-sign-action-will-be-disabled.[SB2]-•-The-end-user-must-choose-all-files-to-activate-the-Sign-button.-•-In-case-of-requesting-multi-signatories-as-employees,-the-end-user-needs-to-input-the-number-of-signatories-(figma?).-•-When-the-Sign-button-is-enabled.-The-user-can-sign-and-navigate-to-3rd-party-page-and-sign-there.-•-The-end-user-can-see-the-signed-message-under-'Sent'-tag-if-the-customer-decides-to-send-the-sealed-document-automatically.-Distribution:-•-MeMo-format-supports-Sign-actions-&-Sign-action-result.-•-Validation:-◦-Reject-MeMo-if-the-company-didn't-subscribe-the-feature.-◦-It-should-be-easy-to-inject-more-validation-rules-by-the-concrete-project.-•-Generate-the-Sign-action-results.-Sample-Sign-Integration:-•-Create-a-sample-integration-where-you-can-click-to-approve-or-reject-of-signing-documents.-•-Also-support-a-callback-to-update-the-sign-status.-•-Will-be-replaced-by-the-3rd-party-such-as-Criipto.-Sign-component:-•-Manage-Signature-order,-Signatories,-documents,-etc.-•-Expose-webhook-API-to-receive-the-event-from-the-sample-party-service.-•-Can-interact-to-a-sample-Sign-integration:-◦-Create-Sign-request.-◦-Fetch-signed-documents.-•-Refer-code-from-mit.dk-repo-`signature-store`.-◦-Exclude-the-Criipto-integration.
