Upload Countersign Admission with airSlate SignNow

Valid countersign

is nathan and i'm here to demo a new digital signature extension for alfresco known as countersign for the purposes of this demo I've uploaded a simple contract document to alfresco this particular document has some PDF form fields defined these are digital signature fields and they've been added to the document as first second and final approver as a first step I'm going to go into manage aspects and I'm going to add a new aspect to this document called PDF document with signature fields this actually triggers a content policy in alfresco that extracts the available signature fields and adds them to the document metadata once these have been added I'm going to click Sign PDF document to go to the signature page on this page I can fill in a location i'm going to use home office a reason i'm going to use approved for release and a signature password for this particular user because this is the first time this user is signed a document we have to provide a password and confirm it we do some basic password strength checking here i'm going to apply this as a visible signature and i want to select a signature field in this case first approver lastly i'm going to go out and i'm actually going to draw the signature and once that's completed i can click save to apply this signature to the document because this is the first time this user has signed a document on the toolkit is actually going to generate a new pkcs12 key store and RSA key pair for this user and a certificate that they can use to sign this doc once the signature has been applied we can see this on the document preview page with our little drawn signature and the signature not verified message because we are using at this point a self-signed certificate so i'm going to log out as this user and log back in as a different one and go right back to our document and i'm going to apply a second signature here now when i go back into Reese ein this document i can give it a new location and a new reason and this user since they've already signed documents previously they already have a keystore generated so I'm going to provide the same password that was provided the first time the user in this case I'm still going to apply a visible signature but I'm going to turn off the signature image and i'm going to pick again a signature field notice that the first approver field is now absent from the list because it's actually been occupied by a signature now because the second signature was applied without a signature graphic we generate a simple placeholder graphic which provides some basic information about this signature such as who signed it when the reason in a location that was provided at the time the document was signed with these settings with each signature that's applied we're actually collecting some additional signature metadata and we can view that by going to view signatures this page is going to show us the document preview again along with a list of the applied signatures the date the reason the location and who actually did the signing along with a simple map that provides the geographic location the user was at when they did the signature on this is obtained using the standard html5 geolocation API is and mapped with leaflet and then a very simple document timeline which shows the document creation date and some simple information about when it was signed this timeline is actually going to expand in the future to include other workflow related events that are a part of the signature package that's it for now so feature requests are always welcome and thanks for watching