What are 'Imprint Fields'?

Hi muscal,

Imprint Field is a new feature introduced in recent release 11.51. It's a new type of field that can be placed on documents during the transaction creation and is not tied to any signer or signature. This ensures that the information the sender places in these fields is visible to all recipients and remains unchanged throughout the signing process.

For more detailed information, you can refer to my developer blog - OneSpan Sign Release 11.51: Imprint Field

Duo

That's great to hear this feature was developed. It was unclear from the release notes that this was part of the 'imprint field' blog post nor was i able to search search for any use of 'imprint field' in the search query. 

I have an additional question related to functionality.

Can imprint fields act as calculated fields to include information related to the transaction without explicitly setting the value during the draft package status.

As an example,

1. Create and send transaction and set the imprint field to {{onespanTransactionId}}

2. The imprint field would automatically pull from a OneSpan global canonical field and set the actual OneSpan Transaction ID into the field label

Hi muscal,

No, unfortunately I don't think imprint fields act as calculated fields. You'll have to explicitly set the imprint field value as the transaction ID.

Duo

@Duo thanks for info so far! I am needing to use imprint fields with custom anchor text but it seems like that is not supported. Can you verify? I've included my JSON payload for the REST call I am making to create a package along with my template. When I remove the x/y coordinates properties from the "imprintFields" object, my value does not display. I also don't see the extractAnchor in the imprintField schema so that makes me think it doesn't work.

Assuming that is the case, what is the recommended approach to inserting an imprint field at a specific text string? Can I use standard text tag extraction to do this? maybe like {{esl:Signer1:ImprintField:Label}} or something like that?

My use case involves dynamic documents so setting a hard-coded x/y coordinate will not work.

Let me know thoughts!