anwaykabir's account

Hi Due, thank you for the quick response, it solved my issue. The part i was missing is 'esl_FielName' part, after the correction it works fine. The final expression that worked for me is--> {{*esl_Title:Signer1:textfield:value("Default value is too long")}}' I have one more question on the similar thread, while capturing Title, we want to pass some default value, which may be longer. For longer text, i see the entire text tag is broken into two lines on my document, and in those cases , seems onespan is not able to decode this text properly. I tried to explain the issue with the screenshot. The table on our document where we are trying to print this value is very narrow and we cant make it wider. Is there any workaround on this from onespan side ?

Hello Duo, We used this below tag to capture signer Title from customer, but the problem is if this same tag appears multiple times on my document, its failing , could you please suggest what should we do here? {{esl_signerTitle:Signer1:textfield:value("My default value goes here")}} the error we are getting is: Error creating the Role: 500 - Internal Server Error - {"technical":"EsepCommand failed and no fallback available.","messageKey":"error.internal.default","message":"Unexpected error. We apologize for any inconvenience this may have caused you, please try again. If the problem persists, please contact our support team.","code":500,"name":"Unhandled Server Error"} 12:15:38.473 (2024773771)|DML_BEGIN|[368]|Op:Insert|Type:signatureTransaction__c|Rows:1

Hello Duo, Thanks for the call yesterday. we are still stuck because of the issue that same text field ({{*esl_Title1:Signer:textfield:value("director")}}) cant be repeated on same pdf document. Things becomes complicated as we generate document from multiple templates and its hard to place different title text tags on each document. Initially we thought that i will append name of the docs with the title to make them unique, but as we are generating the docs from Conga, and it has limitation that onespan text tags cant be placed there directly while generating the document (it has to be read from a salesforce field). So i think this solution may not work. So here are my questions: 1. Can we use the textfield only once to capture user's input and then print the same automatically everywhere on the document. 2. Can we use customField here for this use case. Can custom field be used to take user's input and the same information will printed on other occurrences of the document. if yes, how can we put custom field on the document while generating it. Please let me know, if you are available for a quick call on the same. Thanks Anway Kabir

Hello Duo, Reading the onespan documentation it seems like, the same can be done using custom field feature, but i am sure fully how to embed that on our solution. Can we have a quick call to go through on the same? Thanks Anway Kabir +1 3065368026

Hello Duo, As we discussed, that custom field option is not available for apex JDK or Resrt API approach, could you please create an enhancement request for us on this? The requirement is, we are using APEX SDK for our e-sign use cases. We have requirement that during sign process Signer will enter their 'Title' once (Title appears multiple times on a doc) and the same info will be updated on the document on all its occurrences. FYI, we can not achieve this using text field approach, additionally we do not want users to enter same information again and again during signing process. Thanks Anway Kabir +1 3065368026