APEX SDK

I have downloaded the Apex SDK from GitHub that created bunch if apex class in the org and main SDK class named as OneSpanSDK. However, all of the example I see in the onespan community refers to EsignLiveSDK. Is there any difference between these two class? If yes, where can I get the package that have EsignLiveSDK. Please guide

I have a scenario where we want to consolidate as many forms into the least amount of packages as possible but some forms require two signers. What is the best approach to do this with OneSpan Sign?

For example:

• Signer 1 is the sole signer on form 1, 2
• Signer 2 is the sole signer on form 3
• Signer 1 and Signer 2 are joint signers on form 4

All forms use the same document template but have different data on them.

Is the best approach to?

We are generating a form with two fields that are intended for write back. We are able to populate these fields and they are appearing on the document after the users signs.  The file on the OSS server has the document with the fields correctly populated on the form. However, those two fields are missing from the field summary. All other fields are listed properly with their values.

How can we troubleshoot this issue?

If a OneSpan Sign package has 3 documents to sign, does the event notification send one message to cover all three documents or does it send 3 messages with different Document Ids?

I am hoping that it sends a notification for each form that is signed during the ceremony with unique document ID.

I have a few questions about the authentication pattern for the APEX SDK. I think I know the answers but I'd like confirmation:

• What is the life time of an API key?
• Is the API key generated only for the APEX SDK use, i.e. not shared by any other application?
• Is this a one-way or mutual TLS between OneSpan and Salesforce?

Transaction is being created in One Span through apex but transactions are not being created in Salesforce. What's the process to create the transaction in Salesforce?

I think this is an easy one as I think I am misunderstanding something fundamental.  How can I make a field editable?

This is populating the value correctly, but I want the signer to have the ability to adjust it:

We are using the APEX SDK plus OSS event notifications to manage our signing ceremonies. Salesforce sends out all emails to the signers with the OSS url.   However, we have a use case where a document has 4 signers and the last signer needs to be from our supervisory department (this is a common pattern).  Any member of that department can sign the document.  Ideally, any member of the department could select the document in SF (via a custom LWC) and change the signer to themselves after the first 3 sign.  

What is the best way to do this?  

I am successfully receiving events in Salesforce for transactions I created in the OSS portal but not for any packages I create via the SDK.  Is there something I need to set when I create packages via APEX?

I noticed this comment in your blog series on Salesforce events:

"In order to verify if our callback listener works as expected, we can simply create a transaction from sender portal or from any integration points as long as you’ve carried “data” > “origin” : “OSS” in the transaction JSON:"

I am using the APEX SDK to create a package, add a document and signers and then send. I receive an email to sign the document and it works great. 

Can I use getSignerURL to send the email from Salesforce as an alternative to sending the email from OneSpan servers? If so, what Is the best practice to prevent the standard email from being sent?

I tried running getSigningURL and got a link that looks legit but I get Unauthorized Access: Failed to validate token.  Is there a step I need to take prior?