Signing workflow & signer experience — found from sitemap — Viafirma Documents

Cited by

Facts read from this source

• Policy designer location Report an error

  “When creating or editing a template from the admin panel we will find a policy section.”

• Policy definition Report an error

  “Policies are a set of evidence, signatures, approvals and other security elements that will determine how the PDF we send to the user should be signed.”

• Signature methods Report an error

  “Electronic signatures (with digital certificate) Unattended (on server) In client, using Viafirma Desktop.”

• Evidence types Report an error

  “Handwritten or biometric signature Sign OTP SMS Signature OTP Mail Images Simple and advanced checks”

• Approvals Report an error

  “This functionality means that a signature request will not be completed until one or more persons (approvers) have approved the request.”

• Approval methods Report an error

  “Simple approval. This type of approval consists of simply pressing a “Approve” button. It can also be rejected.”

• Evidence configurable fields Report an error

  “Help text: Title that will appear in the actions panel, for example “Customer signature”.”

• Evidence validation rules Report an error

  “Validation rules. You will be able to add validation rules for example for the use of CHECK, taking into account the value of other evidence incorporated in your policies.”

• Signature xml formats Report an error

  “The following formats are allowed: XADES-B, XADES-T, XADES-LT, XADES-LTA; XADES_T format is recommended.”

• Encryption alias Report an error

  “Encryption alias is optional, by default a system-defined public encryption key is used; it is only used if you want to use a different encryption key.”

• Certificate alias Report an error

  “Certificate alias is optional, by default a system-defined certificate alias is used for the unattended signature of the document (PDF) as well as the signature of the XML containing the evidence.”

• Dynamic properties Report an error

  “you can make use of values that you do not know yet but you can get them during the signing process, for example, from a form where you ask the user the data, or through metadata if the signing process was launched from an external system, for example a CRM, using our APIs.”

• Multi signer support Report an error

  “ID of the receiver. Here we can indicate the ID of the signatory to which this evidence belongs in the case of an application with several signatories.”

Scores citing this record

• The Data Protection Officer Signing workflow & signer experience
• The Data Protection Officer Evidence, validation & retention
• The HR Operations Lead Signing workflow & signer experience
• The HR Operations Lead Evidence, validation & retention
• The Integration Engineer Signing workflow & signer experience
• The Integration Engineer Evidence, validation & retention
• The Legal Counsel Signing workflow & signer experience
• The Legal Counsel Evidence, validation & retention
• The Revenue Operations Lead Signing workflow & signer experience
• The Revenue Operations Lead Evidence, validation & retention
• The Skeptic Signing workflow & signer experience
• The Skeptic Evidence, validation & retention