Saturday, March 19, 2022
1 change · master
Enhancements to existing features
Shared signing links now create the final signing request only when a recipient actually signs, reducing unused draft records from casual link clicks. The person who shares the link is also kept as the sender of completed requests, helping ensure they can access the signed documents they initiated.
Original PR description
1. The dummy sign.request is created for the user who clicks the share button and create the share link. As a result, the link sharer of the final sign.request will be the creator of the completed…
1. The dummy sign.request is created for the user who clicks the share button and create the share link. As a result, the link sharer of the final sign.request will be the creator of the completed sign.request and always has its read permission 2. It uses the `copy_on_write` logic. As a result, no matter how many users clicks the share link. New sign.request are only created after they actually sign. There is one redundant dummy sign.request in the database. The user can manually delete the dummy sign.request to stop the sharing. Before this commit: 1. All internal users share the same template share_link. So the creator(sender) of the new sign.request can only be one person(the creator of the sign.template). As a result, the sender of the share link maynot have the read permission of the completed sign.request. 2. It uses the `copy_on_read` logic. As a result, the server will create a new sign.request for every click of the share_link. And some of them will never be completed. task-id: 2686174