From PDFs in each request --> to using templates based on PDFs

Hi Vitaliy, Unfortunately, PDF forms can only be recognized once when uploading to Doc Engine at the first time, then the forms will be flattened during the whole e-signature process. So in your scenario, when you create a transaction from a template, all PDF forms have been gone, which prevents you from supplying the new key-values through Field Injection feature. What can be passed is the OneSpan Sign fields, that's why you can still see the signatures in cloned packages. Since only OSS fields can be passed from template to a transaction, you can consider using label fields instead. The difference is, the label fields will only be stamped to document after the signer signed, whereas Field Injection directly stamped the value during uploading. So the signer may have slightly different user experience during signing. You can either achieve this using code: create the transaction from a template, then update the label field values in DRAFT status. Or you can directly use our bulk send feature that allows you to use a CSV file to supply all these field values.(guide here) And may I also know the reason why you want to preserve the document in a template? I understand that you may not want to upload the document every time since the content are nearly identical, but from my own test, inherit documents from a template actually takes the same time as you upload them every time. Hope this could help! Duo

Thanks Duo! The fact that values are stamped after signing will not work for us. The reason for this is that Salesforce has a limitation of 6mb per transaction. To form a multipart/form-data request in Salesforce we convert binary data to base64 encoded string which doubles document size so our maximum for PDF document is 3mb. However, our documents usually take from 3 to 6 mb, so we use online services to compress them and this compression leads to the situation where form-fields values are in different font sizes. We spend a lot of time to play with form-field's height and settings to fix font issue after compression.

Hi Vitaliy, Are you using OSS SalesForce Connector or invoking API through an Apex classes/OSS Apex SDK? Please note that even if the value will only stamped to PDF after signing, recipients can still see the value during Signing Ceremony, just they are shown in a label box, see below screenshot: Or if you are integrated, another workaround is to bind these labels to your sender, and having an invisible signature with size (0,0), once you've sent the transaction, you can programmatically sign as sender so that these values can be stamped. Duo

Hi Duo, Thanks for the info, we will try this. And we're invoking API through an Apex classes.