This is our third blog out of 3 and therefore our final one in the OpenText cloud blog series. With this series we want to help you understand more about the Cloud offerings from OpenText, as well as how to smoothly implement it yourself.
Next up we want to talk about Core Signature, a cloud-based electronic signature (e-signature) application. It allows you to sign documents and/or send documents to be signed, approved, or reviewed. It also allows users to create templates that can be used later to send documents for signature.
But why use e-signature?
Considering using an e-signature application, might lead to some worries. Is it a secure way of signing documents? Could my signature be forged/stolen by someone?
To put your mind at ease, here are 3 reasons why you should be using an e-signature application.
3 benefits of e-signature
1 Lower cost
One benefit we all like to see is lower cost! Not only do you save on postage and the physicals such as paper and an envelope, but you also save time. And we all know that time is money.
Using e-signature is more convenient. No if’s or but’s about it. We live in a world where even smaller, local businesses have to deal with vendors and customers not only in different cities or states, but across oceans as well. An e-signature allows for remote authentication – which in a global company such as Turnpikes is highly appreciated.
3 High security
Security and safety in our digital world mean everything. And with an e-signature nobody can actually copy it since it includes traceable information on who signed, when they signed and where it happened. Signing a document physically does not provide that same amount of information.
How do you use OpenText Core Signature?
You can send documents to others within your organization or external users for their signature, approval, or review. Apart from the electronic signature, Core Signature provides the below additional features.
- Add an attachment: Sender can add additional files with the document that requires a signature.
- Approve a document: Sender can ask only for the approval of a user, in this scenario user will not sign the document but they will approve the document.
- Forward a document: Signer can forward the signature request to others.
- Decline a document: Signers can decline the document without signing if they found any issues with the signature request.
- Annotate the document: Apart from signature senders can also place the Date field, Text box, and Checkbox.
While sending a document for a signature request, you can use placeholders to place the signature field, Date, Text box, or Checkbox field on the document. You can also define the number of signers and the sequence in which signers have to sign.
Making it a highly functional tool that provides an efficient process.
Signers while signing can use a saved signature or type a signature, draw a signature or upload an image to be used as a signature. Once the signer signs the document both the signer and sender will receive a notification with the signed document and an audit log, signed document will be in a pdf format and the audit log contains details about the location when, and where the user signed, etc.
More technicalities for Core Signature
OpenText Core Signature can be used as a standalone or signature service.
Core signature standalone
A cloud-based web application that allows users to upload contracts, quotes, or other documents from any repository, including desktop, windows file explorer, or any other repository that allows for drag and drop or manual upload and send them to others for signatures.
Core signature service
An API-based solution where developers are provided with APIs that can be used to prepare a document for the signature and send a document for the signature. This solution can be used to send documents for signature from OpenText products or external applications.
API’s from Core Signature are designed so that they accept any request which is made with OAuth 2.0access tokens. These are retrieved using OT2’s integrated OpenText Directory Services OAuth 2.0 clients.