...
Technical field name | Neutral label | Description | |
|---|---|---|---|
yuvsigsubject | Subject | The reason why the signing was requested . This subject is part of the email sent to a signer. | |
yuvsigrequester | Signing requester | The ID of the requesting user | |
yuvsigreqdate | Date of request | The Date and time the request was activated | |
yuvsigdate | Date | The date the signing process wass finished | |
yuvsigstatus | Status | Status of the signing process. The shown values are those of the catalog ‘yuvsigstatus’ described below. | |
yuvsigerror | Error message | Error message writte by the client or the Signing-Service in case of an error. | |
yuvsigplatformid | Signing yuvsigplatform | Signing platform | The technical name of the signing platform that is configured in the signing-prod.yml file and that was used for the signing process. In the beginning only ‘docusign’ will be reported here. |
yuvsigplatformid | ID of the signing platform | The ID of the signing process on the external signing platform. In case of the signing platform ‘docusign’ this will be the envelopId. It is used by the Signing-Service to ask the signing platform for its status. | |
yuvsigners | Signers | The table listing the signers data | |
yuvsignername | Name | The name of the signer as offered on the Docusign platform | |
yuvsigneremail | Email address | Email address of a signer that is used by Docusign for sending the email. | |
yuvsigmobile yuvsignerphone | Mobile Phone number | This number can be used for two-factor authentication | |
yuvsignerorder | Signing order | The number in the sequence of signers. | |
yuvsignerdate | Date | The date and time the signer has signed or revised | |
yuvsignerstatus | Status | The status of the single signing step. This status is set by the Signing-Service. The status ‘inprocess’ is the indicator for the signing service to ask the signing platfrom for the status. |
...
Technical value name | Neutral label | Description |
|---|---|---|
requested | requested | Set when a user is requesting the signing via object action ‘Request signing’. An audit entry is written to the object history. |
signed | signed | Set by the Signing-Service after successful transfer to the external signing platform An audit entry is written to the object history. |
revised | revised | Set by the Signing-Service if one of the signers has revised the signing on the external signing plaform An audit entry is written to the object history. |
expired | expired | Set by the Signing-Service if the signing process was timed out on the external signing platform. An audit entry is written to the object history |
cancelled | cancelled | Set when a users had cancelled the signing process. An audit entry is written to the object history |
error | Error | Set by the Signing-Service in any case of error. An audit entry is written to the object history. |
inprocess | inprocess | Set by the Signing-Service if the transfer to the signing platform was positiv. |
...
A user is offered the object action ‘Request signing’ signature’ ('Signieren Signatur anfordern') if
the signing capability is activated
the relevant object type is derived from the signing abstract object type
they own the edit permission for the relevant document
the document is editable (e.g. not finalized, no signing was requested before)
Activating this action the user is asked to enter the names of one or more signers as well as its email addresses , and a subject that describes the reason for signing.
After finishing the signing request the Signing-Service is fetching the document file and transfers it to the Docusign plattformplatform. The status information is written back to the object as new attributes. An audit entry is written to the object history. A symbol in the object headers is indicating this status.
...