Alex's account

And BIG THANK YOU for your help! : )

Thank you! Just curious, is there any particular reason why you don't plan to publish it on nuget? As far as I know, it doesn't take much time to create a nuget package and it will allow all of your clients to find sdk in one place (i.e. all links in documentation will always point to the right place)!

Ok, I see your point. But if your team will decide to evaluate this option one more time then you can check the following use case: in our team, the person who receives notifications about new versions is not the same who will update the project. As a result, the dev team might receive information about the new release with a delay. Plus, it is just easier to manage external references in one place than going to multiple sites and checking version numbers (we integrate with many systems, so we have quite a few references). Another reason is Newtonsoft.Json.dll. Right now you need to include it into the archive and it is an old version there. At the same time, your team will be able to just reference it in nuget package. And if you tried nuget many years ago, then it might work better for you now.. Hope I'm not too pushy on this : ) And thanks again for your help!

Hello again, We are doing some final testing of this feature before pushing it to live version and we've found one issue: it is highly possible that text tag will be too long to fit on the line. For example, our users use fields in table cells and if we have something like {{?esl:signer1:textfield:size(80,30),offset(0,-15)}} then it is almost guaranteed that some part of this tag will go to a next line. Is there any solution to this issue? In addition, we've tested last week this feature with word document and it worked without issues. Unfortunately, looks like now it works only with pdf docs. Of course, we can convert docx to pdf, just curious why it was working before and doesn't work now.

Hi Haris, > docx We've just tried it and it works again. The most strange thing is that we didn't change anything in code or document itself.. and now it works. I still attached the word document to this post. Do you have some kind of monitoring system to confirm that this feature reliable? Or maybe we just need to convert it to pdf just to be safe? > 1. make the font-size of the text tags smaller Hm, that is a good idea! I think we will use this suggestion! We will change font size to "1pt" and this should work in most cases. > 2. with the flexibility of the offset parameter, you could put your text tag on the next line and use the offset to adjust it back to where you want your signature/field to be. The issue is that we don't control documents. Our users create templates with special keywords and then the system replaces keywords with data or esl keywords. As you understand, this happens automatically, so we don't know when esl keyword will be too long..