New Signing Experience Issue
Thursday, June 3, 2021 at 02:53pmIs there a change in updatePackage call for new signing experience. I am able to generate the package and update the package with settings and roles from old signing experience account but same cannot be done with new signer experience account.
I get below error only with new signing experience account where as it does not come with old signing experience account
Error updating package with OneSpan: 400 - Bad Request - {"messageKey":"error.validation.sendPackage.noApprovals","message":"Cannot send package without approvals.","code":400,"name":"Validation Error"}
JUST FYI: using same configs, same signers, same settings and same files. Just two different accounts, one with old experience and another is a new account that we got.
Reply to: New Signing Experience Issue
Thursday, June 3, 2021 at 03:36pmHi amunjal,
From the error message "you can't send package without approvals(signatures)", I am thinking if you are using the automatic extraction methods (like document extraction or text tags)? Could you share the codes around the package creation and the two accounts' emails to [email protected] so that I can take a closer look at the issue?
Duo
Reply to: New Signing Experience Issue
Thursday, June 3, 2021 at 03:53pmI think issue is that our new account is not recognizing {{esl:Signer1:Capture:Size(120,30)}} signature placeholder.
Request your help to resolve it. please.
Reply to: I think issue is that our…
Thursday, June 3, 2021 at 04:03pmHave you specified data_x.esl_doc_extract_type = '1'; in document data, like below?
//Create Document Metadata
ESignLiveAPIObjects.Document document1 = new ESignLiveAPIObjects.Document();
document1.name = document1Name;
document1.id = document1Name;
document1.extract = true;
ESignLiveAPIObjects.Data data_x = new ESignLiveAPIObjects.Data();
data_x.esl_doc_extract_type = '1';
document1.data = data_x;
pkg.documents = new List<ESignLiveAPIObjects.Document>{document1}; //add document
Or there's an easier solution, you can contact support team ([email protected]) and ask to turn on the "extract text tags" at package settings.
Duo
Reply to: Have you specified data_x…
Thursday, June 3, 2021 at 04:11pmI do not have ESignLiveAPIObjects class in my package.
Sent email to support. Can you help expedite the process please? Case CS0068274
Reply to: Have you specified data_x…
Thursday, June 3, 2021 at 04:33pmI tried below but it did not work.
OneSpanAPIObjects.Document document = new OneSpanAPIObjects.Document();
document.name = Title;
document.id = fileId;
OneSpanAPIObjects.Data data_x = new OneSpanAPIObjects.Data();
data_x.ese_document_texttag_extract_needed = '1';
document.data = data_x;
Reply to: I tried below but it did not…
Thursday, June 3, 2021 at 06:08pmNot sure when we've changed the SDK modelling (actually it seems the new SDK modelling doesn't work). You can solve it by modifying the OneSpanAPIObjects.cls line 242 to:
public String esl_doc_extract_type;
And reference the attribute with:
data_x.esl_doc_extract_type= '1';
Duo
Reply to: New Signing Experience Issue
Thursday, June 3, 2021 at 06:54pmNo it does not work, Tried that.
OneSpanAPIObjects.Document document = new OneSpanAPIObjects.Document();
document.name = Title;
document.id = fileId;
OneSpanAPIObjects.Data data_x = new OneSpanAPIObjects.Data();
data_x.esl_doc_extract_type= '1';
document.data = data_x;
public class Data
{
String origin;
String sdk;
public String esl_doc_extract_type;
public Data()
{
origin = 'Salesforce';
sdk = 'Apex v1.0';
}
}