Attachment requirements
Wednesday, July 19, 2023 at 09:54amHi
Is it possible to declare during the package creation instance that an extra file should be attached after signing the package documents? The package status automatically changes to COMPLETED after uploading the extra file or should I force the status to COMPLETED by API?
Regards
Gabriel
Reply to: Attachment requirements
Wednesday, July 19, 2023 at 10:25amHi Gabriel,
Thanks for your post!
It is expected that if a signer attachment is required, the transaction will be forced to turn on review before completion ("autocomplete":false). This is designed for the sender to manually check the uploaded attachment(s) and determine if to mark the transaction as completed or decline the attachments.
If you want to programmatically mark the transaction as completed, use below API:
PUT /api/packages/{packageId}
{"status":"COMPLETED"}
Duo
Duo Liang OneSpan Evangelism and Partner Integrations Developer
Reply to: Attachment requirements
Wednesday, July 19, 2023 at 10:37amHi Duo.
thanks for your answer, but is it possible to force with "autocomplete: true" in the attachments section?
I try to insert this value.
"attachmentRequirements": [ { "description": "Por favor, suba una copia escaneada de su DNI", "required": true, "id": "gabrieltestattach123456", "data": null, "status": "INCOMPLETE", "comment": "", "name": "Fotocopia DNI" } ],
Reply to: Attachment requirements
Wednesday, July 19, 2023 at 10:38amHi Gabriel,
Unfortunately, no, I think as long as there's a required attachment, the transaction will be forced to turn on "autocomplete":false and you won't be able to edit it.
Duo
Duo Liang OneSpan Evangelism and Partner Integrations Developer