mikcanf

nCino managed package via Apex SDK and "Designer View"

0 votes

https://community.onespan.com/documentation/onespan-sign/codeshare/designer-view-apex-sdk

I believe we are using nCino's managed package built on Apex SDK for OneSpan RESTful API interface.  I believe this SDK is available from GitHub showing about 25 Apex API's but I don't see "Designer View" as part of GitHub Apex SDK's. There does seem to be a "Designer View" available as shared "Apex code", is this correct?

We have encountered two issues

a) By default it seems no owner is specified at time of Pkg creation so it uses "owner" of given ACCOUNT, which is not desired.  We would like to specify specific "owner" instead of default behavior, which I believe is due to usage of API key authentication.

b) It seems the only authentication available is API key, which OneSpan documentation indicates should not be used as it will be deprecated. We would prefer to use ClientID & Secret, which may help with above issue.

Any help/understanding you can provide will be greatly appreciated.  Mike

 


Attachments

Reply to: nCino managed package via Apex SDK and "Designer View"

0 votes

Hi Mike,

 

This code share is created by me, that's because the out-of-the-box APEX SDK has limited functions, that's why I made up for the rest of the most frequently-used functions and post them as code shares.

 

For your two questions:

a) Send on behalf of sender. You can use below code to specify sender email when package creation.

       //Create package
        OneSpanAPIObjects.Package_x pkg = new OneSpanAPIObjects.Package_x();
        pkg.name = 'Example Package Using APEX SDK1 - ' + Datetime.now().format();
         
         
        OneSpanAPIObjects.Sender sender = new OneSpanAPIObjects.Sender();
        sender.email = '[email protected]';
        pkg.sender = sender;
         
        String packageId = sdk.createPackage(pkg);

 

b) Api token instead of Api key. This required a change of the SDK infrastructure, we can bring it up as an enhancement request but I temporary don't have a quick workaround for it.

 

Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Reply to: nCino managed package via Apex SDK and "Designer View"

0 votes

Question/Clarification: We are also using OneSpan inside nCino and we have to create a generic email address and give it a generic name so the email going to a client didn't have my name on it (I was the Admin).

We would love to have those email show as coming from the creator of the package. Is that what the code share will do?

We had a Designer View created as they wanted to remove the Send to Sign button.


Reply to: nCino managed package via Apex SDK and "Designer View"

0 votes

Hi Tina,

 

If you meant the email template customizations (e.g. activation email, reminder email, completion email, etc), they are account level settings and shouldn't be related to the designer view. 

To the question itself, in normal scenarios, the "from" email is always static - it could be either an email under OSS's domain, or if you provided the SMTP information, it can be an email under your specified domain. The transaction owner's email will present in the "Reply-To" field.

If you want to have dynamic "from" email, I was told that if your account has DomainKeys Identified Mail (DKIM) configured, it's possible to send email templates on behalf of various sender emails (I imagine different usernames under your organization's domain, e.g. [email protected], [email protected], etc). If this is what you meant, please kindly further confirm with support team ([email protected]) before you followed this path.

 

Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Reply to: nCino managed package via Apex SDK and "Designer View"

0 votes

Duo:  I was the Admin on our account and all the packages sent from nCino included my name in the Subject line instead of the person who is actually logged into nCino and sending the package. We had to create a dummy email address to use as the Admin and set the name on the account to be Lending Department so my name wasn't attached to every email that was being sent.

We are using the API key and I was hoping that maybe there was code that could have been used instead to identify the actual package creator and put their name in the subject line instead of the generic name.

Sending directly form OneSpan there are no issues.

Image removed.


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