peterzog | Posts: 109

Dynamic Disclosure

0 votes

Reading these two documents:

https://www.onespan.com/blog/onespan-sign-developers-consent-document-vs-default-consent-part1

https://www.onespan.com/blog/onespan-sign-developers-consent-document-vs-default-consent-part-2

 

Is it possible to upload the disclosure agreement as part of the package creation via the API?

We have a disclosure document that the user must accept for some packages, and that disclosure document changes quite often.  It would be ideal to upload the disclosure document at the time the package is being created on OneSpan - via API.  Is that possible? Or do we need to upload the document to OneSpan servers through the support team or the portal?


Approved Answer
Duo_Liang | Posts: 3776

Reply to: Dynamic Disclosure

0 votes

Hi Peter,

 

A quick update on this topic, if you contact support team and customize this UI label:
"oss.components.AcceptConsentBar.button.label": "Read the full Disclosure [here](https://www.google.com)"

The output result looks like the attached screenshot.

 

Duo


Duo_Liang | Posts: 3776

Reply to: Dynamic Disclosure

0 votes

Hi Peter,

 

It's possible to replace the default-consent in package creation call, please refer to the Part2 guide "Upload Customized Default Consent" section.

In short, it's worth an attempt setting both document.id and package_x.consent as default-consent

document.id = 'default-consent';

package_x.consent = 'default-consent';

Please let me know how this works for you.

 

Duo

 


peterzog | Posts: 109

Reply to: Dynamic Disclosure

0 votes

Duo,

One more question on this.  Do you know if we can place an active hyperlink on the disclosure? We want to link out to a URL that represents the full disclosure and give the user the opportunity to click it and review in a new browser tab. I saw another post that said hyperlinks were not allowed on the forms but I wasn't sure if that applied to the disclosure consent as well.

Thanks!

Peter


peterzog | Posts: 109

Reply to: Dynamic Disclosure

0 votes

Not sure if you saw my post above from yesterday since I saw an error that the forum email failed when I submitted it.  


Duo_Liang | Posts: 3776

Reply to: Dynamic Disclosure

0 votes

Hi Peter,

 

I made a reply in another post yesterday, have you got any chance to receive the notification?

https://community.onespan.com/forum/x-getting-removed-package-id

 

Duo


peterzog | Posts: 109

Reply to: Dynamic Disclosure

0 votes

Oh sorry! I think we have two different topics going.  This one is about clickable hyperlinks in the consent disclosure.  See a couple posts up on this thread.


Duo_Liang | Posts: 3776

Reply to: Dynamic Disclosure

0 votes

Hi Peter,

 

Yes, I also missed your post in this thread... Feel free to make a new forum post if I didn't get notified or didn't reply. ;)

Back to this topic, as far as I know, OSS now keeps the hyperlink in the PDF after signing, but they are not clickable during the signing ceremony. See the screenshot, none of these hyperlinks were active.

As a workaround, in OSS signing ceremony, there are two places allow to customize the UI labels with Markdown formatting:

Help Page:https://www.onespan.com/blog/onespan-sign-release-1136-new-package-settings

Thank you Summary:https://www.onespan.com/blog/new-signer-experience-thank-you-summary-page-part-2

I will ask around internally if there's any more UI labels customization allows Markdown formatting and allows hyper link.

 

Duo


peterzog | Posts: 109

Reply to: Dynamic Disclosure

1 votes

You're the best.


peterzog | Posts: 109

Reply to: Dynamic Disclosure

0 votes

One more question, the button label option (below) is global. right?


"oss.components.AcceptConsentBar.button.label": "Read the full Disclosure [here](https://www.google.com)"

We are seeking a dynamic option where we can display an active hyperlink link based on the form used. Our disclosure is almost 300 pages, it changes a lot, and it only applies to a subset of our forms.  So, the ideal experience from a maintenance and scale perspective is if we present the signer with a clickable link to a page we manage.


Duo_Liang | Posts: 3776

Reply to: Dynamic Disclosure

0 votes

Hi Peter,

 

Yes, the AcceptConsentBar button label is specified at the account level. Another option is to keep the hyperlink URL in plain text in your PDF, so that the recipient has the option to manually open a new tab and visit the hyperlink.

 

Duo


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