LogoSignature Service
Built-in Clients

Integrate white-labeled apps

Sysmosoft provides client apps for Android, iOS and Web platforms that can be used out without a line of development.

Customizing client behaviour

The client behaviour can be slightly customized by adding meta-data in the contract sent to the workflow engine.

Contract's title and description

Specify the title and the description to display for the given contract in the different views of the app. These labels are displayed as is, without translation depending on device's locale.

Contract's metadata

"metaData" : {
  "title":"My title", <1>
  "description":"My description" <2>
}
  1. Contract's title
  2. Contract's description

Sign refused PDF

Adds a watermark to the PDF indicating that the PDF is refused by the user, then signs digitally the document once the user confirm the signature.

Contract's metadata

"metaData" : {
  "sign-refused-pdf": "true" <1>
}
  1. Specify whether the refused PDFs should be watermarked and signed. Default: false

Applies only for contract's type PDF.

Custom signature appearance

Customizes the signature appearance with signer's name and a short description.

The signer's name is built using the firstname and / or the lastname provided. If none are available, the username is used.

Contract's metadata

"metaData" : {
  "firstname": "John", <1>
  "lastname": "Doe", <2>
  "signatureDescription": "Digitally signed by Product Name" <3>
}
  1. Fistname of the user (required)
  2. Lastname of the user (required)
  3. Free text written at the bottom of the signature. Default: Digitally signed by {firstname} {lastname}

Applies only for contract's type PDF.

Custom signature attributes

Some of the signature attributes can be set with labels provided as meta data :

The labels may contain well-known placeholders ({firstname},{lastname}, {userEmail}, {phoneNumber}) that will be replaced by meta data with same key if available.

Contract's metadata

"metaData" : {
  "signatureName": "{firstname} {lastname} ({userEmail})", <1>
  "signatureReason": "Confirmed by SMS ({phoneNumber})", <2>
  "signatureLocation": "Zürich - Switzerland", <3>
  "estimatedSignatureSize": "16000", <4>
  "firstname": "John",
  "lastname": "Doe",
  "userEmail": "john.doe@example.com",
  "phoneNumber": "+41781234567"
}
  1. Sets the name attribute. Default: the username of the user
  2. Sets the location attribute. Default: null
  3. Sets the reason attribute. Default: accepted or refused depending user's decision
  4. Sets the estimated size of the digital signature in bytes. It must not be lower than the actual signature size. Default: 32767 (32KB)

Applies only for contract's type PDF.

Notification

Specify the text of the OS notification displayed when a new contract is available

Default behaviour : Generic label (body only) is used depending on the device's locale.

Contract's metadata

"metaData" : {
  "notificationTitle": "This is a custom notification",
  "notificationBody": "This is a custom notification"
}

It's possible to disable push notifications by adding the following meta data in the contract

Contract's metadata

"metaData" : {
  "skipNotification": "true"
}

Applies only for mobile apps.

Transactional buttons

Changes the text of the ACCEPT and REFUSE buttons to ACCEPT TRANSACTION and REFUSE TRANSACTION. This may be needed to meet the company's compliance requirements, depending the use case.

Default behaviour : ACCEPT and REFUSE buttons are displayed.

Contract's metadata

"metaData" : {
  "transactional": "true"
}

Applies only for mobile apps.

Cancellation interval

Adds a 3 seconds interval during which the user can cancel his response. This may be useful to reduce the risk of manipulation errors by users.

Default behaviour : Response is sent instantly after user's action.

Contract's metadata

"metaData" : {
  "cancelable": "true"
}

Allow user to save document after signature

It allows the user to save the document on its device after the signature. This may be needed to meet the company's compliance requirements, depending the use case.

The user's choice (save document / discard document) can be retrieved in the Audit trail.

Default behaviour : User is not allowed to store the document on its device.

Contract's metadata

"metaData" : {
  "allow-user-save-pdf": "true"
}

Applies only for mobile apps and contract's type PDF.

On this page