Text Tags support in Salesforce

Hi Sam,

Yes, OneSpan Sign Salesforce Connector supports text tags extraction.

However, you may also see the word "text tag" when creating a convention > signer label in the connector. This is just a general word for how to place the signatures and fields. The available options are document extraction (PDF form field extraction), static position and text anchor.

Duo

Thanks Duo;

Are you saying that the words "Text Tags" would appear in the actual document? The issue we are having with is that they have introduced a longer document into one of their processes and the signature fields are showing up in the wrong area. The old document was 5 pages and the new document is 7 pages. Petro in support brought up this possibility and I am currently awaiting them confirm. I was thinking if they use text tags that would solve the issue going forward.

Hi Sam,

It sounds like they are using static position and had specified the page number. They can find where they specified this info and update there. And of course, using text tags is another solution.

Duo

Hi Duo

We could use some help with the main issue. We are hoping you can see something in their code that prohibits it from working.

Main Issue

The client has replaced a 5 page document with a 7 page document inside of the Salesforce connector and the signature field is not moving to the bottom of the 7 page document after updating the settings.

This is the link to the recording of our session with them.

Background

They have created a custom solution using OneSpan API and have the system set up so all they need to do is change the Signature Page setting (red arrow) from 5 to 7 and the signature field should move accordingly. It does not

The attached document contains a table of bookmarks that breaks down the recording - with a brief description and the time each topic appears in the recording.

Hi Sam,

Their solution looks good to me. It's a kind of static position where they stored the metadata in a custom object. Few thoughts from my end:
1. for signature page, the index is 0 based, so the first page should be signature page 0 - however if page 7 ( + 1) exceeds the maximum pages, there should have an API error telling it exceeds the boundary.

2. they can add some debugging point in the code, like to system.debug the setting.Signature_Page__c

also, they fetch the raw request of the API call if they monitoring the request in developer console > File > Open Raw Request.

Duo

Thanks Duo

I will run this by them

Well we got closer. You were right about Signature setting to be 6. That got it to the right page. How can they push it down towards the bottom (See image)

Hi Sam,

That's a good start! Try to increase the "Signature Top" value to make it towards bottom, and adding "Signature Left" value will make it towards right.

Duo