Salesforce

Users just started reporting an error code when trying to send a signature to a customer.  "The supplied input cannot be parsed"  Any clues as to what the issue could be? Is this a salesforce error or OneSpan?

Please help me find documentation on how to add a Salesforce Custom Object as an available option in "Related object type". I also need to be able to automate prepare/send transaction by relating it to records in the custom object.
 

Hi Team, we have a one span configured to send the document signing in french but when they complete the signing our tags in document for Signer's Date [{{esl:Signer1:signingdate}}] is showing the date format as English format rather than French date format.

How can we fix this issue? 

Can we add formatting at tag level or org level to switch based upon the language?

Thanks and Regards

Akshay Munjal

Hi,

I want to implement some sort of writeback feature for our transactions to update a Salesforce record upon completion.

Is it possible, once we've identified that a package has been completed, we can query using the packageId the values that a client has inputted into their transaction?

I'll have around 14 different input fields and these all need mapping to individual fields in Salesforce.

Cheers in advance,

Cam

We are not receiving event notification (Decline, package complete, …etc) from OneSpan sandbox. A few years ago, it was set up for both the production and sandbox environments. All is well with production; just the Sandbox has stopped operating.

Using the below links as a reference we have reconfigured “OneSpan Sign callback service”.

We are working on creating Onespan transactions in Salesforce and have written out some Apex Trigger code to assist with the process. In order to use it in Production, we will need to write an apex test class that cover the code itself. In doing this, we are facing the below error when we try to insert, in Salesforce, a Onespan Transaction record. We are able to do the API callouts properly and they do get created on the OneSpan side. Has anyone received this error before or know what we need to do to not run into it?

Error:

We're trying to implement OneSpan Sign, but in the process of using Apex SDK, we noticed that Callback Event Notifications are not getting created for the transaction. If we create the transaction manually in Salesforce, event notifications are created for the transaction. Is there a set of requirements that need to be met in order for Callback Notifications to be turned on for a Transaction?

I created an OneSpan Sign sandbox account and I'm trying to connect via the Salesforce OneSpan app however when I try I get an API key is not valid error. Has anyone ran into this before? 

HI Team,

How can we allow a particular signer to upload a signature file into the agreement?

I know how to do it from UI but need to do it using salesforce apex code. Right now we are just adding the role as below.

Hello Community, 

I was able to install the connector on My Salesforce Dev-Org the app is showing when I go to the Admin page to connect to my OneSpan Sign sandbox I select the right environnement US2 sandbox (sandbox.esignlive.com) when I his connect a new window pops up to connect and I have the following error message : 

error=invalid_client_id&error_description=client%20identifier%20invalid

this happens both when I try with my credentials & API key 

I was wondering if You guys would be able to help