Lite Flow User Interface
- Pablo Garcia Gonzalez
- Jose Luis Lozano
Lite Flow allows the signer to perform a simplified signature process.
Advantages: The process shown to the signer consists of fewer steps to perform a quick signature.
Disadvantages: An inexperienced user may feel unguided in the process and have doubts about what he/she is doing.
On this page you can find help concerning
How is the Lite Flow process activated?
This process can be activated by web or by api at signer level in an EviSign. o Also at the time of requesting the bulkSign / SignLink signing URL.
WEB: This process can be activated by web or api at signer level in an EviSign. o Also at the time of requesting the bulkSign / SignLink signature URL.
API: LiteFlow can be requested from two endpoints. In both endpoints a LiteFlow parameter of type Boolean is added.
True: The simplified signature process is activated
False (Default): The simplified signature process is deactivated.
EviSignSubmit: at the SigningParties level, LiteFlow parameter must be specified.
ver: EviSignSubmit
"SigningParties" : {
"Name" : "Elsa Pato",
"Address" : "developer@client.test",
"SigningMethod" : "WebClick",
"LegalName" : "StaleObjectException",
"LiteFlow" : false
}EviSignBulkSign / SignLink: When requesting the signature link, the LiteFlow parameter must be reported.
ver : EviSignBulkSign
{
"UniqueIds":["d11caec270bd4739afd5aa7600920538"],
"party": "pruebas_evi@hotmail.com",
"DiscardedThreshold": 80,
"LiteFlow" : false,
} What does a simple process interface look like?
Depending on the configuration of the EviSign signature step, either the main document is accessed directly or authentication is requested using the signature method specified by the issuer.
Once the document has been read and accepted or rejected, the user is asked for confirmation to finalize the signature process.
Features that allow the use of LiteFlow
Feature | Supported | Notes |
Iframe | Yes | It's necessary to activate the simple delivery |
SignatureQuestions | Yes |
|
Challenge SignMethod | No |
|
Handwriting SignMethod | No |
|
MobilePin SignMethod | Yes |
|
VoicePin | Yes |
|
Webclick SignMethod | Yes |
|
WhatsApp | Yes |
|
Geolocation | No |
|
Begin SignStep | Yes |
|
BeforeDoc SignStep | No |
|
AfterDoc SignStep | Yes |
|
End SignStep | No |
|
Attachments | Yes |
|
SignedRedirectUrl | No | Not supported because we always redirect to Finish/ThankYou page |
AdditionalCommitment | Yes |
|
GSD | Yes |
|
CommitmentOptions | Yes |
|
AcceptReasons | Yes |
|
RejectReasons | Yes |
|
LandingPageInfoText | No | Is not supported but we don't throw error with this feature |
SignatureAppearances | No | Not supported because we don't support Handwriting SignMethod |
Reviewer Role | Yes |
|
SigningOrder | Yes |
|