Date: Fri, 29 Mar 2024 13:48:08 +0100 (CET) Message-ID: <98983142.236.1711716488421@atlconfluence01.d4.namirialtrusted.it> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_235_1929659211.1711716488419" ------=_Part_235_1929659211.1711716488419 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Alice and Frank want to buy a new car. So they are going to the local ca= r dealer to look and check the models to buy one. The car dealer is using e= SignAnywhere for digital signing. To record biometric signatures on the poi= nt-of-sales (POS), a native app (e.g. SIGNificant App or SignAnyWhere App o= n iOS, Android or Windows ) is required on the tablet device.
You find a = list of available stories here. Please also see the developer mode for = this tutorial here: Visit the dev= eloper mode.
Information
This example uses the native SIGNificant App (for Android and iOS) and r= equires an eSignAnywhere Instance with an open Workstep Controller Process = interface. This is available at https://demo.esignanywhere.net/= a>, so it is recommended to create an free account at https://dem= o.esignanywhere.net/ for testing this example or use your own on-premis= e or private-SaaS eSignAnyhwere instance.
Note: Due the security limitations, this example will not work on http:= //significant.com. Please use https://demo.esignanywhere.net/= instead. The following example and description uses the endpoints of <= a href=3D"https://demo.esignanywhere.net/" class=3D"external-link" rel=3D"n= ofollow">https://demo.esignanywhere.net/.
The integration of this use case requires eSignAnywhere and the SIGNific= ant App on the tablet. Due the integration of the native App, this integrat= ion is a little bit different from eSignAnywhere-only integrations.
The creation of the workflow is similar, except that in one step (so one= recipient) two persons are signing at once (=E2=80=9Chosted meeting=E2=80= =9D). This is done via the use of the native SIGNificant App. Therefore no = authentication is required. Moreover, this scenario is perfect for biometri= c signatures (advanced electronic signatures) and due the biometric signatu= res it doesn=E2=80=99t require any authentication.
To bring the document to the tablet there are some options available:
This example shows two integration for option 1 (Email) and option 2 (QR= Code).
The workflow is the following:
Endpoint (URI) for REST: https://demo.esignanywhere.net/Api=
callback=
code> is used to update the car dealerships CRM
{ "Documents": [{ "FileId": "c30dbbfc-1234-1234-ae0f-55ee351d9452", "DocumentNumber": 1 } ], "Name": "Test", "Activities": [{ "Action": { "Sign": { "RecipientConfiguration": { "IncludedEmailAppLinks": { "Android": true, "iOS": true, "Windows": true }, "ContactInformation": { "Email": "janedoe@sample.com", "GivenName": "Jane", "Surname": "Doe", "LanguageCode": "EN" } }, "Elements": { "Signatures": [{ "TaskConfiguration": { "OrderDefinition": { "OrderIndex": 0 } }, "ElementId": "sample sig biometric", "Required": true, "DocumentNumber": 1, "DisplayName": "Sign here", "AllowedSignatureTypes": { "Biometric": { "BiometricVerification": false, "AllowBiometricStoringOnly": false, "StoreSignedResponseWithoutBioData"= : true, "AllowSkipBiometricVerification": f= alse, "BiometricServerUserId": "string", "SignaturePositioning": "WithinFiel= d", "Preferred": true, "StampImprintConfiguration": { "DisplayExtraInformation": true= , "DisplayEmail": true, "DisplayTransactionId": true, "DisplayTransactionToken": true= , "DisplayPhoneNumber": true, "UseCustomStampImprint": true, "DisplayIp": true, "DisplayName": true, "DisplaySignatureDate": true, "FontName": "string", "FontSizeInPt": 0 } } }, "FieldDefinition": { "Position": { "PageNumber": 1, "X": 100, "Y": 200 }, "Size": { "Width": 100, "Height": 70 } } } ] }, "SigningGroup": "firstSigner" } } }, { "Action": { "SendCopy": { "RecipientConfiguration": { "ContactInformation": { "Email": "janedoe@sample.com", "GivenName": "John", "Surname": "Doe", "LanguageCode": "EN" } } } } } ] }
Workflow:
&responseType<=
span class=3D"pun">=3DreturnWorkstepId).
callback=
code> is used to update the car dealerships CRM
Retrieve WorkstepID and generate the QR Code
The first recipient in this example is the tablet. The SIGNificant App r= equires the workstepId for signing the document. After you created the enve= lope (SendEnvelope) you do the following:
workstepRedirectionUrl
. This URL is the link to the Sign=
Anywhere Viewer (Web-Client), which forwards to the eSAW redirector and del=
ivers a link with a workstepId parameter. With the additional parameterhttp:/= /launch.xyzmo.com/SignificantAndroidAppLauncher.aspx?WorkstepId=3D##WORKSTE= PID##&server=3Ddemo.esignanywhere.net/WSCProcess&protocol=3Dhttps= span>