RightSignature is a fast and reliable e-signature service that lets users sign PDF and other documents online. Signatures can be obtained digitally, with a pointing device like a mouse or on an iPhone or an iPad, both of which also support apps.
RightSignature is exceptionally handy in the sense that it let’s you digitally sign documents on the go, whether you’re travelling or need to sign the documents in person. It is compatible with most popular browsers and requires no downloads or plugins in order to function.
With RightSignature, it is also possible to achieve a certain degree of automation; it lets you automatically send documents at predefined points points in your workflow, so that you never have to manually request signatures from a long list of clients. It’s open sourced and the API easily integrates with your website or company systems.
RightSignature and LearnDash:
LearnDash, while intended to be used as an e-learning tool on WordPress, can also be modelled as a project tracking software all thanks to it’s powerful reporting capabilities. Under these circumstances, each project is set up as a lesson, and users can be enrolled as per requirements.
To integrate RightSignature with LearnDash, you can link the document that need to be signed with LearnDash Lessons and configure them to be sent to users on events such as successful enrollment etc. Integrating RightSignature with LearnDash allows you to obtain signatures in one of the two ways:
- Send an email to user with the link to the RightSignature site to sign the document.
- Allow users to sign documents on the client site by embedding a frame that allows digital signing.
RightSignature employs a callback functionality which allows us to take different actions based on the callback data. For example: while creating a RightSignature Document, we send xml data to RightSignature site and callback location. So once the document is created, you can easily capture the event of creation and can execute your code after that.
The Events for which a callback can be employed are:
- Document creation
- Document signed by a party
- Document signed by all the parties
- Document trashed
Different actions can be performed in different cases; a document signed by all the parties, can lead to the lesson, to which the document is linked, being marked as complete. Another example is to upload signed documents to DropBox.
Integration Process Flow:
- When a user is enrolled for a Course, then our code fetches the list of all the lessons associated with the course.
- For every lesson associated with RightSignature, the path to the relevant PDF document is fetched from the lesson’s meta information, stored using meta box, and will forward the document to RightSignature.
- Once the document is generated, we obtain a unique GUID, used for accessing the generated document.
- A special table is created to store the details about GUID, User, Document status (send, signed, trash), Lesson ID.
- When a user visits a particular Lesson, the log details are fetched from the table that we created and will request RightSignature to generate a token. This token, which is valid for one hour, will request for an iframe to sign the document on the page.
- While generating the document, we also need to specify the callback URL on which RightSignature hits for different events, like when a document is trashed or signed. To capture the callback hit, a WordPress endpoint needs to be created.
- So when a user lands on a lesson page, he will see an iframe to sign the document. Once the signature is done, a callback hit will be done by RightSignature with a status parameter “signed” (in the case when all parties have signed the document) and “recipient_signed” when a single party has signed.
- Once you obtain signatures from of the parties, the lesson can be marked as complete and the column values of our custom table is changed.
- When a user is unenrolled from a Course, we can trash the documents which we have already generated for the lessons pertaining to the course.
To make the user sign exclusively using a client site, RightSignature should be configured to not include the signing URL in the email, but instead use the email as [email protected] in XML data sent to generate the document.
Doubts and queries? The comment section below is all yours. Stay tuned!