PDFs can have locks created by different PDF signature vendors and SWF will, by default, check for known locks in the documents you upload. If a known lock is found, the PDF is refused and the user can not create an errand with that PDF. To continue with that document, remove the lock and upload again.

To decide what message should be shown if a lock is detected, update the following attribute in the PdfValidation.properties file that can be located in you overlay folder:

pdf-validation-locked=Your message here. Include file name with %s

When a PDF is uploaded to SWF, a check for previously added signatures will also be conducted. If any previously added signatures are found, a warning will be shown to the user. However, the user can still decide to continue with the document since it is only a warning.

The above functionality is enabled by default, but if you wish to disable it, this can be done by adding this to your config file:

"signingOrders": {
	"disableDocumentChecks": true
}

The property to control message in the PdfValidation.properties file:

 pdf-validation-signed=Your message here. Include file name with %s
 pdf-validation-sign-page=This is a message if a sign page has been found which can make it unable to sign with further signatures. Include file name with %s

The application can be configured to validate PDF/A conformance validation on PDF files, when a signing order is created. The purpose of this function is to warn the user if the uploaded file does not meet the standards required by organisation policy.

Configure the system by indicating what PDF/A flavours are allowed. If NO_FLAVOUR is configured, all PDF/A flavours will be accepted. If no flavour at all is configured, the validation is skipped.