...
The structure of the XML as svg can be found here: eso.svg
and created via .xsd:
| View file | ||
|---|---|---|
|
The svg also contains XML elements which aren't relevant for TyrService upload.
...
SignatureRequestEnvelopes group several signaturerequests. The envelopes can contain documents and download conditions. The user has to fullfill the condition before or after signing. The position of the document / condition inside the envelope is defined with the <Position> element. The <Position> element begin with position 1 (and 2, 3…).
If the xml contains an envelope, all <ESign> children which are not green, are defined for each document in ESign.SignatureRequestEnvelope.Documents.Document.
...
XML-Element | webso | Type | description | ||
|---|---|---|---|---|---|
<QesId><QesProviderId> | x | Integer | The id of the qes service provider. Either <QesId> <QesProviderId> or <QesProvider> must be provided. | ||
<QesProvider> | x | String | The name of the qes service. Either <QesId> <QesProviderId> or <QesProvider> must be provided. example:
| ||
<UserName> | x | String | The UserName. It is used to map the Qes data of the user to the signature fields. | ||
<Number> | x | Number | The phone number without country code. e.g.: 173 123 123 | ||
<PhoneCode> | x | String | The international phone code of the mobile number according to iso 3166-1 alpha 2 (https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 ). e.g. “de” for Germany |
| Code Block |
|---|
<ESign> <Qes> <QesUser> <UserName>signer2@example.de</UserName> <Number>17100100100</Number> <PhoneCode>de</PhoneCode> <QesProvider>signius</QesProvider> </QesUser> <QesUser> <UserName>signer1@example.de</UserName> <Number>17200123123</Number> <PhoneCode>de</PhoneCode> <QesProviderId>1</QesProviderId> </QesUser> </Qes> </ESign> |
...