yannickaustin | Posts: 2

Cannot send package without approvals

0 votes

UPDATE: Solution in comment section

Hi,

I create packages only by adding roles and signatures with ESL tags on document and it always worked perfectly. Until rencently, maybe a couple of days, we started receiving "Cannot send package without approvals" error.

Checking my code, I see I put null for approvals which of course is why the error comes out. Though, it always worked until recently. Has it become suddenly mandatory?

If yes, I can definelty start adding approvals, but kinda confused on weither I have to add an approval per role, or per signature, etc.

Let's say a document with 2 roles, 1 signer per role, 3 signatures for the first and 2 for the second.

In what way should approvals be added?

Thanks!

 

Note: Seems like the tags may not be recognized anymore. They look like this:
{{esl:Signer1:signature:size(200,50),offset(0,0)}}


Approved Answer
yannickaustin | Posts: 2

Reply to: Cannot send package without approvals

0 votes

We found out ourselves what was missing.

After recent updates of OneSpan, this breaking change came up: when you set the document parameter "extract" to "true", "extractionTypes" is now mandatory.

Example in JSON payload:

"documents":[
   {
      "id":"testDoc",
      "name":"testDoc",
      "extract":true,
      "extractionTypes": ["TEXT_TAGS"]
   }
]

The text tag example in post is still good.


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off