---
title: "5.6 Multi-round signing with PDF with signature acrofields"
description: "In multi-round signing with PDF with acrofields (and other active elements) we can also define available signature acrofields. Within the registration of new *signature request* we use parameter *allowedFields:SIGNATURE*, in example value *_sigAcrofield1_.* It is possible pre-fill the other active…"
url: "https://wiki.signatus.com/documentation/okdokument-api/5-6-multi-round-signing-with-pdf-with-signature-acrofields/"
updated: "2025-03-21"
category: 5. Configuration of the signing process
---

# 5.6 Multi-round signing with PDF with signature acrofields

In multi-round signing with PDF with acrofields (and other active elements) we can also define available signature acrofields. Within the registration of new *signature request* we use parameter *allowedFields:SIGNATURE*, in example value *_sigAcrofield1_.*

It is possible pre-fill the other active elements, like in example before.

```
{
    "signatureRequestId": "1d58a59e-e8f7-4d07-bb99-d3fa39cb58a8",
    "expirationTime": "1702288000000",
    "sendInfoURL": "http://api.okdokument/info",
    "resulturl": "https://okdokument.com/",
    "allowedFields": {
        "SIGNATURE": "_sigAcrofield1_"
    },
    "rules": {
        "signAnywhereEnabled": false
     },
    "fieldConfig": [
        {
            "name": "firstName",
            "value": "Jozef",
            "readOnly": false
        },
        {
            "name": "lastName",
            "value": "Novák",
            "readOnly": false
        },
        {
            "name": "date",
            "value": "31.12.2022",
            "readOnly": true
        },
        {
            "name": "checkBox1",
            "value": "1",
            "readOnly": true
        }
    ],
    "filedata": {
        "content": "xyz_JVBERi0xLjc==",
        "state": "tosign"
    }
}
```

For the next round of signature, the same rules as for PDF with tags. Portal has to:

- Register new *signatureRequestId* – if generated by OKdokument API it will be new random value, if pre-filled by Portal, new *ID* must be used
- Reference to document ID – signed document from the first round of signing is stored in internal OKdokument API storage. Use document *ID* as a reference of the document (*filedata* with document content is not needed)
- *Change state* – after signing the document in the first round, the document changes the state to “signed”. It is needed to change the document state to “tosign” in order to sign the document in the next round of signing
- Change *allowedFields:SIGNATURE* to value *_sigAcrofield2_*

After first round of signing are all active elements in the PDF (not signature acrofields) unavailable for further editing. That’s because any changes to the document after first signature are not allowed. That’s why in the second signature request there is no need to fill/use the parameter *fieldConfig*.

```
{
    "signatureRequestId": "1d58a59e-e8f7-4d07-bb99-d3fa39cb58a8",
    "expirationTime": "1702288000000",
    "sendInfoURL": "http://api.okdokument/info",
    "resulturl": "https://okdokument.com/",
    "allowedFields": {
        "SIGNATURE": "_sigAcrofield2_"
    },
    "rules": {
        "signAnywhereEnabled": false
     },
    "id": "y7Ki_u1mrUwijfb-o_S1JiphSsoXya8iypH380F",
    "changeState": "tosign"
}
```
