Account


Earned badges

Achievement: Latest Unlocked

Topic Started

Topics

I am getting the following error. I'm using the code in a Salesforce Flow. This works perfectly in the first sandbox. But I'm beginning to move this to production and something is not working.

I'm working on the callbacks into Salesforce. The callbacks are triggering just fine.

I am using a template inside OneSpan to create the package. The template is set up for 2 signers but I would like to remove the second signer using the apex class if there's not one.

I am having trouble replacing the "Placeholder" signers for the template created. I have 2 signers setup as placeholders ('Signer1'). 

I am getting an error error.validation.sendPackage.noApprovals from the Salesforce Package. 

Replies Created

Reply to: Set up Callback Listener in Salesforce

0 votes

I am working through this process. I have the reset_token from part 1 and it tested sucessfully in the first of part 2. I have pushed these settings to OneSpan using Postman and I used the "get" to test and it looks like it returned just fine.

However, when completing the signing of a transaction, I'm not seeing any signs that it's coming through. There are no logs popping up in the Dev Console. It could be the key.

From my understanding, the key is a base64 json line derived from:

{"host":"test.salesforce.com",
"client_id":"3MVG97wqan.......14tfqr8JKu1T4f6Zx",
"refresh_token":"5Aep861MbVwd.....X_I1oLvvdMyo2Z.i.Q"}

host - this is my sandbox
client_id - this was created from my connected app in Salesforce
refresh_token - this was created in part 1 and tested successfully in part 2.

I took this code and put it in https://codebeautify.org/json-to-base64-converter which created a really long string. This string is what I'm using as a part of the key.

I'm hoping I've done everything correctly?


Reply to:

0 votes

Thanks Duo,

I have edited the OneSpanAPIObjects.cls. The dev log shows this when sending the package

{"status":"SENT","data":{"sdk":"Apex v1.0","origin":"oss","esl_doc_extract_type":"1"}}

 

Originally, origin had "Salesforce". It also should be noted that "oss" is in lowercase. Does this need to be all uppercase?

Also, I've used 3 different websites to create a base64 string of the json code. All three have returned different results. They are small but they are different.


Reply to:

0 votes

Thanks Duo,

I have edited the OneSpanAPIObjects.cls. The dev log shows this when sending the package

{"status":"SENT","data":{"sdk":"Apex v1.0","origin":"oss","esl_doc_extract_type":"1"}}

 

Originally, origin had "Salesforce". It also should be noted that "oss" is in lowercase. Does this need to be all uppercase?

Also, I've used 3 different websites to create a base64 string of the json code. All three have returned different results. They are small but they are different.


Subscriptions

Topics Replies Freshness Views Users

I'm wondering if the APEX SDK has the ability to create a sender. I see that some of the other SDKs can.

 

2 7 months ago 29
Profile picture for user Duo_Liang

I am getting the following error. I'm using the code in a Salesforce Flow. This works perfectly in the first sandbox. But I'm beginning to move this to production and something is not working.

2 8 months ago 20
Profile picture for user Duo_Liang

I'm working on the callbacks into Salesforce. The callbacks are triggering just fine.

4 9 months 1 week ago 74
Profile picture for user Duo_Liang

I am using a template inside OneSpan to create the package. The template is set up for 2 signers but I would like to remove the second signer using the apex class if there's not one.

2 9 months 2 weeks ago 31
Profile picture for user Duo_Liang

I am having trouble replacing the "Placeholder" signers for the template created. I have 2 signers setup as placeholders ('Signer1'). 

5 10 months 1 week ago 91
Profile picture for user Duo_Liang

Code Share

This user has not submitted any code shares.

Subscriptions Release Notes

This user is not subscribed to any release notes.